Hello!
I recently installed Cubase 14 Pro and Reason 12. With Cubase 14 Pro I experience that the VST3 plugin freezes Cubase - it does not show the GUI… only a blank page as it starts - and then it stops. Cubase has then to be terminated via Task Manager. However! The plugin works just nicely in Cubase 10 Pro - which is why I suspect this to be a Steinberg-problem. My OS is Windows 10 Pro with some 128GB RAM, a fast intel I9 processor, ASUS ROG Maximus z790 Hero motherboard and Presonus Quantum2626 thunderbolt audiointerface. Apart from the Reason 12 VST3 plugin, the system seems to work fine. I’ve been a Cubase/Reason user for as long as I can remember. I do not whish to ditch Reason …
Hi,
Generate a DMP file and share it via Dropbox or a similar service, please.
Use the Microsoft ProcDump utility to generate a DMP file, please.
-
Please download ProcDump64 from Microsoft (~650kB) and extract the archive to a local folder on your hard disk.
-
Run Command Prompt (cmd) as administrator (right click and select “run as administrator”)
-
Navigate (in the Command Prompt) to the folder with the extracted procdump file.
For example:
cd C:\ Users \ \ Downloads \ Procdump
Note: the dmp file will be written into that folder. -
Launch Cubase/Nuendo. You can work as usual. At any time, change to the command prompt and start procdump, to monitor Cubase/Nuendo for unexpected behaviour (see next step).
-
Launch procdump64 via Command Prompt:
Cubase 13:
procdump64 -e -h -t Cubase13
Nuendo 13:
procdump64 -e -h -t Nuendo13
The -h option will write a dmp file in case of an application hang. This might kick in too early sometimes, in case some action takes a little longer. Feel free to skip the “-h” option, if you are only up for fetching crashes.
The option -e will catch exceptions and the option -t terminations of the application.
- Prodump is now monitoring the Cubase/Nuendo process and will write a crash log, in case Cubase/Nuendo crashes or hangs. Perform the action that causes Cubase/Nuendo to crash and send us the generated crash dmp.
ZIP and share the DMP file via Dropbox or a similar service, please.
I have seen this standard answer in threads here. But why this?
“Launch procdump64 via Command Prompt:
Cubase 13:
procdump64 -e -h -t Cubase13”
I do not have Cubase 13!!.. it’s 14 - I clearly stated that.
Hi,
In case of Cubase 14, use procdump64 -e -h -t Cubase14, please.
Hi,
may I remind you that this is a USER forum? Please keep it friendly - no need to be so harsh when other users are helping you out (no need to be harsh even if this was an official support channel for that matter).
And seriously. Is it really so hard to guess which number you need to change if you are on Cubase14…
2 Likes
Sorry - I did not mean to sound harsh. I got confused by the message. Thanks anyway. I’ll try to create the DMP-file , but then send a support ticket to Steinberg.
1 Like
I haven’t made that file yet. But - I found the craziest workaround ever. Well - at first I tried disabeling VST2 plugins - that did not work. Then - after a hard closedown of a frozen Cubase via TaskManager I chose to start it WITH PREFRENCES disabled. Had to choose my ASIO Quantum2626 on the way in - but - to amazement the Reason VST plug loaded nicely. So I set all my prefernces to default, quit Cubase and tried to start it again. But alas - same problem… so I killed Cubase via TaskManager again… after which the plugin once again worked… THIS time… I saved the project and quite Cubase the normal way. Started Cubase again and loaded that project… mind you - I had to look for it - it was not in Recent projects… BUT! it loaded the plugin just fine. If nothing else - this (and the fact that Cubase 10 has not this problem, makes me pretty convinced that there’s something seriously wrong with Cubase 14). Glad I found a workaround - taking notice of it. I’m kinda busy but will communicate my findings to Steinberg soon.
Hi,
This means, something is broken in the defaults.xml file (which is bypassed, when you start Cubase with the disabled preferences option).
Therefore I believe, deleting the preferences from the Safe Start Mode would do the job for you.
Do you mean in the Preferences window? Not all preferences are related to this window.
This may or may not help.
I have seen a lot of issues with Reason plugin, usually in larger projects (freeze while trying to connect to allow plugin)
Try this: Open a empty Cubase session then load the Reason plugin. Then load your project.
Was reported to Reason previously…
edit: no problems with c14 and reason 13 plugin so far.
Yes… I did the reset in the Prefrences window. I will deffo try the fix you are suggesting. Thanks a lot!! Will report back if the fix is working or not. 
Have a nice weekend. Best regards from Norway
OK - actually I did not have to do anything else. After I had performed my little fix - and a cold restart of the computer - the Reason VST3-plugin has been faithfully loaded. After a few days I think I can say the issue has been solved. Thanks for all your input to the thread. Regards Eivind, Norway