[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Search]

[Emacspeak] Re: TTS Problems with Pipewire and Fedora 37



I probably wasn't clear.

After removing pipewire-pulse, the system was using pipewire-alsa. It
works, but felt a little laggy and the quality sounded a little
distorted. However, it worked fine. Unfortunately, many other apps won't
work without the pipewire-pulse module (I suspect I can probably
configure pipewire for each of them to make them use pipewire-alsa - I
was surprised they didn't do this automatically once pipewire-pulse was
removed). I did do a full reboot, so I know it wasn't due to some things
still being loaded etc.

What I want to try and do is configure pipewire to force espeak to use
alsa rather than pulse. If I can do that, I can have the pipewire-pulse
module, so all pulse apps work and have espeak work using alsa
under pipewire. I know this can be done because I briefly did it
accidentally using the CLI tools. Unfortunately, I was not able to
reproduce the config after a reboot. When I did have it working, the
device was reporting as Pipewire Alsa espeak rather than just espeak as
usual. 

There are just so many moving parts here - I find it extremely
confusing! I have a reasonable grasp of the basic architecture and
relationship between hardware, ALSA, pipewire and
pipewire-pulse. However, all the different configuration layers, plus
the extensive use of lua by pipewire as the configuration/scripting
language is certainly challenging. I probably need to spend some time
learning lua as I know nothing about it as a language. From what I can
tell, I should be able to define some lua scripts to take the espeak
output and route them to whatever sink I want, so should be able to get
it to bypass pulse.


"T.V Raman" <raman(a)google.com> writes:

> Like I said, look for pipewire-alsa.
>
> Espeak adds another twist in that it uses portaudio and that gives one
> more level of indirection 


|May 1995 - Last Year|Current Year|


If you have questions about this archive or had problems using it, please contact us.

Contact Info Page