You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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)
I have Fedora 39 with espeak-ng and Voxin installed system wide. Before installing pied:
After installing pied:
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!
The text was updated successfully, but these errors were encountered: