I understand the issue you’re raising and agree, that it would be nicer if screen locking wouldn’t be disabled, and even nicer if the system was allowed to sleep and wake while Cubase is running (without negative side-effects).
However, I simply disagree on how horrible this problem is. At least for my use case - and presumably the use case of many Cubase users participating in this forum.
While I’ve worked in and later managed enterprise IT environments for longer than I care to remember, I have different priorities and expectations in my home studio. And I also have different expectations from a company like Steinberg than from someone like Oracle, IBM or SAP. And it’s not that the software put out by those companies doesn’t have issues that don’t seem to get fixed, because they simply don’t bubble high enough.
… maybe you didn’t “read the room”?
Some of your posts sounded to me a bit similar in tone to a CIO type, who’s used to being able to mandate priorities without much push-back, because of the organizational power they yield.
This forum is a pretty egalitarian nerdy place where such power doesn’t count - and most of us have our own pet issues with Cubase that we wish Steinberg would consider as high priority. And we tend to be pretty opinionated in our nerdy ways about what’s important, and what’s not so important. In this environment your voice is just another voice at peer level. Some people will see the issue you’ve raised as important, and others will see it as much less important.
Welcome to the forum! And hopefully there will be more fun filled threads in your future here.
It’s odd what gets people so riled up. Whilst I don’t give a toss about security, being an absolute amateur, Cubase’s tendency to ignore SYSTEM settings gets right up my nose. So yes, Steinberg, allow my monitors (2 x 32") to turn off when I go to eat, allow my pc to sleep when I go to bed so I don’t have to wait 5 minutes for it to boot up in the morning.
(Using Win 10/Cubase 12 on an i9 12700K with an AMD 6700XT graphics card and a RME AIO audio card.)
I forgot to mention the way Cubase screws up my sound settings. Every time I close Cubase I have to reset my audio output back to my speakers, because Cubase, for whatever demented reason, ALWAYS switches that output to headphones.
I’m using an RME AIO card, every driver up to date.
This used to happen on my old i7 4790 machine and now on my i9 12900 machine.
I had to disable and/or uninstall all other audio drivers (except my interface driver) in Device Manager to prevent this from periodically happening to me. However, it was a Windows issue for me not a Cubase issue.
I’ve tried this. I have 2 "High Definition Audio Device"s along with my RME driver. I’ve uninstalled them, deleted them, wiped them clean. Next time I boot up, voila! They’re back. I suspect they’re installed by my AMD 6700 software. I have 2 monitors, so 2 drivers?
Could be. Whenever I update my Nvidia monitor driver I have to go in and delete the audio drivers it reinstalls again. Frustrating but now that I’m aware of it I just do it automatically. Price of using Windows, I guess.
That’s “plug and play” at work. Your monitor will have audio streams available if you’ve got it connected with HDMI or DisplayPort, but that should show up labeled as such (like HDMI Audio or the name of your display). The ‘Hi Definition’ is a generic driver that’s usually a built in audio device (does your mobo have audio outputs or a headphone jack?). If you delete the drivers, the hardware is still there. Windows will find a new device every time it reboots and install those system drivers for it.
So yeah, I’m a bit of a lurker, but I’m picking up on the idea mentioned earlier that there is a silent majority of users who are perfectly happy with everything C12.
I think it’s more likely there’s a silent majority that does bump into the bugs & quirks mentioned here but doesn’t feel compelled to add to the chorus as these issues are already brought up by others.
I’m one if those.
However, I feel for the first time that I really, really need to speak up and strongly urge Steinberg to reconsider and release one more C12 update, as all the Render in Place bugs (faults really) need to be ironed out before asking us for more money. RIP is such an essential part now of many users’ workflow and the one thing any DAW has to do perfectly is render.
It would be the decent thing to do.
I’ll second that for a last maintenance update hehe. Im one of the folks that is having absolutely NO problems with C12 (or C11 for that matter), but… I haven’t yet needed to bounce anything in place… I’ll more then likely be buying the update to 13 right away but, would be nice to get that fixed up just in case…
