Cubase :A Serious Problem has occurred

[DarkStar]

^^^^
Just to expand on that. You can reply to any email from Tech Support about the problem (including the auto-acknowledgement) and attach the files to your email.

[dollarshades]

Thanks Peter - I've sent over Cubase Crash files as you suggested. Hopefully there is a solution to be had soon.

[dollarshades]

I just noticed that since I 'Froze' my main vocal track I haven't been getting the 'Serious Problem' error on the project, even though I have the TR6 'Mothership' and a few other modules on various other tracks.

The only difference is that the vocal track has a chain of modules including non-Ik plugins.

The Chain is as follows: RX10 De-Click > Ozone 11 Dynamic EQ > TR6 Mothership (British Channel+Black 76+Channel Strip X) > CSR Hall > MTM Reso

Perhaps TR6 isn't playing nice with the other processors on the track?

I'll experiment more and see if there is one particular module causing the issues.

[dollarshades]

Just tried removing the Ozone EQ and MTM Reso from the vocal chain and *so far* no errors, plus the CPU meters have returned to normal instead of peaking into red as they were with those two vsts in the chain.

I'll update my help desk ticket accordingly - it would be interesting to hear from other users with the same problem if they are using their TR6 modules with other 3rd party apps in a chain?

[dollarshades]

The idea that this issue only arises when TR6 modulaes are used in a chain with other non-IK vsts seems to have gone out of the window ... all sorts of problems occuring now on Delay Lab, Bass One etc. Plus, Cubase is now vanishing without trace when trying to open this same project that has been troublesome ... no option to save under a different name, no warning, just 'Poof' and Cubase is gone.

Also just to confirm that I don't have HiDPI enabled on Cubase.

Looking forward to an urgent response from Support ...

[jockelundberg]

Another one with the same problem. All the new TR6 plugins are useless in Cubase as they make sessions crash on start up, and repeatedly make Cubase unstable while the session is active (i.e. a serious issue occurred...).

Have shared screenshots for specific plugins with support.

All my TR5 plugins works flawlessly.

[dollarshades]

Odd behavior still, but the problem only seems to occur on the first project load of the day. Get the error, save off with a new name, close down Cubase , restart and all is well for the duration of the session.

Using a lot of TR6 modules (mostly within the Mothership) and haven't had as many problems.

Strange ... definitely an issue that needs resolving but still no more response from Support.

[auggybendoggy2]

Same for me in Cubase 13 pro. I've had to remove all my Tr6 plugins from my project and resort back to Tr5.

IK has done a great job in the past updating so as soon as they recognize it's an issue for many, they'll fix it.

Aug

[drapeta]

Happens in Nuendo too. However, only when starting a project and always randomly with different V6 plugins. Usually the only thing that helps is restarting Nuendo and praying ...

[dollarshades]

I've found that when opening a project and getting the unstable error, if I save the project (not Save As ...) it will automatically save it with a new name. Then I close the project and exit Cubase.

Start Cubase again and open the newly named project and all is well (Other than a build up of unnecessary storage of renamed projects!).

Once up and running doing it this way I don't seem to have any more issues throughout the session.

Very odd behaviour that points to some sort of overload on startup.

This is on Windows 11 and CB Pro 13.0.41 (the latest maintenance release appears to have multiple problems of its own that I don't want to have to handle on top of this IK issue)

[dollarshades]

Just updated to Cubase 14. So far, so good ... no issues to report.