Conversation
Phantasm
phnt@fluffytail.org
I love when software that's supposed to be better than it's previous alternative merges old stupidity from the old one. Thank you PipeWire for merging the alsa-ucm conflicting device patches from pulseaudio. Now there's almost no way to switch between speakers and headphones on most laptops I've used without physically unplugging them.
2
1
2
Phantasm
phnt@fluffytail.org
@getimiskon No, it's the new 1.2.0 release of PipeWire ("The UCM conflicting devices patches were merged." in changelog). Reverting to the last stable version (1.0.7) fixed it.
There's apparently some wireplumber config to ignore the alsa ucm which might fix it. I'll try it later.
There's apparently some wireplumber config to ignore the alsa ucm which might fix it. I'll try it later.
1
0
1
gettie (
arc) 
getimiskon
@phnt personally I never had many issues with PipeWire in general. But I absolutely hate wireplumber. It's the worst piece of software in my audio setup I have to deal with. And the sad thing is that there's currently no alternative to it.
1
0
1
Phantasm
phnt@fluffytail.org
@getimiskon Personally wireplumber mostly "just worked" for me most of the time. I've had some weird audio pops and stutters recently, but those were fixed. But I get where you are coming from. Writing a config for disabling the alsa ucm thing, which didn't work, wasn't easy. The config syntax is stupid.
Btw the new way for switching the ports is to change the card profile in pulsemixer. The "Set port" option only shows the active port. However KDE Plasma somehow worked around that and still shows the two options like it did before.
Btw the new way for switching the ports is to change the card profile in pulsemixer. The "Set port" option only shows the active port. However KDE Plasma somehow worked around that and still shows the two options like it did before.
1
0
1
gettie ( arc)
getimiskon
@phnt personally i want to kill the developers for not providing some fucking documentation. No man pages, so if you're offline for some reason, "fuck you". Also they have made quite a few breaking changes that required me to reconfigure my audio setup.
And the thing is because I use broadcasting software, I need specific configuration for my stuff, which is another pain in the ass. I hate it, I just hate it.
And the thing is because I use broadcasting software, I need specific configuration for my stuff, which is another pain in the ass. I hate it, I just hate it.
0
0
1
1
0
0
@phnt@fluffytail.org
All you have to do is edit that config to disable it
1
0
0
@dushman Nope, this config is the more generic one that most users would use. I checked all the config that wireplumber read at startup (sof-hda-dsp ones) and none of them had the manual conflict definition. It had a playback priority set 2 levels deep in includes and changing those only changes priority (same priority results in both outputs playing at the same time).
The real solution is to change the card profile in pulsemixer instead of changing the port that isn't available anymore for reasons. KDE already dealt with that change and works exactly the same.
The real solution is to change the card profile in pulsemixer instead of changing the port that isn't available anymore for reasons. KDE already dealt with that change and works exactly the same.
0
0
1