[01:03] <Eickmeyer> Uh... yeah. heh
[01:10] <Eickmeyer> OvenWerks: Got something fun: bug 1888588
[04:45] <OvenWerks> Eickmeyer: after reading: https://wiki.pine64.org/index.php?title=PinePhone_v1.1_-_Braveheart
[04:45] <OvenWerks> I don't feel so bad
[04:47] <OvenWerks> Eickmeyer: I think the bugs I have already deal with that too... but I will add that to the list.
[04:56] <Eickmeyer> OvenWerks: Honestly, the amount of bugs in SC isn't so bad considering.
[05:19] <OvenWerks> at least one of them has been there since fist release :)
[05:20] <OvenWerks> it takes people really using it to point some of these out
[05:25] <Eickmeyer> Exactly, which is why I wasn't shying-away from doing a release.
[05:50] <OvenWerks> can we remove notes.txt? I think changelog covers it.
[06:04] <OvenWerks> I think I will default phones device to none.... unless I can find an easy way to detect what internal audio is called (INTEL, PCH, GENERIC, etc.)
[14:24] <OvenWerks> Eickmeyer: My work with the firewire stuff and other complex audio devices, has convinced me that the way alsa presents mixer controls is not very good. Alsamixer does not even show all controls if there are more than 9 channels and on top of that present those first 9 as 3 stereo sets and 3 mono channels. Alsamixer also is not able to group more than 2 sets of controls per channel, level 
[14:24] <OvenWerks> and mute.
[14:27] <OvenWerks> QASMixer is better in that it does show all the controls at least and it does not group a set of controls in bits of stereo and mono. (it will gang the whole group of 12 or whatever controls though)
[14:33] <OvenWerks> But QASMixer is hard to navigate when there are a lot of controls for a device.
[14:36] <OvenWerks> All that to say... one of my next projects will likely be studio-mixer... which may be a fork of qasmixer or not depending on the toolkit I use for the GUI.
[14:39] <OvenWerks> I expect that where the device allows it will have mixer strips that gather all strip controls in one strip. If meters are available they will be included too.
[15:44] <Eickmeyer> OvenWerks: re: notes.txt, sure.
[15:44] <Eickmeyer> studio-mixer sounds interesting. I'm sure there would be a ton of benefit to that.
[21:32] <OvenWerks> Eickmeyer: controls 2.0.1 pushed (you can change that to 2.1.0 if that works better) Take a look.
[21:32] <Eickmeyer> Nah, 2.0.1 is fine.
[21:33] <OvenWerks> 5 items in the change
[21:39] <OvenWerks> Eickmeyer: I haven't tagged
[22:17] <Eickmeyer> I tagged. Building the package for upload now.
[22:18] <Eickmeyer> BTW, Focal builds are fixed.
[22:40] <OvenWerks> I saw that, how soon to the pont release?
[22:49] <Eickmeyer> A week or two.
[22:52] <OvenWerks> good that it works then
[23:27] <Eickmeyer> Yeah, I'd been bugging the release team about it for some time. The problem was caused by me adding linux-lowlatency to lowlatency-settings recommends, but they found a way to keep that from being a problem in the future.