Here’s my second post concerning a provable, reproducible issue that goes into ignore mode by Steinberg development. (There will be more.)
If I have Cubase 10.0.40 open on one of my two Windows 10 build 1809 or 1903 machines, it completely defeats all power saving features. If Cubase is open I get no screen saver, no screen power off, no sleep, no hibernation.
I’ve confirmed this problem on two machines. One is my primary DAW and has been updated with every patch in the Cubase 10 lifecycle. The other is a less exotic PC where I installed v10.0.40 fresh and clean. The problem exists on both without me touching any Windows power settings and without engaging the Steinberg power scheme.
Shall I describe why this sucks?
OLED screens can suffer from burn-in, and this will certainly add to the likelihood of you burning that new and expensive monitor.
Also, I often walk away from a long session and return much later. I’d like my power savings features to engage UNLESS I tell it not to. Specifying power features to not engage can be accomplished either through Windows power settings via Control Panel or inside of Cubase with the “Steinberg Audio Power Scheme”. (This is accessed through: Studio > Studio Setup > VST Audio system > “Activate Steinberg Audio Power Scheme”)
As I said, I’m not touching either option, but Cubase dictates control, not me. This condition can’t be defeated.
Support was called and wants to help, but couldn’t. Support reached out to Steinberg HQ and they offered only this response:
“Double checking with the main office. There are no settings that should affect power settings on the computer.
There is actually a setting in Cubase to turn on high power mode on the computer (Activate Steinberg Power Scheme), however if that is not enabled then it should not be affecting the ability for the power saving settings such as a screen saver to turn on.”
NOT HELPFUL MAIN OFFICE. It’s reproducible on two independent machines, so it certainly is causing the issue. I can reproduce it freely and at will. I continue to be disappointed on the lack of debugging when an issue is real and is not simple user confusion or something that can be overcome with a config change.
I know, I know, just remember to close Cubase before walking away. Or…turn off the monitor to avoid the burn-in. There’s a workaround for many issues. I’m sick to death of having to manage all of them. The software should not dictate policy when it’s positioned to not be the expected behavior.
Anyone else care about this issue?