Issue [2.2.21] and [2.2.20] cpu bar go to full switching more song - crackle - no reset

VST Live
1

Again, as it happened in the past, this issue appear.
Now, win 11, same project, that works fine in last vstlive1, to test.

  • load the project
  • change songs, in stop mode, or after playing a song, doesn’t matter.
  • switch more than one songs… 4-5-8…

what happen now? the cpu bar, from quite status go to the saturation (red led) (green bar) every time i switch song, and more and more every time i change song.

more songs, or part you switch, than the cpu bar show more engagements, to saturations, than crackle. (doesn.t matter the buffer, high or low, and with high energy profile for system)+

IMO this mean every change, add a saturation of cpu, maybe do not unload the previuous charge.

this happen without do any, simply jump with the mouse to select songs, random, does not matter what song is, what is the containt.

please note, that every songs, when you load the project, if selected first, has no charge on cpu bar.

reset audio device has no effect to reset the bar, MP IS OFF.

the only solutions is reload.

most of songs have this structure: 2 stacks with same plugins, on mixer, and same send to group (project group) with some plugins.

is the usual old prj, nothing new, i sent many times in the past to you.

thanks , @musicullum @Spork

2

Hi @frankvenice ! I promissed myself not to comment in the forum for a while…, but…

(I had such problem months ago, for I’ve found what caused the problem and that one has been fixed already)

Quickly tried your receipe out. Installed 2.2.21 both on my Mac and WIN. Couldn’t reproduce. That means - would help developers - using your project: try to turn off, remove, etc… elements, stack, plugin, whatever and narrow the situation. (make a sandbox copy first)

Maybe developers can repro this immediately on their test project, but maybe just with your further receipe.

F

1 Like
3

“load the project” - tried “new_fresh_test_2_0_23” with version 2.2.21 and cannot reproduce. Missing some plugs though, so what happens when you remove F6_RTA, Vitamin, and AR TG, still problem? Also we checked our debug routing, going through all Parts multiple times and back, there are no cumulating audio processes, and no CPU problems.

4

I have this problem with two instances of Antares autotune when playing back vocals from recorded tracks to stacks, it’s plug-in dependant for me … seems that this plug-in won’t release processing when transport stops in the middle of a track playback … does not happen when live audio monitoring …. Not a VST live problem anyway …

Cheers Ciro.

1 Like
5

I lose more time to test, and it is not a good thing, it is not the first time, as you can see in my posts in the past .
So people who comments, please don’t tell me what i have to do.
.
I try to built a new simply project, loading the 3 waves vst . and duplicate songs more times, in stacks and groups…
Seems that the issue is not there… or yes.

I tried to load , unload,… so i suspect there is something when i switch songs that unload these plugins.

NOTHING CHANGE IF I UNLOAD A VST, OF WAVES. THE RESET IS IMPOSSIBLE. ONLY RELOADING THE PROJECT, NOT THE SETLIST, NOT ERASING SONGS, NOT UNLOADING ALL no-steinberg vst.

So , come back to my original prj, i tried to load setlist with 10 songs,… instead of the whole, about 70.
the issue repeat after switching 10-15-20 times… mean loading and re-loading the same plugins, because all stacks are preatty the same in all songs.

I don’t know why in previuos versions (vstlive 2.1.32 …less or more, and vstlive 1, ) the prj have no issue.

and finally if i reset audio device, from menu, no change, and the STACK NUMBER 2 , LOSE CONNECTION ON INPUT = N/D INSTEAD PIANO. of the selected part, after reset.

I don’t know what is the issue, it’s up to you.

6

That is extremely rude. If you post here and others try to help you giving tips, responding to that with “don’t tell me what to do” is very unsocial. Please keep this forum open and helpful as it has been for a long time already.

And shouting is not necessary either.

We offered to help, examined your project and cannot reproduce it so we check the differences and advised to exclude those to see if the culprit of your problem (which nobody elase appears to have) might be related. We cannot keep each and every plugin in the world on our computers to test. This is all to help you, but if you don’t mind your tone, you will not find much of that in the future.

1 Like
7

Probably fixed for the next version, see https://forums.steinberg.net/t/undo-does-too-much-2-2-17-and-many-previous/982910/7

8

I apologize my capitol letter (for wrong netiquette) , my intentions was to assure that i tried to unload. maybe bold was appropriate.

So i understand that you can’t try every single vst in the world. But speaking about waves, one of most popular brand, it is useful for many users.

I’m social if social means tip and help. If mean “you have to report this …”, so i’m not stupid, my posts, and report in the past, and the time i spent, was for all , not simply for me.

I respect anyone, please do the same, My English is poor and this is a limit for me.

but i’m not a payed beta tester, i’m a customer, it’s quite different.

So i suggest to improve the number and kind of Steinberg vst in vstlive, so we can prefer more stable and tested project for every future release.

Frequency, for example, something as magneto, with less latency as possible and so on.

I’ll trust in your kind support, as in the past, hoping to be clear this time.

9

Sorry, that was a betaforum reference, my bad.
Basically saying that the issue should be fixed with the next version.

1 Like
10

We do have many many Waves plugins, because you are right in that those are popular and so we have quite some to test against. Just not those you mentioned, therefore the suggestion to exclude these for testing. No such issues with any of the ones we tested so far.

11

ok, I see. This kind of issue happpened to me in the past, if you remember, when Multiprocess comes in, and when Preload was improved., or before, when mixer, group songs, was improved.

I don’t understand what new feature, or improvments made this kind of issue, maybe new last adjustment of preload?

12

I tried 2.2.23, still issue.

13

I think the most important thing here, from what @frankvenice says, is that the problem doesn’t occur with VST Live1 or even with VST Live 2.1.32 (the version I use for the live show because it’s very stable). So the problem shouldn’t be which plugin you’re using, but rather what change was made in the version after 2.1.32. From there, developers should see which of these program modifications may have affected performance.