Michael Hansen
Michael Hansen
Not yet, but this is planned.
I need to figure out a good way for this to work. Some voice models also contain multiple speakers, for example the LibriTTS voice has 900! This will quickly become...
I won't have time to get this working, but if someone else is interested they will need to get [piper-phonemize](https://github.com/rhasspy/piper-phonemize/) compiled for Android. This will involve compiling an [espeak-ng fork](https://github.com/rhasspy/espeak-ng)...
The audio parameters that @Luke100000 linked are tuned for 22Khz (not by me, by the original authors). Did you choose "high" quality when using 44Khz data?
@Inzuki39 You may be running into this problem with the Windows console and UTF-8: https://stackoverflow.com/questions/57131654/using-utf-8-encoding-chcp-65001-in-command-prompt-windows-powershell-window
Development has moved: https://github.com/OHF-Voice/piper1-gpl I think the "text" phonemes type should behave similar to how you have "raw" here, no?
If it's exposed as a proper `fan` entity, it could be done with the new `HassSetFanSpeed` intent: https://github.com/OHF-Voice/intents/pull/3336
Related issue: https://github.com/home-assistant/core/issues/134224
Looks good to mean. I'd like to hear from the other language leaders, so let's give it a little time. This fix needs to be in the intents bump for...
A PR is being worked on to add support for this intent 👍 https://github.com/home-assistant/core/pull/136484