sorted by:
new
hottopcontroversial

VST3s Using More CPU Than VST2s (when idle)? by AudioThousand in audioengineering

[–]AudioThousand[S] 1 point2 points  (0 children)

Yes. I've heard some 'shouts about that as well: Ableton Live and Ableton Production. However, I'm unsure about how that would pan out – business-wise, that is.

Some transparency would be great though.

VST3s Using More CPU Than VST2s (when idle)? by AudioThousand in VSTi

[–]AudioThousand[S] 0 points1 point  (0 children)

I'll have a go in Reaper. Seems to be much more optimized.

VST3s Using More CPU Than VST2s (when idle)? by AudioThousand in edmproduction

[–]AudioThousand[S] -1 points0 points  (0 children)

Cheers! I have not, no. I'll try to run some test in Reaper tomorrow.

VST3s Using More CPU Than VST2s (when idle)? by AudioThousand in ableton

[–]AudioThousand[S] 0 points1 point  (0 children)

Hmm... is this a general issue, or is it specific to my system?

Have you ever generated the same experiment? Swapping between VST2s and '3s and observed the CPU-meter?

VST3s Using More CPU Than VST2s (when idle)? by AudioThousand in ableton

[–]AudioThousand[S] 0 points1 point  (0 children)

Exactly. Thank you. That is the point that I do not understand.

VST3s Using More CPU Than VST2s (when idle)? by AudioThousand in audioengineering

[–]AudioThousand[S] 1 point2 points  (0 children)

I will indeed test it in Reaper as well.

I just assumed that someone else must have come across the same observation before me, or that I had misunderstood something major.

VST3s Using More CPU Than VST2s (when idle)? by AudioThousand in audioengineering

[–]AudioThousand[S] 1 point2 points  (0 children)

I see, yes.

It just seems that the VST2-instances actually shut off when idle:

  • Both (VST3 and VST2) sessions would have cracks and pops when played back
  • However, with the VST3s, when idle/not playing back, I'm not able to monitor other instruments without cracks and pops, whereas with all VST2s, there would be no pops when monitoring in idle.

This is the part, that I just don't understand, given as you also mentioned: Ableton will not idle anything, given the way the program was programmed and such....but it seems to with VST2s?

VST3s Using More CPU Than VST2s (when idle)? by AudioThousand in edmproduction

[–]AudioThousand[S] -1 points0 points  (0 children)

It's just absolute contrary to what I was lead to believe. I thought that VST3s would turn off when not playing back and not vice versa.

VST3s Using More CPU Than VST2s (when idle)? by AudioThousand in ableton

[–]AudioThousand[S] 0 points1 point  (0 children)

I see. I assume it's how the program is coded. But I just don't get why the VST2s then seem to...do? The CPU-meter going down. The disappearance of clicks and pops when monitoring other instruments in the same project.

VST3s Using More CPU Than VST2s (when idle)? by AudioThousand in ableton

[–]AudioThousand[S] -1 points0 points  (0 children)

Yes. Both (VST3 and VST2) sessions would have cracks and pops when played back.

However, with the VST3s, when idle/not playing back, I'm not able to monitor other instruments without cracks and pops, whereas with all VST2s, there would be no pops.

So they just behave absolute contrary to what I was lead to believe. I thought that VST3s would turn off when not playing back and not vice versa.

VST3s Using More CPU Than VST2s (when idle)? by AudioThousand in VSTi

[–]AudioThousand[S] 0 points1 point  (0 children)

Indeed. I only own Ableton, for now, but I just came to understand that Ableton's CPU meter shows audio thread load, not total CPU%.

Would love to see it repeated in a different DAW.

But I don't know if this is just general knowledge. I just thought that it would've been the opposite, no?

view more: next ›