28 Feb
2018
28 Feb
'18
7:08 a.m.
Luke Kenneth Casson Leighton wrote:
what happens with alsamixer and alsamixergui? i
suspect you have a
loop on your hands where pulseaudio has taken control without your
consent or knowledge of the ALSA devices.
what do you mean? I installed pulse and let it take control. alsamixer works
just fine. When alsamixer is invoked without argument, it shows pulseaudio
as audiocard. When I run it with -c 0 it shows the audiocard as when pulse
was not installed
pulseaudio may be interfering, i've had to kill
pavucontrol, and
pulseaudio, then finally the audio programs were able to wrestle
control of /dev/snd/* away from pulseaudio, and things went to normal.
restarted pavucontrol and it was fine.
when killing PA, kmix also goes at 100% CPU - need to quit kmix. When I
press volume key kmix starts again
i suspect this is *nothing to do with* tde, and
everything to do with
pulseaudio being a pile of shit.
Well, I appreciate your opinion, but there must be a solution, so that kmix
does not go 100% CPU. I am asking if someone has experience, or had a look
already, otherwise I have to go through kmix code or who knows what else
and write a patch.
regards