Bug? Three problems with Waves plugins only in VP20.

pierre-k wrote on 5/11/2023, 3:02 AM

Hello.
This has been bothering me since the first release of VP20.

FIRST PROBLEM - NO FIX

1. Put the Waves plugin on the Audio Master FX. For example, ideal L316 or Ultramaximizer.
2. Render a piece of the project.
3. Close the Render window and start playback in the Timeline.
4. Problem - The sound starts playing only after half a second.

Emergency solution:
Reloading the project or changing settings in the Audio Device tab.

The problem with the Waves plugin L316 nebo Ultramaximizer. also occurs when you click the record track icon.

 

SECOND PROBLEM with Waves plugins: NO FIX

If the Waves audio plugin window is open, the playhead jerks during playback. The plugin may not be active and still cause tearing.

 

Another issue with third-party plugins: FIX IN VP21

In VP20, plugin settings are choppy. Even if Vegas isn't playing.

 

Does anyone have the same problem?

Comments

Peterson wrote on 5/11/2023, 2:24 PM

Another issue with Waves plugins:

If the Waves audio plugin window is open, the playhead jerks during playback. The plugin may not be active and still cause tearing.

 

I don't own the Waves plugin, but had the same issues with RX denoise using Vegas 19.

Playhead did "scratch" and "slow down" as if it was a fancy audio-fx (like a turntable on the wrong speed).

Realtime editing was impossible using RX (it was working fine on very low end machines using e.g. Audacity or Sound Forge).

Fortunately in Vegas 20 it works smoother now.

Als when you did enveloppe an effect, say adjust from 100% to 99.999% the playhead would became extreme slow and unusable for editing.

But that was in Vegas 19, not Vegas 20.

Another issue with third-party plugins:

In VP20, plugin settings are choppy. Even if Vegas isn't playing.

Yes, in every 3rd party plugin inside Vegas 20 / build 403 (not 370).

It is now impossible to edit audio in Vegas, because of this sluggish / tearing bug in the GUI.

You can't simply set a parameter by slider / knob, because the whole mouse "freezes" or "chops" over the screen.

-------------------------------

The thing with VST3 is that they should not be active when there is no audio playing (instead of VST2, where processing is always active, even during silence).

But Vegas is always processing, even VST3, even without any sound on the speakers / monitors.

It's the same bug like those several recorded undo-states that shouldn't be there.