aahh - interesting – but it seems that you can still put Windows to sleep manually.
However when I just tested the manual sleep while Cubase is running, and waking the system back up, Cubase threw a dialog box about changed sample rate. That in turn didn’t seem to create a real problem, so there’s definitely some weirdness going on when Windows sleeps and wakes.
I’m not enough of a OS internals and hardware driver expert to know details, but I assume that powering off and on has a lot of hardware/driver implications including some pretty dodgy drivers that come with some musical hardware. And so I can’t judge how reasonable Steinberg’s approach to power management is. I just havechoose to live with it.
I think they just keep the O/S active as some fullscreen video apps do, or playing a game would. Which then prevents screensaver or machine from locking as there’s no period of inactivity.
For vast majority of users it’s probably the right option, but I have previously seen people complain about risk of screen burn if they accidentally leave Cubase running in the background and it prevents screensaver kicking in.
Trouble is, you can walk away from a machine and sometimes not return for hours if something takes your attention.
If by sleep, you actually mean putting the OS in a sleep state (whether you mean sleep, where the computer is put in a low power state, or hibernate where RAM is written to disk and the computer turns off), that’s not what we’re talking about here. I could see where that could cause some hiccups with some poorly designed SW, but given that most apps today are designed to run well on laptops, many of which are put to sleep or hibernate when you close the lid (instead of doing a shutdown), I would expect most figure out how to make it work.
What I’m referring to here is simply LOCKING the workstation so that in order to use it again you have to enter some credentials, like a password or PIN. This functionality, based upon the user’s power setting preferences, also puts the monitors in a low power (power saving) mode. The computer does not change state as it does when put to sleep or in hibernate mode. In fact, apps still run in the background in this state when the auto-lock kicks in - if they are designed that way. Hope that makes sense.
I get it that lock doesn’t work either and that this presents a security issue, but I remember someone also specifically complaining about energy consumption:
I’m not trying to downplay the security issue, but in my situation I consider my entire studio a reasonably secure environment. If it wasn’t, I’d also worry about someone un-plugging or re-plugging a whole bunch of audio, midi, usb, network and power cables. That would be a low tech way to really mess me up.
Yeah, that’s just a side effect of this Cubase security “feature”.
Do you always remember to lock you machine when you leave every day? Food for thought: could someone walk into your studio at night, insert a USB stick, download all your client’s raw tracks and post them all over the internet? Would you even know it happened? At that point, someone unplugging a bunch of audio cables would be the least of your problems. But I’m sure you have all that figured out and contingency plans in place.
Someone after my own heart! I did the same ping ponging with a 2 track reel to reel. Actually did it first with a cassette player by putting a piece of tape over the erase head so it wouldn’t erase the 1st track while recording the 2nd. lol
everything is windows fault. they have optimization settings for gamers. but no windows for creators and realtime audio. like windows lite. this bothers me the most. this means we need to spend money on stronger hardware than we need. as well as continuing and uninstalling a lot of crap and a lot of other things that you don’t need.
imagine if you could make a profile 2 in windows that you can.
where steinberg has a dsp pcie card that can handle all the bottlenecks that can arise, such as kicking in when there is more than 10ms latency in cubase, it must handle cubase and third party vst vsti and optimize for sound cards and have MTT technology so everything comes when it should come. others already have it.
now steinberg can start making dsp and other hardware, now they have been building Halion and other software vst and vsti for many years. it should be a self-playing piano now that they have brought in sound designers and programming consuls.
there’s a lot you want for Halion but won’t upgrade until everything is scalable.
so now steinberg can focus on hardware such as dsp pcie card and other hardware that optimizes and synchronizes everything automatically for low latency and other problems that can arise in a hybrid setup studio and in the box. as well as optimized usb hubs for audio computers with MTT technology, etc.
all hardware steinberg makes is of super quality, and will last well into the future.
believe in a pcie card that optimizes and syncs everything and ensures that there are no bottlenecks, and optimizes how the computer should be used. and if it is something, it should tell you that you need to change this setting or change or change some hardware.
we buy new hardware all the time and the cpu gets stronger and stronger same with ddr, and the usb ports are high quality same as the chipset, still the problems never go away, how is it possible? well, it’s windows that doesn’t care about creators or musicians. and all daw programmers tear their hair out when windows only releases drivers and other updates without caring about others. only gamers and office people.
when steinberg gets to handle it themselves and build hprdware so that it becomes a closed system in windows. then we should probably see that we get at least 50% more power in the computer.
