You’re insisting that there is a bios in Cubase? Are you sure you don’t want to say “baios”, as that is where the crash happened?
Hi Johnny
Easy mistake to make.
No matter Martin said Component
I would like to know how long Is this going to take
By the time a next update comes out , so will Cubase 15.
My CC121 controller functions also affected.
Hi,
Oh yes, you are absolutely correct! And I wrote it more than once. Thank you, @Johnny_Moneto!
I should buy a reading glasses.
Now Now boys!! Moneto v Jirsak sounds like a heavyeight world title fight, watch on Sky!! Lol
Hi Martin
Nothing we can do. I find it odd that there is no word from Steinberg on what and when they will fix this update. I had a word with Scan before all of this erupted and nearly sent my machine back. Scan are right Things today are rushed out too quickly. I had other problems as well and the DISM health fix took care of It. A good Admin CMD line to keep.
I have gone back to the last version for now and all works ok even my controller now functions correctly. The Important thing Is to keep making music rather that worrying about flaming computers.
Thanks Martin for all of your help. You should tell the people .“Do not shoot the messenger”.
All the best
John
Hi @JohnS ,
I’ve had a look into the dumps you provided.
Two of them show a crash in the built-in asio driver, which is installed along with Cubase.
The crash dumps look as if the audio processing was stopped shortly before the crash and Cubase crashed on resuming work. The processing stop/start can happen:
- due to an extreme processing overload (dropouts)
-
- likely to happen when you record arm, then disarm the instrument/ MIDI track
- when changing the studio setup (buffer size, driver)
- when creating or deleting a new bus (input, output, control room)
- sometimes: when you put Cubase to the background, e.g. when you a switch to the browser window AND the option “Release Driver when Application is in Background” is active:
If this option is enabeld: disable it, please.
If troubles persist, as first step: if you have an external audio interface, please try the dedicated Asio driver from the manufacturer’s download page. After installing the driver, select the driver from the drop down list in the Studio setup. Use a sufficient audio buffer (eg 512). Thus, we can see if the built-in driver is involved.
Second: if crashes keep happening: disable AsioGuard (you may need to select a bigger buffer to avoid processing overloads).
Please let me know if this changes anything.
We are also further investigating the dumps, so I hope we can find the underlying issue and provide a fix soon.
Cheers
Chriss
Oh no it isn’t!
(Where I live it’s the 21st.)
I would really have been surprised if the machine was at fault. Here’s hoping the temp workaround works (posted by @Chriss .)