Back in December, SoftTube Amp Room quit working proplerly on my system with all version of installed Cubase ( 12, 13, 14). It works fine in Reaper and Ardour.
What happens is that when I load the AmpRoom plugin in Cubase, it will start to load, wait a bit, windows starts to crash, then the PC freezes. I have to power-down to reboot.
I had cleared the user settings for Cubase 14, reinstalled SoftTube Amp Room (along with all the other plugins), and refreshed the iLok licenses as advised by SoftTube Support. I also disabled OpenGL. I had also removed all of the SoftTube plugins and reinstalled. Deleted User Presets. None of this fixes the problem. I sent them the crash logs, and they finally dropped me and said that they could not figure out the issue, as there was nothing of importance in the crash log that helped them figure out the issue.
I tried it in Cubase 12 and 13. The same issue occurs. I
It was working fine in Cubase 14 until one day it just decided to crap out….
I don’t really understand this sequence. If Windows crashed, how can it freeze after?
Please, attach the *.dmp file(s): Win: %userprofile%/Documents/Steinberg/Crash Dumps
If you cannot find any, create them manually.
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).
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.
Thank you for looking at this. I still can move the mouse, and move a window, but response is very slow. I am not able to pull up the task manager and see what is going on with processes, memory, and drive. Then eventually, I am unable to do anything. It seems like a memory leak type of thing.
What is the difference between a .dmp file that has ‘freezedump’ at the end and one that does not ?
Thank you. This seem very Cubase specific. I have erased the config file and started over. It did not fix the problem. Would a Cubase 12/13 file be shared with 14 ? A VST Preset ?
I may have made a Cubase ‘Default’ (using the VST window, not AmpRooms preset manager) preset for this plugin. Maybe that is the issue. The plugin works fine in other DAWs on this system. Where would that be stored so that I could reset / delete that ? I did not see it in Media Manager.
You can always overwrite the default preset with a new one, or delete them from the VST3 presets folder (in your windows Documents folder).
I had a look at the dumps, but they don’t show anything specific, and from what you wrote it seems like Cubase doesn’t really crash, but Windows becomes very slow and unresponsive, which I would agree looks like some sort of memory leak. Have you tried opening Task Manager with the Performance/Memory view open before you start Cubase and load the plugin? Maybe you can see whether memory usage starts to grow suddenly.
Well, plugins behave differently in different DAWs, and DAWs handle plugins differently, that is nothing new.
Have you tried starting in safe mode with User preferences disabled? I can’t think of how that would make a difference, but it is quick to try.
What I meant with open Task Manager before Cubase: open it so you can see it all the time, on another monitor or if you only have one, resize the Cubase window so you can see both at the same time. Then load the plugins. Maybe it can show you something, maybe not, but worth a try.
Those are the things I would do to test. Else, I dunno, sorry. It might be something just changed on your system that provokes this behavior, but those things can be hell to find out…
Today, that project caused Cubase to crash on launch. The reason for the crash was the ..Softube Weiss Comp Limiter: FAILURE_BUCKET_ID: BREAKPOINT_80000003_Weiss_Compressor_Limiter.ssx!Unknown
After restart, project loaded fine.
I launched Amp Room, it loaded instantly and ran quickly and smoothly (and I remember that I hadn’t used it in a long time precisely because it used to run so slowly).
I smoothly loaded one amp and module after another - everything was working just fine, until I tried to open Tube Delay, at which point Cubase crashed. I took a dump: FAILURE_BUCKET_ID: BREAKPOINT_80000003_Tube_Delay.ssx!Unknown
IDK, brilliant Softube plugins used to be slow to scan after updates. What I’ve noticed in the latest versions of Cubase (since .20?) is that there’s finally a visible preview of the VST3 scan, and there’s even a prompt asking what to do if the plugin takes too long to scan - just like in Wavelab or Reaper - finally!
To sum up my two cents - Amp Room runs smoothly on my system (PC, Ryzen 9 5900X, 64GB, Radeon6600, RME), but there are some occasional glitches between Softube and Cubase 15.