[EAS] What is the solution for the TTS problem?
Tom Taggart
tpt at literock93r.com
Thu Jan 19 12:22:42 CST 2012
Harold Price wrote:
"Out of the box, the various TTS implementation are
inconsistent. Local areas will need to train each device
type to say
their place names. Trust me, this is pretty tedious to do
even once."
Gee, even the carbon-based text to voice readers have
problem with some of the weirder place names. Even the ones
you wouldn't think would be a problem.
Like VUR-Sails for Versailles, VI-enna for Vienna,
Nuh-VAY-duh, for Nevada.
Then there's Medina (MehDINE-uh) and Lima (LYE-muh)and
Muskingum, which every network news guy east of here insists
on pronouncing as Muskegon.
The big boxes (Sage, Dasdec, Tri-lithic) are all computers.
I am assuming if heads were beat together to use a
standardized text-to-voice program it could be made to work
on all three & just downloaded at a later date.
Granted, this gets to the basic weakness of the entire
system--it assumes the stations are going to be able to get
these things installed & talking to the internet. For many
small stations this requires two contract people--the 65
year old engineer who keeps them on the air, and the 15 year
old kid who keeps their computers running.
One of my employees manages a B-1 college station. Got his
Sage all programmed and installed--fires off tests and hears
NWS and his relay. only problem is he's been waiting
several weeks now for the College's IT staff to get him an
internet connection that works.
But that's a different issue.
More information about the EAS
mailing list