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.
On Tue, 21 Sep 2021 23:41:04 +1000 Philip Rhoades via users users@lists.fedoraproject.org wrote:
Some told me they thought that browsers talked directly to the soundcard?
Not for a long, long time. If you have pulseaudio or pipewire installed, and are using them as default, then no matter what the browser thinks, it is talking to pulseaudio or pipewire.
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 . .
This sounds like a bug. You could look at the list here, https://gitlab.freedesktop.org/pipewire/pipewire/-/issues to see if it is listed. Otherwise, you could open a new issue.
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.
Because play is working everywhere, record should work everywhere. So, a bug or possibly a mic misconfiguration error.
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:
I think it is hybrid, with pipewire replacing more the higher logic, and still using the basic plumbing of pulseaudio.
Any info on how this stuff is supposed to work / hang together would be appreciated! - a diagram somewhere would be great!
I'm not aware of anything like that. Pipewire is still under very active development, so that is probably taking priority until the fires are out.
At the bottom of this page, there are some links to more information about pipewire. Might or might not help you.
stan,
On 2021-09-22 23:01, stan wrote:
On Tue, 21 Sep 2021 23:41:04 +1000 Philip Rhoades via users users@lists.fedoraproject.org wrote:
Some told me they thought that browsers talked directly to the soundcard?
Not for a long, long time. If you have pulseaudio or pipewire installed, and are using them as default, then no matter what the browser thinks, it is talking to pulseaudio or pipewire.
Right.
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 . .
This sounds like a bug. You could look at the list here, https://gitlab.freedesktop.org/pipewire/pipewire/-/issues to see if it is listed. Otherwise, you could open a new issue.
OK, I will check that out.
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.
Because play is working everywhere, record should work everywhere.
Why is that so? - one is SNOOP and one is DMIX controlled isn't it?
So, a bug or possibly a mic misconfiguration error.
Right but how could it be a misconfiguration error if I am just using the "default" Mic all the time?
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:
I think it is hybrid, with pipewire replacing more the higher logic, and still using the basic plumbing of pulseaudio.
Ah, OK.
Any info on how this stuff is supposed to work / hang together would be appreciated! - a diagram somewhere would be great!
I'm not aware of anything like that. Pipewire is still under very active development, so that is probably taking priority until the fires are out.
I can believe it . .
At the bottom of this page, there are some links to more information about pipewire. Might or might not help you.
Nothing here?
Thanks for that - I appreciate the feedback!
Regards,
Phil.
On Thu, 23 Sep 2021 03:18:06 +1000 Philip Rhoades via users users@lists.fedoraproject.org wrote:
On 2021-09-22 23:01, stan wrote:
This sounds like a bug. You could look at the list here, https://gitlab.freedesktop.org/pipewire/pipewire/-/issues to see if it is listed. Otherwise, you could open a new issue.
OK, I will check that out.
Because play is working everywhere, record should work everywhere.
Why is that so? - one is SNOOP and one is DMIX controlled isn't it?
I'm talking higher level than that: if pipewire handles playback, it should handle recording. If it doesn't, it isn't working correctly.
Right but how could it be a misconfiguration error if I am just using the "default" Mic all the time?
The default is not set to a proper value, possibly internally in pipewire. What does arecord -lv show? Is the default set via pavucontrol one of those? If you set the one you want as default again in pavucontrol does it make a difference?
Nothing here?
I could have sworn I added this link
https://github.com/PipeWire/pipewire
At the bottom of the page there is a section called Documentation.
-
Philip Rhoades -
stan