Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Piper as TTS provider #261

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Add Piper as TTS provider #261

wants to merge 1 commit into from

Conversation

rkusa
Copy link
Collaborator

@rkusa rkusa commented May 24, 2024

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/

@rurounijones
Copy link
Contributor

rurounijones commented May 26, 2024

I think having a high quality local TTS provider is worth any dependency niggles like having a separate exe (We could always bundle it) and there isn't too much latency.

I think merging this is a net positive!.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants