• Get involved.
    We want your input!
    Apply for Membership and join the conversations about everything related to broadcasting.

    After we receive your registration, a moderator will review it. After your registration is approved, you will be permitted to post.
    If you use a disposable or false email address, your registration will be rejected.

    After your membership is approved, please take a minute to tell us a little bit about yourself.
    https://www.radiodiscussions.com/forums/introduce-yourself.1088/

    Thanks in advance and have fun!
    RadioDiscussions Administrators

Sage Digital Endec

Hello All,

Like most small market stations, we are automated, and while some say what I'm about to ask is "bad programming" I feel it is VERY IMPORTANT to automaticly relay information from our Sage over the air. Warnings, Watches, etc.

I haven't used a sage in a long time, and on former stations I worked at, I simply had the old version to relay everything. I can't seem to remember how I did that..(thats why i'm here).

So, How do you get the new Sage Digital Endec to relay all alerts?

Thanks!
Egon
 
It's the same way really. In fact, if you have your old config file from the old one, I think you can use ENDECSET and copy it to the new one. I'd advise not wearing your audience out too much by sending everything, but that's your programming call. Tornado watches and may T-storm warnings would be as far as I'd ever dream pushing it. Too much can sensitize your audience to not even paying attention to when it really matters.
 
Apparently there is a way to use your automation system to "hold" certain alerts until after a stop-set. Haven't played with, would appear to require a system that can supply a closure to the Sage. Something to investigate.

Probably best to use the EndecSet software designed for the digital unit, there are a number of settings specific to this box. The manual is fairly useless, but once you figure the software out it is not difficult. First set up the counties in your local area, also which RMT's to respond to (we straddle two states, so our local area is different

You then set up several different categories of filters, depending upon what you want to do--e.g., EAN one category, tornado warnings , blizzard warnings etc. would normally go into a relay immediately category, while some other alerts you may want to delay for a certain number of minutes (which you can set). Other alerts may be set to log only.

Because you connect your digital Sage to your local area network, delaying some alerts can be useful, even though you are automated. We set up a shortcut on the air computer that takes you directly to the Sage control page. When an alert is delayed, it can be manually aborted. Useful on those days when there are a lot of thunderstorms moving through & NWS sends off multiple alerts, each with a 90 second lecture about not driving through flooded roads.
 
TomT said:
Apparently there is a way to use your automation system to "hold" certain alerts until after a stop-set. Haven't played with, would appear to require a system that can supply a closure to the Sage. Something to investigate.

I would like to try that with a DASDEC but I'm not sure if StationPlaylist can supply a "hold off" closure. (LPFM, no need for high dollar automation system here...)
 
OKCRadioGuy said:
Tornado watches and may T-storm warnings would be as far as I'd ever dream pushing it. Too much can sensitize your audience to not even paying attention to when it really matters.
That's my philosophy as well and it worked out fine in most cases, but one station called me and asked why the ENDEC wasn't working while there were Tornado warnings in surrounding counties. I set this station up for Tornado Watch/Tornado Warning/Severe T-Storm Watch and Severe T-Storm Warnings in their county of license (500 watts AM with 100% of the audience within the county). At their request, it now includes all surrounding counties, even though no one listens in those counties when the weather is good. Add lightning static to the mix and it's even less likely. Guess that's why I never made my mark in the programming world.
 
Our B-1 hits bits and pieces of ten counties, and they are programmed in as the local area for alerts. Sometimes very relevant, when a front is moving from the SW to the NE. Sometimes not when when moving from the west directly east.

We monitor two NWS stations, which can also result in duplicating alerts. One NWS station will send an alert for counties A,B, & C; the other for C, D & E. Since we have county "C" programmed in the alert runs twice; to the Sage it's a different alert.
 
Status
This thread has been closed due to inactivity. You can create a new thread to discuss this topic.


Back
Top Bottom