pavucontrol opens a peak meter for every input and output device, no matter whether the device panel in question is open or not. I'm trying to build a multi-station PA system. pavucontrol displays all of these streams in the Playback and/or Recording panels. IMHO these streams should be marked so that they are not displayed by default. As it is it's almost impossible to find the one stream I'm actually interested in among the large number of peak meters. The virtual vs. hardware distinction doesn't help here, obviously. Secondary problems: * the recording stream's media name ("Peak meter") isn't displayed in pavucontrol * the stream's originator (i.e. the bold part) is named "pulseaudio" instead of "pavucontrol" or _"Volume control".
I didn't quite follow your explanation. What do you mean by "multi-station"? If I understood correctly, pavucontrol shows the streams of some peak meters that you don't want it to show, but what peak meters are those? You probably don't mean pavucontrol's own peak meters, since those streams are already hidden.
Umm, yes I do mean pavucontrol's own meters, and no their streams are not hidden. Not on my system anyway. Can you point me at the code that's supposed to do the hiding? I'll attach a debugger to it and check why it doesn't.
MainWindow::updateSourceOutput() in src/mainwindow.cc checks the application ID to hide all streams from pavucontrol, gnome volume control and kde kmixd. https://cgit.freedesktop.org/pulseaudio/pavucontrol/tree/src/mainwindow.cc#n813
The problem is that masking "org.PulseAudio.pavucontrol" only filters the local pavucontrol's streams. If however a peak monitor stream is opened to a remote system, the app id on the monitored system is "org.PulseAudio.PulseAudio". Worse, looking at "pactl list" it's obvious that the resampling to mono 25Hz peak monitoring appears to be done by the pulseaudio server which pavucontrol connects to, not the one with the actual hardware. This causes a lot of superfluous traffic. One of my setups will consist of 50+ satellites (each a Raspberry Pi 3 with speaker, microphone, and local echo cancelling) which export their audio devices via zeroconf. Handling 150 audio streams at the same time is out of the question. If this resampling issue is just a configuration problem, I'd appreciate a pointer.
There seems to be some confusion here. In the initial report you said that on the local pavucontrol you see streams for every peak meter of a remote pavucontrol, but I don't think that is the case. I believe you're only seeing the streams of the tunnel sinks and tunnel sources. Those streams exist whether or not pavucontrol is running on the remote machine or not, and if you add new streams on the remote machine, no new streams should appear on the local pavucontrol. The tunnels don't adjust their sample rate depending on what rate applications are using, which is something that could be improved, but in the specific case of the 25 Hz streams created by pavucontrol, those will have to be resampled to a higher rate in any case, because otherwise pavucontrol would prevent other applications from using the tunnel devices with any reasonable rate (the device rate can't be updated when the device is being used). If you just want to hide the tunnel streams in pavucontrol, that's a reasonable request. I think the tunnel streams should count as virtual streams, which pavucontrol already has an option for filtering out.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pavucontrol/issues/21.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.