I am using Cubsae 12 Pro, together with VCV Rack version 2.6.4. I tried going back to 2.6.3 reinstalling all plugins and it will work fine for a moment (well at least it did, now it’s just giving me errors), but I can’t open older patches only start new ones. It’s lately giving me this error, when adding the VST instrument. What’s going on here? The stand-alone version of VCV Rack works just fine. Is it due to a certain module or what is causing this issue?
My OS is Windows 10, and been running all the updates ever since, it’s been on there since 2 years. I will download the latest version off the Windows site, and create a new installer, when the end of life of Windows 10 will arrive. Perhaps do a reinstall, but I have so many plugins, just don’t want too loose them.
A new PC (Intel based) with Windows 11 and the latest components is planned, but that could still take a while, I am also eager to upgrade Cubase, but honestly waiting till version 15 before doing an update, which will be released at the end of the year, knowing Steinberg. Then I will do a fresh install of windows with the latest version of Windows 10 or by that time Windows 11.
It’s not the patch, I am getting a error when starting with a new fresh patch too. I noticed Cubase just quits on me whenever I load a heavy 96Khz 24Bit patch (created in the stand-alone version of VCV Rack) in for offline rendering, no error, just quits. So I have too restart, create a new VST instrument with VCV Rack and load the patch into a freshly VCV Rack instrument, then it works, but I only get one shot (or as long the session is open).
I also didn’t hear anything from VCV Rack support service yet, so I guess I’ll just have to wait for that, if they even reach out.
I usually build my patches inside the stand-alone version at 44.1khz, this just because it takes up less CPU draw, once done I want to bounce offline at 96khz 24bit inside Cubase, this used to work fine for years, but now lately having issues, no Cubase plugin have been added since it was running fine.
The “starting a fresh patch”, usually works fine, even when I’m in 96Khz 24Bit, it’s just it does not load the patch anymore after creating a new instance of VCV Rack and loading the patch into that and re-opening the project. I even tried saving the patch back at 44.1Khz before saving (yet leaving the Cubase Project intact at 96Khz), this does not work either when opening.
It’s just that each time I create and want to re-open a patch inside Cubase, it refuses. And have to start all over again.
BTW: I used version 2.6.4 inside Cubase for a while too with no troubles, but it seems that version 2.6.3 is more stable?
I was hoping someone could dissect the crash dump log and make something out of that, perhaps it’s a single added module that is causing the problem, I do add new VCV Rack modules on regular basis, even the paid ones…
Sure, that’s true. But a) the crash trace goes right into VCV, b) there many orders of magnitude more usages of VST in Cubase than there are VCV users. So - either is possible, but if you were giving me even odds I think we both know who I would bet on.
