3 ms·
On a somewhat related note, why does the Google STT engine have a grudge against the word "o'clock"? If you say "start at four" it gives you the text "start at
by Causality1 7y ago
On a somewhat related note, why does the Google STT engine have a grudge against the word "o'clock"?
If you say "start at four" it gives you the text "start at 4." So far so good, but if you say "start at four o'clock" you just get "start at 4" again, not "start at 4:00" like you wanted. In fact you can say the word o'clock over and over for several seconds and it will type absolutely nothing.
- yorwba 7y agoHaving recently experienced a similar issue with "filler" words that mysteriously disappeared in a transliteration pipeline, I'd guess that this is due to an artifact in the training data. Most likely the STT engine was trained on transcriptions created by lazy humans who simply wrote "4" when they heard "four o'clock", so the engine learned that "o'clock" is a speech disfluency just like "umm" that usually doesn't appear in writing.
- Eridrus 7y agoI just tried this on the google assistant and didn't get the behavior you describe. When you look at the streaming results, you can clearly see it produce the o'clock, but it gets normalized to 4:00 at the end. Are you talking about cloud ASR or something?