And what is your rant based upon? Assumptions.
Sure it is! Says it right there in the title, and itās tagged as an issue. See? Bug Report.
Not helpful.
Again, not really that helpful, but 
Snarky and not helpful. (2 points for that)
Thatās a totally ridiculous statement.
Also, not helpful.
I work as CISO and from an information security perspective this is definitely a problem.
If in our company Cubase would be installed on a computer that holds information that is classified as top assets, it would immediately pop up as a high risk at the risk assessment, resulting in a ban on that computer. If there is a strong requirement to have a DAW on that computer, it will be replaced by another software product. Risk management and mitigation is highly customer dependent. There are other measures like separating the information, implement physical measures, additional technical counter measures or having regular awareness trainings in place that people learn to lock their computers as soon as they are afk.
Top assets are information that have high ratings regarding confidentiality, integrity, availability and cost of replacement. I guess in most music studios the tracks/recordings from clients are considered as top assets and demand an appropriate protection. As long as most music studios work on best-effort regarding information security, I guess Steinberg can remain on the current implementation. However, nowadays the aspiration on information security management in a structured way will increase and Steinberg needs to comply.
I noticed this behavior at home as well but ignored it so far, as I have physical measures in place as well (doorsā¦) and conditioned myself to always lock computers. The only damage I would have, if my music would e.g. leak into the internet, is maybe embarrassment that people hear my unfinished musicā¦
The availability of computer systems is also an important aspect of information security and here license management systems are a major concern. Perpetual local licenses, dongles, cloud licensing, etc. Another can of worms and heavily discussed in this forum already.
But to summarize. Steinberg needs to cope with the raising demand on information security in a transparent way, so that it is clear, that the lock screen will be disabled when Cubase is open.
1 Like
Iām going to post another unhelpful post , we all should know that Dawās require the least interrupts as possible to work efficiently and with the Daw in an open state all other programs behaviours should be on hold due to the priority of audio , this is by design , as others have told you ,this is not a bug or an issue , this is the way it is with Cubase .
Why donāt you retitle your topic as feature request or do you like the click bait and all the unhelpful remarks about your requirement ? It is not an issue , it is by design . The issue is your work flow falls outside the standard workings of Cubase so why not ask for the feature to help with your work flow .
1 Like
Lock screen doesnāt get disabled. Try it yourself.
Windows+L still works, and you can set your safety settings with group policies.
To say something makes it not true.
If there is no bug, itās not a bug report and user error is not a bug, btw.
If you set the right things, it is possible to enable screen savers and automatic lock screen with Cubase.
Itās not recommended, but still possible.
So where is your bug again?
You donāt really understand how an event-driven operating system works, do you? Thatās pretty much all of them. Sure, you can request that the OS raise the priority of a program manually, but thatās really all it is: a request. The only reasons DAWs work effectively today with all of their capabilities is because of the speed of the processors, proven by the fact that when you try to run one on an old computer, performance suffers, dropouts occur, users get frustrated, etc.
Plus, if you really cared to understand the issue here, youād know that this behavior occurs also when Cubase in minimized, and in fact, even if a project is never opened. There is absolutely no reason for this, and no other DAW Iāve ever used behaves this way. Hereās an example. I just set my monitors to turn off, and my computer to auto-lock, after 1 minute. I opened Cubase (no project, just Cubase) and waited several minutes. Nothing.I closed Cubase and waited. One minute later, my monitors went into power-save mode and my computer was locked. Oh, and all the while Iāve had a Reaper project open with a TON of plug-ins active on many tracks. It didnāt seem to mind at all, and I have absolutely NO performance issues. Youāre argument is as wrong as it is weak in defending this behavior. If it is indeed āby designā as you say, then it is a design flaw by any reasonable SW Engineering/Security standards. And your argument is made even more absurd by the fact that Cubase actually provides an option to the user to Release Driver when Application is in Background for the audio system.
Iām sorry, but I donāt consider it a feature for a program to, without asking or informing, change the security profile of my workstation. Neither would any of the Fortune 100 companies for which the division I previously ran managed IT infrastructure. Cubase wouldnāt be allowed anywhere near their systems. Iām a little surprised big name producers appear to ignore this issue, as data theft could be very costly and damaging to a reputation. Hopefully they have the best physical security in place and trustworthy employees.
Wrong, in the context of this discussion.But you already knew that (or would have if you had actually read the thread).
To which settings. are you referring, exactly?
Yet here you are telling me something Iāve said is not trueā¦ by saying it. 
Then please show us how, step by step. Iād be interested to know what Iāve missed. Iāll even mark your helpful comment as the SOLUTION. I eagerly await.
You obviously have a chip on your shoulder for Steinbergs handling of a 35 year old profitable DAW so i suggest using something else . Im out of your click bait
1 Like
Running Cubase 12 on a 1st gen i7-950 X58 (Windows 10) with a firewire interface. Performance is starting to suffer (but, I have my āworkaroundsā). Dropouts never occur. I donāt get frustrated.
I probably donāt run my DAW with all of itās ācapabilitiesā, though! 
I assume the workstations you deal with are configured to automatically lock after some time of inactivity. So was the case for us (I worked in the military) However someone found out rather soon. that playing an .mp3 (loop and muted with the player in a mininized state) prevented the computer from locking ā¦
And IT security was taken serious ā¦
oh, thatās badā¦ and yes the the biggest weak point will always be people. I donāt understand what people gain when they bypass the automated lock with intent.
Shane,
I have been on PC DAW platforms and using NUENDO since V1 of the program. I personally like and have ALWAYS appreciated the fact that Steinberg chose to negate the screen saver upon initial bootup of the program As a fulltime professional user of the program I just donāt want my DAW systems or monitors, for that reason, to power down at anytime when I am using the program especially during long recording periods where you may not have any interaction with the mouse or keyboard for some time like live concert recordings, etc.
If you want the screen saver to become active again then the simplest way to achieve this is to once you have booted into the program, either Cubase or NUENDO, in the upper right corner click the Minimize (-) dash icon and minimize the program window and then immediately re-open it by clicking on the Steinberg Icon in the Task Tray where it minimized to. "Donāt Re-launch the program but only minimize for a second and then Restore/Down bringing it back to full operational screen size. This takes all of less than a second of your time and Overrides the Screen Saver Lock Out on initial bootup.
Hope this helps alleviate a little frustration on your part.
Hi, @complexone, thank you for your response. I am running Cubase Pro 12 (v 12.0.52 Build 393) on Windows 10 x64 (v 22H2 Build 19045.2604) on an HP Z820 and unfortunately, the solution you suggested does not work for me. As instructed, I opened Cubase, immediately minimized it, maximized it again after 1-2 seconds by clicking the Cubase button on the Task Bar, and neither the screen saver nor screen lock activated. I had just prior set my screen saver to timeout after 1 minute (which works only when Cubase is not running). Iām not sure what might be different in our setups that allows this to work for you but not for me.
At any rate, I appreciate the suggestion. Cheers.
Shane,
Sorry that didnāt work for you. It has worked for me since V1 of NUENDO and Cubase up through V12 of each program. I actually found out about it by accident when one of my other engineers had minimized the session and then re-opened it only to find that if there was no interaction for a period of time that the screen saver actually kicked in automatically. It has also worked on every other clients DAW running those same programs so I donāt understand why this does not work for you. Let me look into this further for you and if I can find out anything further I will be back in contact with you.
Iām actually setting up another clients DAW today and once I have N12 installed I will test it on his system as well and let you know what I find out.
Complex One Digital Post
Did not work here either.
I am curious to precisely understand how you got this to work, as itās not supposed to according to the specification, and I cannot make it work here. Are you sure thereās not some missing step or maybe an app that disables the Cubase policy?
Hi @complexone, thanks. I am indeed very interested in figuring out how I can make this work on my system if you are able to find the difference. Note that I do not have Nuendo on my system, so not sure if that could be a factor. If you have a system with just Cubase on in, that might be a good one to check to eliminate any potential Nuendo influence. I appreciate your help.
Iām totally guessing here, but a common way Windows allows programs to hijack the screensaver is by changing the application Thread state through its API. This is preferred to actually changing the users Screen Saver/ Screen Lock setting itself (which causes all kinds of other issues). This preferred solution is tied to the application only, and dies with it (in the event of a crash). It would use code such as the following when Cubase launches:
public static void HijackScreensaver()
{
SetThreadExecutionState(
EXECUTION_STATE.ES_DISPLAY_REQUIRED | EXECUTION_STATE.ES_CONTINUOUS);
}
which sets the program thread to a state that keeps the screen saver from activating. If this is indeed what Steinberg is doing, then a SIMPLE and more user friendly replacement would be something as simple as the following modification:
public static void HijackScreensaver()
{
if ( UserWantsScreensaverDisabled ) {
SetThreadExecutionState(
EXECUTION_STATE.ES_DISPLAY_REQUIRED | EXECUTION_STATE.ES_CONTINUOUS);
}
}
where the Variable UserWantsScreensaverDisabled would be an additional option in the User Preferences dialog that provides every user the ability to choose for themselves whether to have this behavior or not. IMO, there is zero need to enforce this behavior on everyone, or else every DAW would be doing it.
If Cubase uses the approach above to hijack the userās security settings, then as far as I know, there is no way for another app to undo that Thread elevation. Whereas, if they actually changed the user options set in Control Panel, one could potentially have a script to set it back while Cubase is running. That doesnāt appear to be what they are doing.
Shane,
Try just Minimizing Cubase to the Task Tray and not re-Open it again and see if that works. Iām still installing software on another system here but will try and duplicate on this end as well.
Hi Jim,
No joy on that approach either, unfortunately. That was the first thing I tried. Re-enabling screensaver when minimized would be ideal (and what I would consider normal).
I discovered this morning that I forgot to close a minimized Cubase and my system remained unlocked, my three monitors on and radiating like space-heaters, and my system in a high-power state all night. Unfortunately, that wonāt for work for me since I donāt have the need for Cubase to be active full-time (ignoring the security risks).
I knew of this behavior from the trial and had decided not to buy Cubase, but got hooked with the $215 Pro 12 special (40% off + crossgrade) thinking I can use the included VSTIs/content in my other DAWs. Iāve paid more for single instruments. And I can always pull up Cubase when I need the features only it provides, especially for film projects. Not ideal, but a solution if I canāt find a workaround.
BTW, I like your site. It looks like youāve got a thriving business in TN (and beyond). I see you use Nuendo. Do you do audio work or sound design for film as well (which are my primary interests)?
Cheers,
Shane
Shane,
Mostly Post Production Mastering these days for musical clients but have done Tracking, Editorial, Mix, and Mastering for the past 52 years. Editorial with a razor blade and splice tape back in the day! No easy undo back then.
Ha! Funny you should mention that. Watched Blowout last night (John Travolta, Criterion Collection) and it really brings home what you just said, from the old Nagra reel-to-reel field recorder, holding your shotgun in your hand (directly), to marking tape with a grease pencil, to walls of tape boxes, all of which were erased in minutes by some nefarious perp. We have it SO good these days. Way before I got into sound, but I do feel pretty ancient with my Sound Devices 302 field mixer.
1 Like