Update 2.4.1 to 2.5.1, massive CPU hit, crackling.

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

Iā€™m still getting approximately 70% CPU usage in 2.5.2 Pro with an empty patch on an i9-12900KF.

How many threads configured?

Yikes! Iā€™d definitely contact Support with details. Did 2.4.1 work fine? Does 2.5.1 have the same problem?

Iā€™m starting to wonder if this issue, at least on Windows, which Iā€™m most familiar with, is caused by an underwhelming Power Plan. If I run my laptop (4 x i7-8565U) in the default Battery plan (on battery), pretty much anything CPU intensive ends up crackling the audio. If I run my laptop with AC, that Power Plan seems to work just fine with VCV on 1 Thread. Most likely because in AC mode the CPU gets overclocked.

Then there is the approach taken by FL Studio. When launched on a laptop it flips automatically to maximum System resourcesā€¦

BTW, if this might help, I experienced this also when I run Pure Data with a weak Power Planā€¦

1 Like

Iā€™ve definitely had trouble in the past with Windows laptop power management. On one machine I even needed to go BIOS diving and turn off all sorts of HW-level efficiency features to avoid crackling under load at any buffer size!

Maybe Windows issues are creating false positives for 2.5.2. I hope so, since the known perf issue from 2.5.1 (regarding port-based cable summing) seemed to be definitively fixedā€¦

1 Like

how is everyone on M1 Mac ARM doing with 2.5.2 ? I still havent upgraded, wondering if itā€™s finally safe to do so?

No problems at all here.

It works pretty well here for me, as long as I run only one thread and have a good-sized audio buffer.

M1 Pro. 2.5.2 vanishes many random devices. Trying to open patches that I was using moments before on 2.4.1, but itā€™s saying I donā€™t have modules installed, almost all my modules are none existent. I just downgraded immediately. I got no time for that. Works well in 2.4.1.

1 Like

this doesnt sound good at allā€¦ iā€™m not sure when iā€™ll ever upgrade.

what is the advantage of 2.5.2? so far the only thing i cant do is load the latest OME modules update which needs 2.5.2ā€¦

2 Likes

The complete changelog for 2.5.2 is available at

Youā€™ll also want to read the changes for 2.5.0 and 2.5.1 (in the same file) if you are upgrading from 2.4.1.

If you anticipate problems for some reason, make a backup (or create a copy) of your Rack user folder before upgrading. If you experience any problems, contact us at VCV Support. Weā€™re happy to help resolve them.

Everything seems fine for me. 2021 M1 MBP OSX11.6.5