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

Local configuration stomps on system-wide configuration #5

Open
joanmarie opened this issue Jan 8, 2024 · 1 comment
Open

Local configuration stomps on system-wide configuration #5

joanmarie opened this issue Jan 8, 2024 · 1 comment
Assignees

Comments

@joanmarie
Copy link

I have Fedora 39 with espeak-ng and Voxin installed system wide. Before installing pied:

$ spd-say -O
OUTPUT MODULES
voxin
espeak-ng-mbrola
espeak-ng

After installing pied:

$ spd-say -O
OUTPUT MODULES
piper

Removing ~/.config/speech-dispatcher/speechd.conf solved the immediate problem of restoring espeak-ng and voxin.

I'd like to be able to have piper with speech-dispatcher, co-existing with voxin and espeak-ng and anything else I might have installed.

I'm also the maintainer of the Orca screen reader. I'd like to get feedback from Orca users on the responsiveness of piper. Pied looks like a great tool to make this possible. But I don't want to wind up with end users losing access to their other synthesizers which they might want/need to modify or restore configurations, etc. So anything you can do to ensure all installed synthesizers remain available as output modules would be great.

Thanks in advance!

@Elleo
Copy link
Owner

Elleo commented Jan 8, 2024

Hi @joanmarie!

Thanks for raising this. I'll try experimenting with copying any existing system configuration into the local user configuration prior to modifying it.

I'm also planning on adding a button for reverting the configuration in the future, which should hopefully make it easier for people to test with minimal risk (currently Pied offers to options to revert immediately after it changes the configuration, but the addition of a permanent button would allow the configuration to be rolled back at any time)

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

No branches or pull requests

2 participants