a.slo...@bham.ac.uk said on Sun, 1 Jan 2023 02:08:43 GMT

>Steve,
>
>Thanks for the rapid response.
>

>[SL]
>> Why not just use ALSA? That's what I do, and except for a few
>> snowflake programs like Zoom, everything works fine.  
>
>Actually zoom is essential for me (and my next invited zoom talk will
>be later this month).

My finding, from a year ago, is there's no way to use Zoom with ALSA
alone. I don't even know if Zoom will work with Pipewire but no
Pulseaudio.

I call Pulseaudio "the land of a thousand mutes", because fixing all
the possible mutes in order to get sound is like playing whack-a-mole.

[snip]
>But f37 has somehow clobbered audio for me so I can't use zoom anyway
>at the moment.

This sounds like a problem best asked of the Fedora people. They
screwed it up, they should fix it. They, and Redhat, were the ones who
ushered in Poetterware in the first place.

>For audio:
>
>I used a 'startpulse' command defined to do this:
>
>    systemctl start --user pulseaudio

Try just running pulseaudio from a terminal emulator (like xterm)
logged into your username. Try to find a command line option so
pulseaudio stays in the foreground. This might help you troubleshoot.
>Is there a simple answer to the question:
>
>    How do I replace pulseaudio (including its menus) with alsa ?
>
>Simple enough to get working before my next talk, alongside a
>collection of other urgent tasks that need to be finished soon?

Just uninstall pulseaudio, and if ALSA isn't already installed, install
ALSA. But my findings is that doing so eliminates sound in your Zoom
sessions.

SteveT

Steve Litt 
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm

Reply via email to