Emergency Alerting with different voices
Our EAS application monitors your countrie's NADD stream, and if there is an emergency message that matches your alerting box, it will interrupt and play that announcement immediately. The way EAS messages play on radio, TV or cable will depend on how it was issued by the originator. Many messages are sent by Pelmorex or NAAD as an mp3 file, sometimes served from AWS. The player downloads this file and plays it on the air. If there is an mp3 file, and it doesn’t arrive (or is somehow corrupted), it will fall back and use on-board TTS engine to read out the description of the CAP alert. The quality on the on-board alerts are "technically challenged" and at best sounds like a robot reading the text.
Our latest OBPlayer has the capability of using AWS POLLY (Machine Learning AI) instead of the onboard TTS. When an alert is received, the text is sent to AWS POLLY using the various voices available on the dashboard setup. If a message comes in without an attached media, OBPlayer will first try using the POLLY service, and if it is not available, use the onboard TTS as a last resort. If the server at POLLY goes 404, or times out it switches automatically to the onboard TTS espeak application.
POLLY is an additional paid service requiring a key that is easily put into your player dashboard. The cost for this service is minimal, $4.00 USD for one million characters, enough for thousands of hours of TTS. Upon receiving and playing a valid CAP message, users of OBPlayer on a CATV head end with an image file (such as a JPEG from the alert issuer) will find it plays full screen, with a POLLY TTS of the message if there was no MP3 file sent. In the case where there was no MP3 or JPEG file in the alert, a red scroll (white text) will display with accompanying TTS.