[05:37] <MauroGaspari[m]> <MauroGaspari[m] "Audio on linux never gets boring"> OvenWerks: been doing some tests on 2 different installs on same desktop with same equipment, swapping SSDs. So it seems it is not a bug with US. Both my installs use same version. One is US 21.04 another UB 21.04 with Studio tools. US still has the issue. I can manually run alsactl restore after login and that puts my volumes back to normal, but will
[05:37] <MauroGaspari[m]> still mess those volumes every reboot. None of that happens on UB install, even if I try to recreate the issue, nothing gets wrong there.
[05:38] <MauroGaspari[m]> also OvenWerks is there a specific config file created by US for Alsa volumes? anything I can remove to try to reset to standard? Thanks!
[15:27] <OvenWerks> MauroGaspari[m]: It would be interesting to see if kubuntu has the same thing then. US should not have changed that part of things at all
[15:28] <OvenWerks> Eickmeyer[kde]: can you reproduce ^^^ ?
[15:30] <MauroGaspari[m]> <OvenWerks "Mauro Gaspari: It would be inter"> the funny thing is, I never did split my channels nor slide my volumes when the issue started. so I really have no idea how to reproduce the issue. sorry. 🙂ideas are welcome
[15:32] <OvenWerks> MauroGaspari[m]: There is no control to split the channel really. If they are exactly the same QASmixer shows them unsplit if they are different then split
[15:47] <OvenWerks> So what you are seeing is one side is not being set it appears. This could be a pulse problem I guess.
[15:50] <MauroGaspari[m]> OvenWerks: so what I did to preserve that install as is, I unplugged that ssd and I am currently using another one. if you guys think it is valuable to dig this out and make sure it does not affect others, I can plug the ssd back and test changes without much fear of breaking the install.
[15:53] <OvenWerks> MauroGaspari[m]: just a quick "this is how things work" When the system starts all alsa levels are at -inf (or whatever their lowest level is) The system runs alsactl restore to bring the levels up. Then as part of shutdown, alsactl store is run to save current levels.
[15:55] <OvenWerks> So it seems the system restore has done things wrong or it has used a command that should tell your HW to bring up the whole device level and the device has interpereted this as bring up the left.
[15:56] <OvenWerks> I am not sure how this could happen in one flavour and not another though as that part of things should not be unique.
[15:57] <OvenWerks> MauroGaspari[m]: maybe try an sudo alsactl store  and see if it reboots back to that state.
[15:58]  * OvenWerks thinks the system store/restore might use a different file than user does ...
[16:01] <MauroGaspari[m]> <OvenWerks "Mauro Gaspari: maybe try an sudo"> it does not, but if I manually run sudo alsactl restore after reboot, my volumes go back to normal
[16:01] <OvenWerks> so maybe a bad pulse audio profile. Which device is this? internal?
[16:02] <MauroGaspari[m]> so I know how to workaround it, just small command on login. but my purpose here is not to workaround a potential issue, but report it and see if we can figure it out, to help other users 
[16:02] <MauroGaspari[m]> it is an USB device. AT2020USB+ I use this for both input and output.
[16:03] <OvenWerks> of course, I was hoping to find out if the saved file was corupt or not being written or something. Not suggesting you fix it every reboot :P
[16:03] <MauroGaspari[m]> great, do you know where I should look?
[16:05] <MauroGaspari[m]> I found this post, but it is super old, and I am not sure if still relevant
[16:06] <MauroGaspari[m]> https://iainbuclaw.wordpress.com/2009/09/15/howto-save-and-restore-alsa-settings-on-startupshutdown/
[16:06] <OvenWerks> Well if you did an sudo alsactl store then the file should have been recreated.
[16:06] <OvenWerks> ubuntu has saved and restored alsa values for a long time
[16:10] <OvenWerks> MauroGaspari[m]: sudo nano /usr/bin/autojack
[16:11] <OvenWerks> look for line:524-ish
[16:12] <OvenWerks> it should say: time.sleep(2) maybe try 5 instead of 2 for testing.
[16:13] <OvenWerks> note this should be the first time.sleep(*) after: def config_start():
[16:14]  * OvenWerks is really not sure what the actual line numbers are because he is working on a much later version than you have.
[16:15] <MauroGaspari[m]> found it
[16:15] <MauroGaspari[m]> # if at session start we should wait a few seconds for pulse
[16:15] <MauroGaspari[m]>     # to be fully running
[16:15] <MauroGaspari[m]>     time.sleep(2)
[16:16] <OvenWerks> looks like line 484
[16:16] <OvenWerks> yeah
[16:17] <MauroGaspari[m]> got it, done and saved. will see how it works on reboot
[16:19] <MauroGaspari[m]> OvenWerks: by the way, in qasmixer i can join and split channels by right clicking on the volume knobs. just tried :)
[16:21] <OvenWerks> yup. but as I said, that is a GUI thing, ALSA it self doesn't link them, though I think it will set both channels if a channel is not specified
[16:29] <MauroGaspari[m]> OvenWerks: same, this is just after startup
[16:29]  * MauroGaspari[m] uploaded an image: (67KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/SjrDIGpUoGozyNTxKqaKfUvQ/qasmixer-startup.jpg >
[16:29] <MauroGaspari[m]> and this after I run sudo alsactl restore
[16:29]  * MauroGaspari[m] uploaded an image: (68KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/sVroFHOTPbPQMydOJeuoFdzL/qasmixer-alsactlrestore.jpg >
[16:31] <OvenWerks> ok it is not pulse then. noticing that it is the right channel that is correct and not the left.
[16:32] <OvenWerks> Normally channel 0 would be set first. This leads me to beleive that alsactl restore is being run before the USB device has fully settled/connected/module loaded/whatever
[16:35] <OvenWerks> the time difference is obviously very small because these setting are happening very quickly. This probably means that vanilla is busier on startup and this delays the restore operation just a bit.
[16:38] <OvenWerks> MauroGaspari[m]: you could test this idea by editing: /lib/systemd/system/alsa-restore.service
[16:38] <MauroGaspari[m]> OvenWerks: best to first restore the changes on autojack, to sorta try one thing at a time?
[16:39] <OvenWerks> you will find the line: ExecStartPre=/bin/mkdir -p /run/alsa
[16:39] <OvenWerks> MauroGaspari[m]: of course restore autojack first
[16:40] <OvenWerks> just before or after that line add another line:ExecStartPre=/usr/bin/sleep 1
[16:42] <MauroGaspari[m]> OvenWerks: got it. working on restoring autojack to default 2s sleep and adding delay to alsa restore
[16:58] <MauroGaspari[m]> victory! I think
[16:59] <MauroGaspari[m]> so changes to delay to alsa restore did not do much. so I restored to default
[17:00] <MauroGaspari[m]> I noticed as I was trying to do alsactl restore it complained about this file sudo rm -f /var/lib/alsa/asound.state
[17:00] <MauroGaspari[m]> so i deleted it, rebooted. and... ta dannn 
[17:01]  * MauroGaspari[m] uploaded an image: (54KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/QINnqNvycEhQrugvncjByrCF/qasmixer-new.jpg >
[17:05] <OvenWerks> so two alsactl restore at the same time :P
[17:06] <MauroGaspari[m]> it is a bit confusing because I had changed zero sound settings in the last... not sure since I installed 21.04 months ago lol
[17:07] <OvenWerks> seems like a bug with state-daemon ? or something.maybe an update changed things?
[17:10] <MauroGaspari[m]> <OvenWerks "seems like a bug with state-daem"> I would like to think so. Do you think it is valuable for me to run more tests and try to recreate it? or leave it for now and keep in mind if someone reports similar issue?