Does Chrome, FireFox, Brave etc use the PipeWire server now? - I get mic problems

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

 



People,

Some told me they thought that browsers talked directly to the soundcard?

With upgrading from F33 (X/XFCE4/ALSA) to F34 (Wayland/Sway/PipeWire) I have been thrashing the system a bit to see how it goes and found trying to serially record stuff online from three different browsers and also recording stuff with a number of apps causes me to lose access to the default mic for ALL inputs . .

Since I don't have any trouble PLAYING from as many sources as I want to but ONLY recording, I have turned OFF access to the mic for all the browsers (C, FF, B) and will try to only use stand-alone apps that need the mic (using default) ie audacity, jisti, obs, zoom, arecord etc - I will see how that approach goes for a while.

Also, because of problems in the early days with PulseAudio, I got into the habit of routinely uninstalling it and just using ALSA plus my .asoundrc file - now I thought PW was going to completely replace PA but I see there are still a number of RPMs installed:

alsa-lib-1.2.5.1-2.fc34.x86_64
alsa-sof-firmware-1.8-1.fc34.noarch
alsa-ucm-1.2.5.1-2.fc34.noarch
alsa-utils-1.2.5.1-1.fc34.x86_64

pipewire-0.3.35-2.fc34.x86_64
pipewire-alsa-0.3.35-2.fc34.x86_64
pipewire-gstreamer-0.3.35-2.fc34.x86_64
pipewire-jack-audio-connection-kit-0.3.35-2.fc34.x86_64
pipewire-libs-0.3.35-2.fc34.x86_64
pipewire-pulseaudio-0.3.35-2.fc34.x86_64
pipewire-utils-0.3.35-2.fc34.x86_64
pipewire0.2-libs-0.2.7-5.fc34.x86_64

pulseaudio-libs-14.2-3.fc34.x86_64
pulseaudio-libs-glib2-14.2-3.fc34.x86_64
pulseaudio-qt-1.2-5.fc34.x86_64
pulseaudio-utils-14.2-3.fc34.x86_64

Any info on how this stuff is supposed to work / hang together would be appreciated! - a diagram somewhere would be great!

Regards,

Phil.
--
Philip Rhoades

PO Box 896
Cowra  NSW  2794
Australia
E-mail:  phil@xxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux