Chris Scott & Associates - www.scott-inc.com 
 Public Radio Station Automation  

PAUSE DETECTION Frequently Asked Questions (FAQ):


Q. If PAUSE DETECTION works, , why haven't I heard of it before?

A.  PAUSE DETECTION is NEW.  It was developed in late 1997.



Q. Why automate these programs?

A.  Network programs sound more consistent. Whether used as an announcer-assist tool,
or fully unattended, this computer automation technology is mature.  There can be significant operational cost savings as well.



Q. What advantage does the pause detector provide over timed local insertions?

A. Timed insertions work great as long as NPR announcers and producers are perfect AND your automation timebase matches NPR.  Too often however, annoucers are human, and err by a second; the result is overlapping or "upcut" audio - it can sound very automated.  The PAUSE DETECTOR will not upcut audio - transitions only happen during silence. Precise time sync is also less critical.



Q. How do I know if the pause detector is compatible with my automation system?

A. Any automation system that can react to external trigger signals within a narrow time window can accept the PAUSE DETECTOR's output.  It works the same way as an external cue tone detector unit would. Audiovault, Cartworks, and most others support the pause detector.



Q. How reliable is pause detection?

A. Quite reliable.  It is dependant upon NPR pausing, but this is easier for them to do than to hit ultra-precise timeposts.  Our tests show that they pause close enough better than 97% of the time.



Q.  How involved is installation?

A.  About the same as a cue tone detector. In order to keep cost very low, the PAUSE DETECTOR is sold in module form.  Depending upon station requirements, installation time will be approximately two to five hours.



 
View Pause Detector Page.
See The original "white paper"