lost multimedia headphone in pavu

[millodrums]

After playing around with jack and pulseaudio , i lost my multimedia headphone interface in pavu; now i only have hdmi speaker and system speaker.

I am using manjaro KDE. Can someone help out ?

in $

Code: Select all

aplay -L 

i still see the headphone, so with

Code: Select all

 /proc/asound/cards.

However in PulseAudio Volume Controller (gui) and pulsemixer (TUI), both no headphone.
And smplayer does now show headphone now also.

Thx

[Linuxmusician01]

Jack is in control of your audio now. That's why your audio stuff won't show up anymore in pavucontrol (= Pulse Audio Control panel). I'd install qjackctl if I were you and use that.

If you want to make thing complex and want to let PA and Jack play together than you can use Jack Sink.

Code: Select all

pactl load-module module-jack-sink &
pactl set-default-sink jack_out &

Then open pavucontrol and set 'jack_out' as e.g. Chrome's playback device.

Good luck with puzzeling with Linux audio.

[millodrums]

After restarted computer, everything is ok now. After i stop jack, the missing interface returned.
If i don't want thing to get complex, what is your advice ?

Jack is in control of your audio now. That's why your audio stuff won't show up anymore in pavucontrol (= Pulse Audio Control panel). I'd install qjackctl if I were you and use that.

If you want to make thing complex and want to let PA and Jack play together than you can use Jack Sink.

Code: Select all

pactl load-module module-jack-sink &
pactl set-default-sink jack_out &

Then open pavucontrol and set 'jack_out' as e.g. Chrome's playback device.

Good luck with puzzeling with Linux audio.

[j_e_f_f_g]

If i don't want thing to get complex, what is your advice ?

Don't use any program that can only use JACK. Make sure a program has some setting somewhere that lets it directly use ALSA, and then set it to do that. Any program that requires jack in order to work is going to give you problems because the majority of audio problems involve jack itself. It's an incredibly invasive, overly complicated piece of software that isn't written to peacefully coexist with linux's official audio api. Rather, jack tries to take away the management and allocation of audio resources from alsa.

[Linuxmusician01]

If i don't want thing to get complex, what is your advice ?

Don't use any program that can only use JACK. Make sure a program has some setting somewhere that lets it directly use ALSA, and then set it to do that. Any program that requires jack in order to work is going to give you problems because the majority of audio problems involve jack itself. It's an incredibly invasive, overly complicated piece of software that isn't written to peacefully coexist with linux's official audio api. Rather, jack tries to take away the management and allocation of audio resources from alsa.

I agree. Try to not use Jack. If you absolutely must use Jack (e.g. Qtractor) then stop PulseAudio and stop using PAVUControl. Unfortunately, PA is a pain in the neck and respawns itself after stopping it. I stop PA this way: uncomment the following 2 lines from /etc/pulse/client.conf:

Code: Select all

autospawn = no
daemon-binary = /bin/true

For newer Linux systems (i.e. Debian 10):

Code: Select all

systemctl --user mask pulseaudio.socket
systemctl --user stop pulseaudio

Then do the kill:

Code: Select all

pulseaudio --kill

Good luck

[millodrums]

Just to clarify,
PA is the default (simple) volume control (right bottom corner).
PAVUcontrol is more complicated (in good way)
Is it correct ?
I think all 3 volume control software, PA, PAVUcontrol and jack are fighting for control right.
When i run pavucontrol; it shows up more audio nodes in jack and when i run PA, it also shows up more audio nodes in jack.. each PA and PAVUcontrol shows their own audio nodes in jack. .

I agree. Try to not use Jack. If you absolutely must use Jack (e.g. Qtractor) then stop PulseAudio and stop using PAVUControl. Unfortunately, PA is a pain in the neck and respawns itself after stopping it. I stop PA this way: uncomment the following 2 lines from /etc/pulse/client.conf:

Code: Select all

autospawn = no
daemon-binary = /bin/true

For newer Linux systems (i.e. Debian 10):

Code: Select all

systemctl --user mask pulseaudio.socket
systemctl --user stop pulseaudio

Then do the kill:

Code: Select all

pulseaudio --kill

Good luck

[Michael Willis]

At a glance I thought this said "Lost headphones in Peru" and I imagined some story about accidentally dropping headphones off a cliff at Machu Picchu.

[Linuxmusician01]

Just to clarify,
PA is the default (simple) volume control (right bottom corner).
PAVUcontrol is more complicated (in good way)
Is it correct ?

AFAIK unfortunately, no. PulseAudio (PA) is a "sound server" on top of ALSA. It enables one to have audio from more than one application at the same time. It's not simply a volume control. And yes, AFAIK, it can "fight" with Jack Audio in some cases.