I just purchased VCV Rack Pro and started testing the VST3 plugin inside a DAW.
It’s an amazing piece of software, but I noticed that the VST3 version lacks the Multicore/Threads option, which instead is present in the standalone version.
I ask this because some patches are particularly heavy and have glitches when run on a single core in VST3, while in the standalone version, thanks to the Multicore / Threads option, they run without glitches.
Because for example the U-He DIVA plugin support the Multicore feature, and indeed, when enabled the workload is distributed across multiple threads, will it be possible to enable this option in VCV Rack in the future?
Note: I didn’t find any discussion on this topic, so I started a new one.
I think this is by design and I seem to remember reading a statement from VCV to that effect somewhere.
Running your own threads within a DAW plugin will mess with the threading system of the DAW itself. I tried multiple threads in one of my own DAW plugins once and it seemed to work fine as long as the plugin was more or less alone in the DAW. But if the DAW is balancing lots of plugins with its own thread management using your own threads makes matters worse, not better.
Edit: One more thought: If your Rack patch consists of several voices it might help to split it into several smaller patches, each running in its own VST3 instance. That way you can benefit from the thread management provided by the DAW.
I can understand that, but I still think adding this feature as “optional” (enable/disable) could be useful for those who, for example, have more than one processors or want to create tracks using only multiple VCV Rack instances as plugin inside the DAW.
Otherwise, I assume U-He Urs in DIVA wouldn’t have implemented it.. as an option to enable or disable, let’s be clear.
About splitting the patches can be a solution fo now, a little uncomfortable, but better than nothing.
I However, I hope that one day this option will be enabled for anyone who wants to try using it.
