I upgraded to 2.2.36; the issues with crackles got worse (happens randomly while playing songs with single parts) and CPU usage went from averaging 2.5% to 9% on the same exact project. I’ve reverted back to 2.2.32 version. Both version in the screenshots below are using the exact same settings. Parts are not pre-loading.
1 Like
My experience is similar, today’s build consumes much more CPU. I don’t know the reason, but wanted to add my experience to this thread.
1 Like
@Spork Have you seen this issue? I have this problem since 2.2.33.
Mine keeps crashing randomly but not generating crashdumps! Ill see if I can force the issue. It crashed during last nights gig twice - big noise out front and then the app just closed on my laptop, but no dump to help. This was using 2.30, upgraded to 2.36 today but having similar random crashes. Ill try film it.
Here’s a video of my increasing CPU usage issue.
Can see here the issue. It seems to happen on this song more than any other so I will rebuild it. Again no crashdump.
1 Like
We are seriously very very sorry.
That appears to be not so good a version. 2.2.35 should work better.
We are working very hard to spot and eliminate these problems. Crashes or unexpected noises are not acceptable.
thanks, will examine soon
Oh - cant see 2.2.35 on the vst live downloads page?
2.2.35 is the same as 2.2.36 due to an issue when 2.2.35 was released (the windows version was wrong).
The “correct” previous version to 2.2.36 is actually 2.2.33 (apparently). Don’t know what happened to 2.2.34…
Correct, sorry, the recommended version would be 2.2.33.
2 Likes