-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Speech dispatcher doesn't work after after installing. #1
Comments
Hi @yummmy-yummmy, Sorry that you're having problems with Pied. If you had an existing user configuration for speech dispatcher it will have been saved as
Alternatively, if you didn't previously have a user configuration, then simply deleting the configuration generated by Pied will return you to the default/system configuration:
To help me figure out why it's not working for you, are you able to let me know what version of speech dispatcher you have installed (running Thanks! |
Thanks, deleting the config file worked. I don't tinker with these stuff usually so this was my first time using it. As for |
Great, glad that's got things working for you again. Thanks for the extra info, I'll try setting up a Fedora VM and see if I can reproduce the issue there. |
I think I've figured out what's wrong, Fedora 39 is using aplay as the default play command instead of paplay, and the format parameters are incompatible. I just need to figure out a good way to dynamically select the right parameters and then this should be sorted. Unfortunately, I'm going to be away at a conference all week, but I'll have a dig into this once I get back. |
The following workaround is working for me on Fedora 39:
to
|
I've just released version 0.2 which includes a fallback to aplay if paplay isn't available on the host system, thanks for finding this issue! |
After installing and changing the config, speech dispatcher no longer works for me.
When i run
spd-say "This is a test"
, it doesn't give me an audio output.Can I revert the changes somehow?
System Information
OS: Fedora 39
Package format: Flatpak
The text was updated successfully, but these errors were encountered: