3 ms·
wouldn't that just mean that Watson sucks at text to speech? also since that's probably the case for most tts services (at least in my experience) why not run
by ldehaan 10y ago
wouldn't that just mean that Watson sucks at text to speech?
also since that's probably the case for most tts services (at least in my experience)
why not run the audio through all the tts engines you can find and compare results. keep what has the highest matches and see if you can get the other words using phonetics engines.
for words that are specific to your company train a tts engine on those words and weight your local engine higher than other services.
you can get a pretty decent translation back, but who would be so lazy as to work that hard..... ;)
- skykooler 10y agoA large part of the issue is that if you are dealing with phone meetings, audio is severely compressed, and not very similar to the training data that Watson has been taught with. Google Voice might be able to do a better transcription, because they have much more data from phone messages to work with, but eventually it comes down to the fact that voices over a phone line are a lot harder to understand without context processing than voices recorded with a decent microphone.