Before I file another CWBRN ...
 
Can anyone successfully use WAVES VST3 in FX chains in the ProChannel??? The idea is simply to have the WAVES EQ in the middle of the ProChannel chain ... so I simply dragged it there ...
 
... but with WAVES VST3 (e.g. with Puig EQ or V-EQ3) I can then select the plugin controls and assign them to knobs on the FX chain ... however, then all controls are actually "shifted" by one knob, meaning if you assign the first 3 rotary knobs of the WAVES VST3 plug to the first 3 knobs of the FX chain, the 1st FX chain knob will not do anything, the 2nd actually controlls what was assigned to FX knob #1, FX knob #3 controls what was assigned to FX knob #2 ...
 
This problem may actually be related to the other one (ACT mapping of WAVES not working) I discoverd a while ago
http://forum.cakewalk.com/CWBRN31715-ACT-remapping-of-WAVES-VST3-plugins-not-functioning-m3184115.aspx
 

What version of Sonar are you using? This is a known issue but I could swear there was a fix a while ago. I'm sure it started working properly at one point. I'm not at my DAW now so I can't check.

It's not just a waves problem. It affects all VST3 plugins.
 
I reported a similar bug in X3, but it hasnt been fixed in SPLAT:
 
1. drag a vst3 fx to a channel fx bin
2. In the inspector click display > module options > fx > show assignable controls
3. Move the bypass control (or any control)
 
RESULT: All the controls are shifted by 1 and get assigned to the wrong plugin parameter
 
The reason I think this happens is because the VST 3 HOST BYPASS parameter gets added as the first parameter in the list

it happens on X3e as well as Platinum ...
 
the fix you mention may relate to some stuff they did for VST2 in X2 (yeah, time flies!!!) because VST2 versions (even though no loner officially supported by WAVES for Sonar) do not seem to have these issues (ACT mapping weirdness, etc).

funk
It's not just a waves problem. It affects all VST3 plugins.
 
I reported a similar bug in X3:
1. drag a vst3 fx to a channel fx bin
2. In the inspector click display > module options > fx > show assignable controls
3. Move the bypass control (or any control)
 
RESULT: All the controls are shifted by 1 and get assigned to the wrong plugin parameter
 
The reason I think this happens is because the VST 3 HOST BYPASS parameter gets added as the first parameter in the list

 
thanks for letting us know ... I was also under the impression that VST 3 HOST BYPASS, which was squeezed in as the first parameter, seems to be causing this ...

I just checked and it looks like I reported that bug (CWBRN-22955) back in Jan 2014. It needs a higher priority but I'm not sure how we do that around here.

funk
I just checked and it looks like I reported that bug (CWBRN-22955) back in Jan 2014. It needs a higher priority but I'm not sure how we do that around here.

I don't know if we need to report again ... probably as it persists in Platinum and bugs in X3 are no longer addressed ...

Thanks for the heads up. I haven't really used the effects chain feature, but I'm sure I would end up using it with Waves plugins if I did, all my Waves stuff is VST3. I'll wait until they get it sorted.

Blast! Still an issue. Anyone from Cake care to comment on the prioritization of this bug?

benjaminfrog
Blast! Still an issue. Anyone from Cake care to comment on the prioritization of this bug?

At what point does it lie on Waves' end?  You'd be surprised at the DAW they officially don't support.