I understand that Dorico and Cubase are designed to prevent Windows from going into Sleep Mode (I’m using Windows 11). Is there any danger to Dorico’s operation if I MANUALLY put Windows 11 into sleep mode?
I understand that the audio engine connection can be broken, but all that one has to then do is go to Device Setup and re-select the proper settings. Is this correct?
To put things into a different light: Yes, Cubase on purpose prevents the app from going to sleep. Imagine you are in a long term recording and while you are recording the app goes suddenly to sleep…catastrophic.
That’s why Cubase prevents the app from going to sleep.
Now, Dorico’s audio engine is based on that of Cubase and shows the same behaviour, even though in the Dorico use case it is not strictly necessary to be like that.
But you can put them into sleep mode by hand, of course. And upon wake up everything should be like it was before.
It is worth trying out yourself.
Hello again, Ulf.
I am revisiting this issue almost two months later, and have a question for you about it, please.
A day or two before this particular post (about Cubase and Dorico preventing windows sleep mode, so as to prevent disruption during recording, etc), I had written to you about problems I was having getting Dorico 3.5 to properly connect with my old MOTU 2408 mk3 digital audio interface, and its drivers – here is an excerpt from that post (Unprovoked Device Setting changes in new system) :
. . . every once in a while, immediately after booting up Dorico, I suddenly find that there is no sound – despite the fact that I have perfect sound when playing other sound sources (local recordings, YouTube, etc). The first time this happened, I saw that my MOTU console settings were absent (sound resumed when I re-filled them). This morning, the Device Setup window’s slot for Stereo Output was blank – even though the Asio Driver slot was correctly filled (“MOTU PCI Asio”). The only way that I was able to fix this was to choose an incorrect Asio Driver (“Generic Low Latency ASIO driver”), which somehow ‘shocked’ things in a way that I could then choose the correct Stereo Output option from the scroll-down window, while also inputting the correct ASIO Driver slot info.>
Via a Dorico diagnositc report, you saw that Dorico was confusing input and outputs. I believe that you were then going to ask me to let Dorico replace the file responsible for that behaviour, but it happened that, without my doing anything, the problem never recurred (and still hasn’t).
But re-reading both posts, it now occurs to me that putting my computer into sleep mode MANUALLY (as you suggest) might provoke that old problem into recurring. Somehow, it seems that – in my situation, in which I am using old MOTU hardware and drivers – disconnecting the audio engine might be what then causes the miscommunication between Dorico and the MOTU.
Am I on the right track here? If so, I am thinking that the safest way forward would simply be to make sure that Dorico is closed whenever I ever want to put my computer into sleep mode. Your opinion on this?
Many thanks, Ulf!
I have a MOTU interface that I use to connect my powered monitors, and it loses connection almost every time I put the system to sleep. This happened even with Finale, so I’m guessing it’s a MOTU issue more than Dorico.
Yes, that is my hunch as well – or, let’s say – it is something that happens when Dorico comes out of sleep mode and tries to communicate with the MOTU (which, in my case, is old, with an old, Windows 8 driver). I posted this question for Ulf to see if this is most likely the case.
Thanks for the feedback. 
Hi @thinkingMusic.ca,
making sure that Dorico is closed before putting your computer to sleep is certainly the safest strategy, yes.
And even though old, but you could also check if there is maybe a driver update available from MOTU.