There was a software update for Sonos today and now the “Say” function does not work anymore. I get an error on the Sonos that says : Unable to play “Say.***.mp3”- file is encoded incorrectly". I have been sending the same command string and it has worked flawlessly:
It is not working for me too this morning.
As it was working well the previous days, it has no link to a Sonos update even if an update was released by Sonos few days ago.
I hope Google has not closed its TTS service !!!
Ditto here… I tried to do a simple TTS say with no speakee… last night. How do we know if Google closed their TTS service and if so what is the alternate? Mike
[quote=“lolodomo, post:2, topic:188206”]It is not working for me too this morning.
As it was working well the previous days, it has no link to a Sonos update even if an update was released by Sonos few days ago.
I hope Google has not closed its TTS service !!![/quote]
Same here, I’m going to try to install osx in a virtual machine and use the osx tts server. I have a windows maching running all the time anyway for blue iris and plex anyway. I’ll report back if I have any success.
Its interesting as mine has stopped working as well on the Play 1’s after update. I have also noticed that all the tts to mp3 sites are not working, could this be a Google issue? In The Sonos app i can see that it groups the zones ok and attempts to play with a “the track i not encoded correctly”
Oook, so is there a recovery schema to Google’s change and/or is there an alternate solution? I take it we fall into the “Automated service” category? Mike
[quote=“lolodomo, post:12, topic:188206”]I just renamed the topic !
That’s really a big problem ![/quote]
I read about Microsoft Translator API this afternoon and I am now convinced that adding this TTS engine is doable.
For the user, that would be more difficult to setup because an account has to be created on a particular platform and a new application has to be declared by the user to get the identifiers that will be required by the plugin.
For the plugin itself, the new thing is that a session token has to be obtained and renewed when necessary.
So I will add this new engine to the plugin. Should be available in few days.
Any idea if the Microsoft speech is as good as Google speech ?
Note that the account is free if you translate less than 20 000 characters per month. That’s largely enough for few TTS messages per day.