I’ve noticed my i7 laptop struggling a bit more, and the fans coming on much sooner, usually immediately when I load VCV. One thing I realised is that upgrading seems to have set the frame rate back to the default 60Hz, dropping this down to 15 lowered CPU use by about 10% straight away, and also got the fans powered down…until I add a ton of modules at least!
Another issue is I’m now getting this on any Reaper projects where I’ve used the Pro VST:
The update didn’t change the location of the VST plugin, so not sure why this is happening.
Ok, maybe I should have phrased it differently - the point is, if you want to run both 1.6 and 2.5.1 on the same machine, you need to decide which one of them you want to be able to use in the DAW, because you can’t use both. The one you want to use in the DAW must be installed last, and its directory and executable must not be renamed after installation, because that’s where the Rack DAW plugin will look for it.
The relevant commit is interesting reading for anyone interested in C++ optimization. Hopefully we’ll see the new approach play out positively in the field!
Sounds good! 1.5% is probably in what I would call “measurement noise” and those numbers tend to bounce up and down a bit. Sounds roughly like “unchanged” to me and I think that’s the important bit. Of course, you could try and make a large and taxing patch, then measure on both versions, and see if you can make the difference consistently larger than that. If not I’d say job done.
There are ways to keep two versions of Rack on your machine (previously posted on this forum, but I don’t have the reference for you), so you can keep your working setup and also experiment with the latest (now 2.5.2).
The CPU consumption has changed positively. I also had big problems with V2.51.
After update V2.52, I have the impression that it behaves like V2.41. Good luck.
While using 2.5.2 for the first time yesterday, I noticed that the only place I experienced crackling where I had not previously, was while browsing the library.
how did you get back to 2.4.1 ? I am having the same issue and with 2.5.1 and the patch is unusable I have tried everything I can to think to fix it even removing modules that seem to use more CPU and still sitting at 150% with crackling and constant audio problems.
I downloaded 2.5.2 on my other laptop to try it because I can’t risk losing the patch (its for an assignment) it was the same result. What I have had to do is get rid of nysthi simpliciter in the patch and now its spiking at around 89% which is useable, kind of. strange because i’ve had way bigger patches before that have never spiked this high.