[14:59] <OvenWerks> 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] <Eickmeyer> 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] <OvenWerks> Right now it is set up to always be ports 1 and 2 on a device.
[15:00] <OvenWerks> I think it should be set up like the main outs
[15:00] <Eickmeyer> It should, in most cases.
[15:01] <Eickmeyer> The switching between speaker/headphone should be done on the ALSA side, Jack shouldn't know any better.
[15:01] <OvenWerks> Eickmeyer: for internal headphones, it is
[15:01] <Eickmeyer> Yeah.
[15:02] <OvenWerks> but the internal device may not be system
[15:02] <Eickmeyer> I see.
[15:02] <Eickmeyer> Because system is set to Jack Master.
[15:03] <OvenWerks> 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] <OvenWerks> 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] <OvenWerks> This works if the output ports are 1 and 2
[15:06] <Eickmeyer> 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] <OvenWerks>  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] <OvenWerks> 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] <OvenWerks> We also provide a scriptable switch method for those laptops that require something else
[15:09] <OvenWerks> (I have one as happens, but from research they are all different)
[15:33] <OvenWerks> 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] <Eickmeyer> Seems like this gets more complicated every time we look at it.
[15:35] <OvenWerks> not really, I think it was just over simplified to begin with
[15:36] <OvenWerks> 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] <OvenWerks> and having provided that manual function (from the beginning), it should work in a useful manner
[15:37] <Eickmeyer> I see.
[15:39] <OvenWerks> 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] <OvenWerks> or to add to the utility I gave you for systray
[15:47] <OvenWerks> 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] <Eickmeyer> 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] <OvenWerks> so I could rename it to studio-cmd?
[15:49] <Eickmeyer> Yeah, that'd work.
[15:49] <Eickmeyer> Nothing you can do now would break anything for me
[15:56] <OvenWerks> 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] <OvenWerks> 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] <OvenWerks> Eickmeyer: in the error tracker, what does the uec-images tag mean?
[16:37] <Eickmeyer> uec-images? I'm not familiar.
[16:39] <OvenWerks> It is the only permission denied I get for a real user.
[16:41] <Eickmeyer> Best I could find, so I wouldn't worry about it: https://help.ubuntu.com/community/UEC/Images
[16:42] <OvenWerks> running on cloud not supported :)
[16:42] <Eickmeyer> Indeed. XD
[17:14] <OvenWerks> 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