Tracktion Software

lkingston · Post by **lkingston** » Mon Mar 16, 2015 6:44 pm

Maybe someone can confirm this issue.

With the latest version of Tracktion 6, if I use a Waves VST3 plugin, all the parameters show up at their zero levels. If I try to move any virtual faders, buttons, knobs, etc, the parameter will immediately slam back down to zero as soon as I release the mouse button. If I use the regular VST versions of the same Waves plugins, they work as they should. If I use other VST3 plugins, they work as they should. It is only the VST3 versions of Wavs plugins that give me this problem.

I imagine that this is a bug and not isolated to just my system.

gigazaga · Post by **gigazaga** » Mon Mar 16, 2015 8:06 pm

lkingston wrote:Maybe someone can confirm this issue.

With the latest version of Tracktion 6, if I use a Waves VST3 plugin, all the parameters show up at their zero levels. If I try to move any virtual faders, buttons, knobs, etc, the parameter will immediately slam back down to zero as soon as I release the mouse button. If I use the regular VST versions of the same Waves plugins, they work as they should. If I use other VST3 plugins, they work as they should. It is only the VST3 versions of Wavs plugins that give me this problem.

I imagine that this is a bug and not isolated to just my system.

Waves VST3 plugins do the same thing for me on OS X.

TSC · Post by **TSC** » Mon Mar 16, 2015 9:02 pm

Plugs that use wrappers like Waves do not play nicely with the VST3 format - stick to VST2 or AU and you should be good

lkingston · Post by **lkingston** » Mon Mar 16, 2015 9:07 pm

Tracktion 5 had no problem with Waves plugins in the VST3 format. Thanks Gigzaga for confirming this issue with OS X.

tonedef71 · Post by **tonedef71** » Tue Mar 17, 2015 3:30 am

Confirmed in T6 for Windows x64 -- I tried to load an instance of the Waves Codex VST3 plugin to a track and it was unusable as a virtual instrument (e.g. it is impossible to produce a sound when the gain and sustain controls are forced to a zero value).

The Waves Codex VST3 plugin did load up fine in T5 for Windows x64.

lkingston · Post by **lkingston** » Wed Apr 01, 2015 9:32 pm

Problem still there with the March 31 beta release.

tonedef71 · Post by **tonedef71** » Wed Apr 01, 2015 11:49 pm

lkingston wrote:Problem still there with the March 31 beta release.

Confirmed in T6.0.29 for Windows x64. I loaded an instance of the Waves Codex VST3 plugin to a track, and it was still unusable as a virtual instrument because all of the parameters are forced to a zero value.

Tracktion Software

KVR Audio

T6 Waves VST3 problem