This problem was in the initial SL10 too.
Win 11 22H2 Build 22621.1992
SL10.0.10
If I leave the standalone version on screen and suspend the PC, when I resume the machine, all the menus etc still respond in SL10, but pressing PLAY results in nothing - no sound, no play cursor movement.
…further… After resuming the PC with a job on screen, if I just close the project (not SL10) then reload the project, play then works normally again.
This problem does not exist if I use SL10.0.10 ARA in Cubase 12.0.60. This combination survives the suspend/resume perfectly.
Why are you suspending the computer , this is one of the top DO NOT’s in the Daw world ? if devices sleep or get suspended some break the link and do not reconnect , i would personally say that Cubase and Ara working ok was more Luck than feature , Cubase has the Steinberg power manager , maybe you need to manage your windows power scheme for Audio work
SpectraLayers has a slightly unusual relationship with the audio hardware in that the endpoint connection is only active when playing not when stopped, which isn’t how all audio software behaves and can cause issues when woken from a sleeping USB port especially, but I suspect because the computer has put the port to sleep you might need to override the computer being able to do that. Depends on where your audio device is connected, but it will look something like this usually in device manager when you right click on the ports/hub it’s connected to. Make sure power management is not checked for the hub:
You also want to disable suspend in your power profile if possible.
This should allow your computer to enter Sleep mode to save power when not using it, but still awake and your audio interface be findable by SpectraLayers. That’s always worked for me anyway.
1 Like
Yeah I get that. I did it by mistake and noticed that ARA SL10 in Cubase survived with no problem at all, wehereas SL10 standalone didn’t.
Perhaps this is useful info for the developers and might point to something which can be improved to increase the robustness of the app in other ways. That’s all.
Not recommending suspending DAWs 
Yeah, I’ve had my computer optimised for audio for decades
The internet is a weird place. You make a comment about an unusual occurence and people assume you know nothing.
Then why ask the question if you knew what the cause was ?
Is it a problem if you knew that suspension isn’t the done thing ?
As I already said…
Perhaps this is useful info for the developers and might point to something which can be improved to increase the robustness of the app in other ways.
