[14:59] Eickmeyer: I don't know if you have used the headphones functionality of controls, but from what I can see I have set it up wrong. [15:00] OvenWerks: I haven't, my headphone jack on my audio interface is tied to outputs 1/2 or 3/4 using an A/B switch. [15:00] Right now it is set up to always be ports 1 and 2 on a device. [15:00] I think it should be set up like the main outs [15:00] It should, in most cases. [15:01] The switching between speaker/headphone should be done on the ALSA side, Jack shouldn't know any better. [15:01] Eickmeyer: for internal headphones, it is [15:01] Yeah. [15:02] but the internal device may not be system [15:02] I see. [15:02] Because system is set to Jack Master. [15:03] That is, the user should be able to use a USB device for mains and then plugin their phones to the computer and the output should switch to PCH,0,0-out_1 and 2 [15:04] if that is the device that is phones. or use the sound on their computer for main and plug a second usb phones in and have audio switch [15:04] This works if the output ports are 1 and 2 [15:06] Right. I don't know why ALSA doesn't automagically do it in the first place. Seems like Pulse does something when directly connected to ALSA. [15:06] However, as in your case, the phones could be 3/4 (or 9/10 in others) and then the manual phones switch should still work. [15:07] Yes pulse does and we do too. We mute mains (in two ways just in case) and unmute phones (in two ways just in case) [15:08] We also provide a scriptable switch method for those laptops that require something else [15:09] (I have one as happens, but from research they are all different) [15:33] Eickmeyer: So, I think phones will have to be stored as jackport and the device will have to be plugged in and active just to set it up... or I will need two fields, one for device and the second for ports. [15:34] Seems like this gets more complicated every time we look at it. [15:35] not really, I think it was just over simplified to begin with === snd is now known as snd1 [15:36] I really only considered two uses: internal and USB phones. Both of which are easy to handle. However, I have provided manual switching for cases outside of those two. [15:37] and having provided that manual function (from the beginning), it should work in a useful manner [15:37] I see. [15:39] In fact, I think really, this would be a case for studio-controls -p to just switch phones and exit so it could be tied to a global hot key. [15:40] or to add to the utility I gave you for systray [15:47] Eickmeyer: are you using controls-cl as the name? If so, I think I will expand it and include it in studio-controls [15:48] TBH, I haven't started working on it yet. I've been super busy with kubuntu focus. We've got the 4th generation laptop we're trying to get out the door, and it requires 22.04. [15:49] so I could rename it to studio-cmd? [15:49] Yeah, that'd work. [15:49] Nothing you can do now would break anything for me [15:56] Ok, I will pull it into -controls under studio-cmd (as less likely to conflict with other packages) and add phones. If you ever do a systray applet, adding phones might be nice. [15:57] I will set it up so it takes phones or no-phones rather than switch to whatever it is not. I will make the same change in -controls [16:36] Eickmeyer: in the error tracker, what does the uec-images tag mean? [16:37] uec-images? I'm not familiar. [16:39] It is the only permission denied I get for a real user. [16:41] Best I could find, so I wouldn't worry about it: https://help.ubuntu.com/community/UEC/Images [16:42] running on cloud not supported :) [16:42] Indeed. XD [17:14] I think I will check for a few things on startup. User 0, user < 1000, do I have write permission for config and log, etc