E Mixer creates many duplicate recording sinks #35
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Mixer module is creating a lot of duplicate recording sinks, as viewed in pavumixer. It is also consuming a considerable amount of CPU ( which is how I noticed ). Steps to reproduce and observe:
Have at least 1 application playing audio.
Open pavumixer and click on the "Recording" tab. Observe the list of clients currently "recording". I generally have none at this point:
Click the Mixer module to close the pop-up window, and the sink disappears.
Now click the Mixer module to re-open the pop-up window. This time, change the volume levels of the client playing audio ( in this example, Firefox ), and note the duplicate __e_mon recording sinks:
As mentioned, this has a serious impact on CPU utilisation, in Enlightenment and X. When I restart E, all the duplicate sinks are removed.
I don't see duplicates like you - i do see the source outputs. e (and e's mixer tool) use these to monitor playback, output and input streams. pavucontrol also does the same thing. mixer popup appears - i see one of e's monitor outputs then when popup goes away, it disappears (in pavucontrol). e and e's mixer tool (both inherit the same backend code in the mixer module) specifically ignore any outputs named __e_mon as it knows it's one of its own monitor streams. pavucontrol does the same trick. it names them "Peak detect".
So this command to list media:
that's with pavucontrol running. now i open e's mixer popup:
now i hide the popup:
i run e's mixer tool:
Close the emixer tool window:
Now close pavucontrol:
i.e. - nothing. I now pop up e's mixer popup again:
Also nothing. No output playing or anything recording and nothnig to monitor...
So I'm not seeing some leak in monitors here. Regular pulseaudio running. 3 Audio devices (2 USB and a HDMI device).
I guess I should have e ignore "Peak detect" recording streams as they are just pavucontrol's own way of doing what e';s mixer popup does and emixer tool does - monitor input sources to show the current sound levels. e's mixer popup will only show the microphone volume level monitor if it sees something recording at the time (i did this for the case you use e.g. zoom or whatever and you now know what is asking to record - the cases for the 2 mixer tools is one where they are not actually recording but monitoring so filtering is probably a better experience).