Hi,
I was working on a song fine yesterday and today it won’t open at all, Cubase 14 freezes on the Loading MixConsole process.
Important to know that my Cubase OFTEN will produce the Safe Mode window upon opening, even when the program seemed to have closed fine. To me there is definitely an issue in Cubase about closing the program and I am not the only one to experience this.
Here is the DMP generated via ProcDump :
I’d love some help so I can get back to work on my music, thanks a lot !
Fixing my own issues, I found the culprit : Waves StudioRack.
Removed from my system, the project loads fine !!
Shame because it is such a handy free tool to make multiband parallel processing megaplugins !!
Maybe Steinberg could come up with its own version ? I really dig this plugin, for example on this track I had a StudioRack on my drums bus, with saturation on the low band, an IK LoFi instance on the mid-band, and an exciter on the high band.
I’d love a Cubase built-in way to do that, with the Macros like StudioRack.
Would be more stable I guess.
Thanks @Martin.Jirsak for changing the title.
I hope that will solve the issue on Cubase closing the app.
I often get the Safe Mode even when the app closed properly.
But as it happens on many projects where I do NOT use StudioRack, I don’t hope too much.
I have already written to Waves about this. I will need to test C15 to see if it’s better and decide if I buy the upgrade or wait.
UPDATE :
After persistant issues I identified the issue could be with IK Multimedia plugins.
Here’s a simple test with 2 identical tracks, each with no audio on it, just loading one instance of LoFi Punch and one of CSR Plate.
When closing the project, it creates a dmp file, and Cubase then reopens in Safe mode.
For more complex projects this can lead to project not reopening like what was happening in the original post with those IK plugins loaded inside a Waves StudioRack instance.
I will write to IK now, but since I’ve had those issues for months across projects, it would be worth checking in Cubase has issues with unloading plugins on closing projects. Files below.
Cheers
both the crash and the freeze occurred in LoFi Punch.
I don’t know if StudioRack was being used when these happened, but there is no indication that it could be involved.
We can’t see what the problem is, there were no calls from Cubase in both callstacks, they contain one LoFi Punch call and a couple OS tasks (see callstacks below). These need to be resolved / checked by IK.
There is also no indication that CSR is involved. But I used it quite often since 2009 (I actually have CSR Room and Plate on most projects) and didn’t see it crash in several years.
Did you notice if, on the project(s) that hang on opening, if you saved it with the IK plugin’s UI open?
Any specific reason why you’re still on 14.0.31? I don’t think .32 or .40 would behave differently, but as .32 was a hotfix for .31, I’d recommend to use that (or .40, if you’re not using Atmos… there’s a bad crashing bug in .40 with Atmos).
You can of course test out the C15 demo, but I’d guess it will crash just the same.
I saw posts with users complaining about bits about 32 and 40 so thought I’d rather not move ! I will try update (I don’t use Atmos), and will test Cubase 15 too.
When I read that I thought yes might be it ! Since I had issue with the double monitor before crashing when plugins were opened on the second monitor.
But weird stuff when testing :
1- I reopened the project that was taking 30s to close and producing a dmp, works fine (LoFi and CSR on 2 tracks, no StudioVerse)
2- I ran a battery of tests, found out that I can run many tracks with LoFi and CSR and many other plugins without a problem. I can even run StudioVerse with a multiband and some IK plugins, but not LoFi Punch ! That one cannot be loaded within SV without causing the project file unable to open after closing Cubase.
I will email details to IK.
For now I’m glad I know what not to do with my mixes ! Shame as I love LoFi Punch on my drum bus just on the mid range, but I can live without.
Thanks again Fabio !
Cant’ see much problems with .32, the submitted issues are less than with previous versions - .40 has that unfortunate Atmos issue, most of the crashing issues you see are due to that.
But we’re working on a hotfix for that too, so no reason to move up right now, I doubt it would fix your issue.
Weird that it’s only the combination, for what I see it’s either an OpenGL issue (one dump shown a recursive NVIDIA call, likely a hang), as both IK and Waves use that on Win, or simply LoFi has an issue the other TR6 don’t.
But then again, I can only speculate, if you hear from IK, please let me know what they say.
Waves plugins are often the cultprit of a good portion of DAW related problems because of how they work. Each plugin version starts a local server when a DAW is opened and that can cause a whole heap of issues from plugins not loading properly, plugins not closing properly, the processes triggering auto-scan routines because the DAW thinks the server loading is a new plugin, etc.
Errr… apologies on the above… I’m usually not that detailed with public posts, I don’t like it - thought I was replying to Antoine’s PM. Apparently screwed up for good. Guess I’ll file this under “Oh, well, so next time you remember to double check, aye?”.
No worries at all Fabio, this public post hopefully can help other people.
And when I learn something from you I try make sure to pass it on to other Cubase users in the forum !
I’ll keep you posted when / if I hear from IK or Waves.
Btw thanks to you too @BrunoDSL I will reply to Waves about it !
