No, I never actually did. I originally installed it like half a year ago because I wanted to try out a virtual audio cable type setup but didn’t really figure out how it works and didn’t have the time to, then unistalled it. The only reason that it is installed now is because I compiled OBS recently and it’s one of the (soft-)dependencies.
pavucontrol has a lot more stuff available then the KDE sound controls at least… while looking at that I also noticed that the Line Out is also gone now, and it’s only showing the Digital Out as a selection.
KDE Sound Settings:
pavucontrol:
When I select Analog Stereo Out in pavucontrol, the device disappears from the KDE system tray…
/edit: setting it back to Digital Out and selecting Analog Stereo Out again and it’s still there.. weird.
After plugging the Headphone back into the mainboard I now have Line Out back, but no Headphone/Speaker there. I thought that maybe Speaker and Line Out are swapped on the board, but Plugging it into the Line Out actually removed the Line Out and I just have the Digital Out again…
As for alsamixer, I’m not sure what I’m looking at:
Well no, not really different. It was the same for me when I still had both selections. Line Out was also the default audio plug is was sent to because no matter how often I replugged the headphones, the sound control would say “unplugged”. Though I don’t know if that is the reason for the Line Out default, but the sound also didn’t go out anywhere.
Currently there is nothing plugged into the motherboard directly at all because then I wouldn’t have sound. I have both Mic and Headphone/Speaker connected to the G430 now as a work around. But my Mic is still getting terrible noise that is being directly monitored to the headphones and I can’t disable it apparently.
Not really, no. I thought about that too but why did it work (sort of) when installing then… I mean if it were a problem with the board, the sound devices would have been missing from the start, no?
Also alsa-info with the Headphone plugged into the motherboard (instead of the G430):
http://alsa-project.org/db/?f=7f80cbccc414b3b7512f8677cce0eb3a0deebd09
edit:
I think someone’s messing with me …
So I didn’t really want to fiddle around with the ALSA controls but I thought it’s busted anyway soo… I did this:
And now I’m actually getting sound out of the headphone jack, but KDE’s control still calls it Line Out (which.. not a big deal, just weird).
But why was it muted there in the first place… also not sure if it will persist.
And another edit:
I just saw that the motherboards backside actually labels the jack as “Line Out”, not Headphone, so the naming sort of makes sense. But then the <Headphone> in alsamixer controls it and <Line> is probably the (blue) Line In.
edit after restart:
No sound again, alsamixer’s <Headphone> is on MM (which I assume is supposed to be “mute”?) again and Volume at 0. Weird thing is: When I turn up the volume without “unmuting” I still get sound… eh?
Anyway, how would I go about it not being muted on each restart? 