[EAS] EAS Digest, Vol 21, Issue 12

[Mike McCarthy]

The challenge is to make it universally compatible without the need for 
introducing another pathway to maintain.  Especially if the IP side 
doesn't follow the same pipe as the audio.  Plus, I'm preferring to not 
spend hundreds of dollars on hardware for a once a week event. I can 
achieve the instant goal of using DTMF by hanging a $150 or less decoder 
on the program path.

And to one of my other prior points...embedded DTMF (or other embedded 
signal) is fairly simple and free to implement at the station end (ie no 
cost if done in a DAW), a firmware upgrade, and some wiring for the box 
for analog monitoring using input #6.

AES gets messier unless there is sampling/monitoring done in the box. If 
not, the external closure is likely anyway due to a DA converter.

I will say the Dataprobe IPIO8 is an interesting product.  That would be 
good for a split day/night site operation needing to switch sites.  
Could not find the CC-IP-CC however.

I'm going to let this lay and see what the manufacturers have to say 
about this concept for RWT triggering of a remotely located device.

MM

On 7/6/2012 8:45 AM, Arthur Leisey wrote:
> Mike,
>
> Your concept of having the EAS box decode DTMF is entirely possible.  The manufactuer would need to modify their firmware to handle this.  However, due to the need to have an Internet connection for receiving CAP messages, your remote site inherently has Ethernet available.  At least two major suppliers of EAS gear have been moving to more IP-centric architectures in their deployments, using the Dataprobe CC-IP-CC switch for remote control.  And, at least one even embeds the TX control commands into their firmware.
>
> Art Leisey
> aleisey at gmail.com
>