https://bugs.kde.org/show_bug.cgi?id=395466
Bug ID: 395466
Summary: plasma-pa mishandles virtual streams, creates issues
with PulseEffects
Product: plasma-pa
Version: unspecified
Platform: unspecified
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: now...@gmail.com
Reporter: tyx...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: ---
Hello there,
unlike users of other DEs, Plasma users currently have some issues when using
an audio effects app PulseEffects. This app relies on using two virtual
streams "PulseEffects (apps)" and "PulseEffects (mic). There's three observable
issues:
1. PulseEffects is started on the wrong outputs; instead of Built-in Analog
Stereo, playback will start on e.g. PulseEffects(mic). This means there is no
sound and PulseEffects does not work! The user has to go into pavucontrol and
fix this.
2. The PulseEffects recording stream will be switched to a wrong output once
audio playback finishes. This means you have to go to pavucontrol and switch it
every time you play a new song.
3. The levels of both PulseEffects streams, which should always be kept at
100%, get messed up by volume keys because plasma-pa allows this at certain and
specific times. This means you may get quieter audio when using PulseEffects
than when not.
Now the first two issues are highly likely related to a bug with the
'device-manager' module which *should* be resolved in PulseAudio 12 and a
temporary workaround for Plasma users is to unload the module (discussed here:
https://github.com/wwmm/pulseeffects/issues/99). But the third issue seems to
be specifically related to plasma-pa and not KDE itself because it does not
occur with KMix, which means using KMix is the workaround for this problem for
now. For some reason, plasma-pa will allow volume keys to alter the levels of
PulseEffects virtual streams, even when Built-In Analog Audio is clearly set as
the default output device. For me there's always a sure shot way of reproducing
this:
1. PulseEffects' two virutal streams need to be loaded, the program itself can
actually be turned off and doing nothing
2. Play a song in Youtube and stop its playback.
3. Open a new song in a new tab, led it load fully, but do not switch to this
tab yet.
4. plasma-pa is now affecting either PulseEffect(apps) or PulseEffects (mic)
via volume keys!
5. Now you go play the tab and it's back to properly affecting Built-in Analog
Stereo
Here is a verbose (level 4) PulseAudio log of when this precise thing happens:
https://github.com/wwmm/pulseeffects/files/2103997/pulseeffects_issue235-3.txt
And this is the thread where the bug was reported with PulseEffects first, the
author states there is no code in PulseEffects to cause this:
https://github.com/wwmm/pulseeffects/issues/235
Some more troubleshooting can be found there, but I'd be happy to provide any
other information I can. And sorry for the long report, it's quite a specific
issue so I felt like I had to explain everything related to it :)
P.S - this was mentioned in the github thread, but toggling the 'Automatically
switch all running streams when a new output becomes available' option makes no
difference.
--
You are receiving this mail because:
You are watching all bug changes.
