[EAS] Spanish Language Version

[Mike McCarthy]

Harold,

Thank you for the reply.

I'm not in front of a web skin, but I'll look later this morning on the
abort and kill buttons. I'm fine with the "sending the entire header"
aspect before the EOM's.  The interest lay mainly with killing any message
which played, but didn't end because the sender didn't send an EOM or the
box is simply misbehaving. Such as what happened with the Illinois IEMA
EAN OOOPS in 2010.

#2..  The goal would be avoid the need to go out to a site which may have
seen a surge, lightning strike or other observed odd operation. Such as
not wanting to run the RWT when the button pressed. Or more significantly,
when an alert has somehow locked up the box and can't be terminated.

Now...while one can not presume the remote reset will work in all cases,
it's a potentially significant time saver for those who have remote boxes.
Clearly that function can be initiated as I saw that with the update to
89-30.  The question is how that could be brought to the skin and make it
highly reliable to execute even if the box is otherwise locked up.

Another is to avoiding having untrained non-technical staff poking around
the rear of a rack to power cycle the unit.

#3, The picking point would after the insertion. So the audio monitored
would be absolute and positive of what is leaving the box. Again, for
remote boxes, it's a confidence monitor to insure that correct program
audio has been restored following a message or we can monitor an event as
it's played out.

I understand AES will be a challenge....  One of our sites is AES I/O. 
The balance are analog.

Cheers...

Mike

On Thu, September 29, 2016 7:48 am, Harold Price wrote:
> Mike,
>
> As always, thanks for suggestions, many features were originally
> added because someone asked for them.
>
> Everyone - I am always a bit embarrassed to hijack user forums for
> vendor specific items, in the normal case, please contact Sage directly.
>
> Harold
>