Update 2.4.1 to 2.5.1, massive CPU hit, crackling.

No not yet, apart from having 1.6 installed to run really old patches…

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.

Cheers Lars, I already had 2.4 VST so I’m not sure why it’s not recognising the update.

From looking at the changelog it seems that Andrew has fixed (or at least attempted to fix) the performance regression in the latest version 2.5.2.

1 Like

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!

1 Like

I only see about a 1.5% CPU diff between 2.4.1 and 2.5.2 with same patch, so yes, much better, but not yet same, if no 2.5.x features used…

3 Likes

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.

4 Likes

for those of us (me) who is still on 2.4.1, should we still wait to upgrade? i cant afford any glitches right now!!

2 Likes

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).

I can’t afford a drop of performance now, I am waiting for good news on this community. :broccoli:

1 Like

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.

2 Likes

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.

1 Like

For me 2.5.2 has been on par with 2.4.1, so… happy times. (Thanks devs! :slight_smile: )

1 Like

whats your system

Win7

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.

Before you go back have you tried 2.5.2 ?

3 Likes

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.

Hi and welcome to the forum! Could you send the two patch files, with and without Simpliciter, as well as your log.txt file (found in your Rack user folder) to us at VCV Support so we can look at what’s going on?

2 Likes

Glad VCV Support is on it! :slight_smile: In the meantime, @sophiekilworth, if you want to get to 2.4.1 the binaries are available from the dev blog: it says “pre-release” but the files are final . If that causes trouble with paths, etc. you can build 2.4.1 using the relevant Github target and instructions available here, which will give you an isolated install and is a good experience if you ever want to get into Rack development. Good luck with the troubleshooting and the assignment!

1 Like