I’ve finally started to implement some announcements into my system. I’ve so far been using Piper and it works beautifully so long as I’m not targeting a (Google) Nest Hub or Hub Max. The old first generation Google Home speakers, a Nest Audio speaker, some 2nd gen Sonos Play:1 speakers, and even my Sony HT-A7000 soundbar all play back the Piper messages without incident and in their entirety. The devices with screens however have a delay that cuts off the start. I’ve looked around but haven’t noticed others complain about this. So is this a known issue? Or an issue with me doing something wrong?
My inelegant workaround for the time being is to have “Nest Hub delay” prepended to the Piper TTS directed at a screen device. That phrase seems to be exactly the amount of time that gets cut off at the beginning. Well the timing is right if you’re using the voice “hfc female (medium)”. I havent actually tested it with other voices.
Thanks for sharing this! It’s working great for me and has the added benefit of being able to display an image and text. I’ve just been dealing with the cut-off bug for years with throwaway text at the start, but now that I moved to piper and I’m dynamically generating the TTS input, it has come back to plague me.
There must be some inherent issue with the Hub and Hub Max. If I change the voice to anything “medium”, the problem persists. amy-low works fine and amy-medium brings me back to just hearing “finished”. Also the stream_type: “BUFFERED” seems to make no difference with either low or medium voices.
Well for the time being I’m just going to use amy-low, which honestly sounds just fine to me.