All sound control functions die on awake from sleep

[GalaxyXYZ888]

Describe the bug:

After awaking from sleep, the sound control stops working and i have to restart the software, closing it in tray and opening again. Meaning, there is lights, if i move the knobs the bars appear with the correct apps and show the volume changing, but the volume does not change at all, every volume, the ones set to focused app and also the ones connected to specific apps.

Steps to reproduce:

Let windows sleep and wake up again.

Expected behavior:

It should resume normal behavior.

Additional context:

I am using windows and the latest version of the software and lunching it on startup with privileges using the Task Manager method.

[nvdweem]

Thanks for the report. Yhis looks like a bug that was fixed after 2.0.90 went out, it should have been included in the latest snapshot

Could you try the latest snapshot build, 2.0.91-snapshot (105), and let me know if it still happens? I've tried it myself and it kept working, but I usually don't let my pc sleep.

If it's not fixed, a few more questions:

1. Which version number is shown at the bottom of the window?
2. When it's in the broken state, do your buttons still work for non-volume things — does the ui still update, a keystroke, a media key, switching profiles, OBS?
3. When it's broken, open the app, edit a dial, and open the list where you pick an application. Does the list fill in, or does it keep loading?
4. Does it ever start working again on its own if you leave it, or only after you restart the software?
5. Is it full sleep or does the machine stay half-awake? And do you have a USB headset, DAC or receiver that switches off with it?

[GalaxyXYZ888]

Thanks for the report. Yhis looks like a bug that was fixed after 2.0.90 went out, it should have been included in the latest snapshot

Could you try the latest snapshot build, 2.0.91-snapshot (105), and let me know if it still happens? I've tried it myself and it kept working, but I usually don't let my pc sleep.

If it's not fixed, a few more questions:

1. Which version number is shown at the bottom of the window?

2. When it's in the broken state, do your buttons still work for non-volume things — does the ui still update, a keystroke, a media key, switching profiles, OBS?

3. When it's broken, open the app, edit a dial, and open the list where you pick an application. Does the list fill in, or does it keep loading?

4. Does it ever start working again on its own if you leave it, or only after you restart the software?

5. Is it full sleep or does the machine stay half-awake? And do you have a USB headset, DAC or receiver that switches off with it?

Thank for fast answer. I tried the snapshot and i am having the same problem unfortunately.

So:

1. v2.0.91.105
2. apparently no. I dont switch profiles much but indeed stop working too.
3. The list fills in normally
4. I am not sure but i think only after restart
5. Windows normal sleep, fans, lights and etc off but i click in keyboard or mouse movement and it comes back. Sleep(S3). Right now i only have a wireless charger connected to the keyboard USB, keyboard, mouse, mouse wireless 2.4Gh receiver and Headphones connected to case font jack.

For context i was using an older version of the app that still had the app version and not the browser version and updated from that which was working fine. Updated not reinstall.

If you need more information pls ask.

[nvdweem]

A v2.0.91 release is building currently. I noticed a similar issue when I disconnected my headset, so that should be fixed. It might be issue that causes your problems, but it might also not be.

If it triggers on this version again you can generate a report bundle.
You can generate that by clicking the bug icon in the ui (put some random text in the What went wrong field, click Continue on Github, then close the new-github-tab), a file-explorer window should open in the PCPanel report directory holding the reports.

[GalaxyXYZ888]

After some early testing it seems to be solved!

[nvdweem]

Sounds great. I'll leave the ticket open for now in case it fails again. Might close it after a while.

Let me know if it triggers again.