[13:31] <rgh> hi
[13:32] <rgh> if I store my alsa mixer settings with `sudo alsactl store` everything seems to be saved but not my headphone switch
[13:34] <rgh> anytime I reboot ( and start/stop jack I noticed) the Headphones toggle in alsamixer/qasmixer are muted
[13:52] <rgh> oh, it's a pulseaudio thing it seems
[14:38] <OvenWerks> rgh: PCH headphone "plug state" is a hardware based state that pulse reads and "does something with" before studio-controls takes over. Studio-controls should also read that state and it should be able to leave both speaker and HP turned on via scripts at startup if that is what you want.
[14:41]  * OvenWerks would be hard pressed to think exactly how that would be done from CLI at the moment
[14:43] <rgh> OvenWerks: the plug state only works with jack stopped
[14:45] <OvenWerks> rgh: which sounds like a bug or a setting thing. HP device has to be pointed at the internal device of course
[14:47] <OvenWerks> rgh: also, the HDA bus spec does not cover some of these things very well and in any case HW designers do wierd things too.
[14:47] <rgh> It's a minor inconvenience. 
[14:48] <OvenWerks> on top of that, Linux tends to change what it does on plug unplug events as well
[14:48] <rgh> My kids already learned how to open qasmixer, select correct hw device and toggle the box. 
[14:48] <OvenWerks> :)
[14:48] <rgh> He's 10 
[14:48] <rgh> Linux is hard... Sure 
[14:49]  * OvenWerks would be lost trying to figure the same thing out on windows or mac
[14:51] <rgh> Selecting the input of your soundcard in windows is a frikking nightmare 
[14:51] <rgh> But I guess windows people feel the same about linux. 
[14:58] <OvenWerks> I rememeber a friend coming to record a song of his with his win10 laptop. The machine would not even see the USB 2.0 device. We ended up using my old 32bit laptop with jack and Ardour...
[14:58] <OvenWerks> The device was his not mine BTW
[15:01]  * rgh does some practice programming
[15:01] <rgh> TIL: when you feel smart and smug, try dynamic programming ...
[15:01] <rgh> that'll teach ya
[18:19] <rgh> New reverb 
[18:19] <rgh> https://github.com/Dougal-s/Aether/releases/tag/v1.0.0
[19:25] <YannMonnier[m]> Hi, I am working with Blender. What does Ubuntu Studio do more than Ubuntu 20.04 regarding Blender? For example, on 20.04, I am having a headache on Blender as my render is done with my CPU ... Instead of Blender using my amd-gpu with opencl. Does Ubuntu Studio has this fixed?
[19:32] <YannMonnier[m]>  * Hi, I am working with Blender. What does Ubuntu Studio do more than Ubuntu 20.04 regarding Blender? For example, on 20.04, I am having a headache on Blender as my render is done with my CPU ... Instead of Blender using my amd-gpu with opencl. Does Ubuntu Studio have this fixed?
[19:41] <tomreyn> YannMonnier[m]: hi there. both Ubuntu and Ubuntu Studio share the same foundation, and (for the most part) software repositories.
[19:42] <tomreyn> i.e. the blender packages are likely identical, unless they're from a Ubuntu Studio specific PPA.
[19:44] <tomreyn> i think the shortcoming that the Blender packages in 20.04 LTS don't support OpenCL hardware acceleration is really due to this Blender version not supporting it, yet.
[19:47] <tomreyn> The usually well maintained Arch Linux wiki at https://wiki.archlinux.org/title/Blender#Troubleshooting says "Blender only supports the official AMD proprietary drivers for rendering with OpenCL, meaning you will need to install one of the [proprietary] AMD OpenCL drivers"
[19:49] <tomreyn> Blender's documentation says "AMD drivers are open source, except for the OpenCL support which is available as part of Pro drivers." - which is only part of the story, since there is also mesa-opencl-icd