[22:38] <n4dir> hi there. I got no more sound for my external speaker. I had the problem earlier, it seems to come and go, but i don't know how to troubleshoot it.
[22:38] <n4dir> same is valid for the headphone if i plug it in. Internal speaker works.
[22:49] <n4dir> i created another user, works for him. Now how to figure out which setting is wrong?
[22:59] <OvenWerks> n4dir: Do you have a more complete description of what is happening?
[22:59] <OvenWerks> is jack running?
[22:59] <OvenWerks> sound from what application?
[23:00] <OvenWerks> how are the interanl and extrernal speakers hooked up?
[23:00] <OvenWerks> (to which which audio interface)
[23:14] <n4dir> OvenWerks: jack is running, but the same is valid if it is not. The internal speaker is from the laptop, the external is plugged into the laptop.
[23:15] <n4dir> the funny/weird thing is that it happens after reboot, it worked, so i didn't change anything. And it also started to work again without much input from me
[23:15] <n4dir> this is 2 or 3 days in a row now. Stops working, starts working again.
[23:15] <n4dir> pavucontrol says "no soundcard available".
[23:16] <n4dir> i guess that is still too vague. sorry for that. pretty new to audio stuff.
[23:17] <n4dir>  i usually use mocp to play audiofiles. i tested vlc, but it had the same problem. pavucontrol showed via volume meter there is output,  but i heard nothing, as said.
[23:17] <n4dir> else i tried to get the head into zynaddsubfx and ardour.
[23:21] <OvenWerks> n4dir: if pavucontrol says "no soundcard available" that is a good indication jack is running.
[23:22] <OvenWerks> unless jack has crashed
[23:22] <n4dir> ok, got that.
[23:22] <n4dir> as in: i wasn't sure about it until now
[23:22] <OvenWerks> ubuntustudio controls unloads pulse's alsa  modules when it starts jack and then bridges pulse to jack.
[23:23] <n4dir> ok.
[23:24] <OvenWerks> when jack is not running pulse should show the devices
[23:24] <OvenWerks> when pulse sees the device, switching from one device to the other will be automatic.
[23:24] <n4dir> i stopped jack with qjackctl, lots of back and forth, but i am quite sure that pavucontrol didn't show "soundcard" after stopping jack.
[23:25] <n4dir> which it sure did in the past
[23:25] <OvenWerks> if you start jack with -controls that is how you should stop it too.
[23:25] <OvenWerks> qjackctl does things differnt
[23:25] <n4dir> sorry, i don't understand that.
[23:26] <OvenWerks> if you use ubuntustudio-controls to start jack then that is also the way you should stop jack
[23:26] <OvenWerks> otherwise pulse will not get reset
[23:26] <n4dir> ah, i see. I didn't use ubuntustudio-controls
[23:26] <OvenWerks> ok
[23:26] <n4dir> but it is either the one or the other. not mixing both methods
[23:27] <OvenWerks> right
[23:27] <n4dir> ok, thanks
[23:27] <OvenWerks> in alsamixer which devices do you see?
[23:28] <OvenWerks> I should ask in a different way...
[23:28] <OvenWerks> aplay -l
[23:28] <n4dir> HDA Intel Mid ? (yeah, probably a different way). ah, ok
[23:29] <OvenWerks> shows what?
[23:29] <n4dir> a second, quite some output i will pastebinit
[23:29] <OvenWerks> aplay -l |pastebinit
[23:30] <n4dir> https://paste.ubuntu.com/p/thd6FBwd6f/
[23:31] <OvenWerks> ok so just one audio card.
[23:32] <OvenWerks> amixer -c 0 scontrols |pastebinit
[23:32] <n4dir> https://paste.ubuntu.com/p/MHHdgY8GnP/
[23:34] <OvenWerks> so the internal speakers use the speaker level control and the external is Front?
[23:35] <n4dir> sorry, but i really don't know. Usually i plug in the external and that makes the internal silent. And the other way around.
[23:35] <n4dir> to raise or lower the volume i just use "master"
[23:36] <OvenWerks> have you ever opened alsamixer?
[23:36] <n4dir> but yes, external seems to be front
[23:37] <n4dir> yes, but only ro change the volume by usin "master"
[23:37] <OvenWerks> in alsamixer when you plug and unplug things the levels and mutes for those plugs should change
[23:38] <n4dir> the "speaker" of alsamixer doesn't change. i can't change it
[23:38] <OvenWerks> when you plugin the phones the phone level should go full and the mute should go off
[23:38] <OvenWerks> if it a full level control or just a switch?
[23:39] <OvenWerks> can you give me a screen shot?
[23:39] <n4dir> of alsamixer?
[23:39] <OvenWerks> ya
[23:39] <n4dir> give me a bit
[23:41] <n4dir> OvenWerks: https://postimg.cc/nsG5f1GS
[23:42] <OvenWerks> ya the speaker is just a mute button if you move to it and hit m you shoud get sound.
[23:43] <OvenWerks> same with headphones I see. phones are not muted right now.
[23:44] <OvenWerks> you have a different setup than I have seen before. Good info.
[23:44] <OvenWerks> (for me)  ;)
[23:45] <n4dir> so i probably hit "m" by confusion, and also i hit "m" by accident to make it work again. Which is less unusual than it may sound. switching windows in "screen" i use "n", which is quite close
[23:45] <n4dir> OvenWerks: this should be pretty much the way it was from the beginning. I installed a few days ago, perhaps 1 or 2 weeks
[23:46] <OvenWerks> do you have devices in pavucontrol right now?
[23:46] <n4dir> no, but let me look again.
[23:46] <n4dir> no
[23:47] <OvenWerks> I have a long command all one line...
[23:47] <OvenWerks> cd /tmp && wget https://community.ardour.org/files/adevices.sh && bash ./adevices.sh |pastebinit
[23:48] <OvenWerks> That will let me see if something else is using the audio
[23:48] <n4dir> https://paste.ubuntu.com/p/spG684c7Wc/
[23:49] <OvenWerks> so jackdbus is running
[23:49] <OvenWerks> cat ~/.config/autojack/autojackrc |pastebinit
[23:50] <n4dir> https://paste.ubuntu.com/p/cCjThkFfFz/
[23:51] <OvenWerks> open ubuntustudio-controls go to the audio setup tab and hit "Stop jack" at the bottonm
[23:51] <n4dir> ok, stopped
[23:52] <OvenWerks> pavucontrols shold show devices now.
[23:52] <n4dir> in case ... yes, it does show it.
[23:53] <OvenWerks> ubuntustudio-controls remembers the last command about jack so if it is running when you reboot it will still be running next time you boot up
[23:53] <n4dir> OvenWerks: assuming i hit the mute "m" in  alsamixer, it should create the problem for both, pulse and jack, right?
[23:54] <n4dir> or might it be the problem is what you just said?  (i had a quick look at ubuntustudio-controls, not sure when)
[23:54] <OvenWerks> possibly, but also if jack is started in ubuntustudio-controls and then stopped /started from qjackctl that would cause trouble as well
[23:54] <n4dir> and said earlier, mixing qjack and ubuntustudio-controls.
[23:55] <n4dir> ok, one last question, hoping this problem won't occur again (at least i will have learned a bit to troubleshoot):
[23:55] <OvenWerks> The last paste showed that ubuntustudio-controls had started jack and thought it was running
[23:55] <Eickmeyer[m]> Moral of the story: don't use qjackctl. It's outdated and cumbersome.
[23:55] <OvenWerks> the long line showed that jackdbus was running
[23:56] <n4dir> would you advice me to rather use ubuntustudio-controls instead of qjackctl ... the question was answered already :-)
[23:56] <Eickmeyer[m]> n4dir: It's built to *replace* qjackctl in functionality and be easier to use, so yes, absolutely.
[23:56] <OvenWerks> n4dir: also, any profession audio program (like ardour with the alsa back end) will block the device from other uses untill exit
[23:57] <n4dir> how would i "route" devices like the midi-keyboard in ubuntustudio-controls ?
[23:58] <Eickmeyer[m]> n4dir: That's why Carla is linked. Use the patchbay tab in Carla.
[23:58] <OvenWerks> n4dir: right now auto switching from internal to extren speakers to headphones does not happen while jack is running.
[23:59] <OvenWerks> the next version of studio-controls does... I am not so sure about the speaker thing though :) That will take some thought.