Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Piper as another TTS provider.
Similar to #231, it cannot directly be compiled into DCS-gRPC, but at least doesn't require running an http server. In a nutshell: it requires to manually download Piper, and DCS-gRPC runs the
piper.exe
each time TTS is executed.I am not sure if I really want to add Piper this way, which is why I'll be keeping this as a draft PR for now. Ideally, I'd personally prefer to remove all other TTS options eventually, if we are able to settle on a local option with great quality (so that we/I don't have to maintain 5 different providers).
It definitely has great speech quality and does not require a lot of resources (it is optimized for the Raspberry PIs).
sample.zip
Voices can also be tested here: https://rhasspy.github.io/piper-samples/