[00:16] <Eickmeyer> OvenWerks: Cool!
[00:22] <OvenWerks> Eickmeyer: I have one problem... I can detect when HP are plugged in, but not if they are plugged in at startup
 here's a question: is there even a mechanism that could be used to DETERMINE if it's plugged in or not at startup
 because I know there's system-level detect triggers for "new device plugged in" during initial handshakes to make it work
 but not sure if there's an exposed flag or such to that end that indicates 'connected' at boot, at least at a way you'd be able to do it easily
 'course you guys know more about it than I do :)
 *lurks more*
[00:24] <OvenWerks> Eickmeyer: I am also wondering if I should monitor anything that gets connected to the speaker output and auto reconnect that to the hp device (if they differ)
[00:25] <OvenWerks> teward: yeah, I can find a one line difference in /proc/asound/PCH/codec#0.
[00:28] <OvenWerks> The only problem is if it is there in the same place on all (or even most) systems
[00:29] <Eickmeyer> @teward001: Yeah, HP = headphones, and that gets reported by the hardware weirdly.
[00:35] <OvenWerks> so Control: name="Front Playback Switch" has Pin-ctls: 0x00: that changed depending on plugged...
[00:35] <OvenWerks> but: Control: name="Headphone Playback Switch" does not change :P
 Eickmeyer: yep, it does 😜
 'course... depending on the headphones, mine're USB-C and probably aren't going to get reported right anyways XD
 *shot*
[00:37] <OvenWerks> Actually, I can deal with USB headphones
[00:37] <Eickmeyer> @teward001: It's been something we've been working on for quite some time. Users are reporting difficulty when they have Jack running and want to use their headphones: nothing is switching it.
[00:37] <Eickmeyer> @teward001: USB headphones are easier to deal with.
[00:37] <OvenWerks> if the device exists... usb headphones are in :)