Hi guys!
Could Anybody  get the waves plugs well mapped with Act?
Thanks! :)

I had to go through each parameter to figure out what controlled what then assigned them to the knobs buttons on my vs100
 

Ok thanks Thornton!

I did ACT remap WAVES plugs (for the vs-700 channel strip layout) and it worked, but I haven't bought any new WAVES plugs in a while so I've haven't done any remapping lately or on new WAVES releases ... anyway my ACT remaps persist between Sonar upgrades so I did not have to think about that at all ...
 
now, X-Ray is a different story - WAVES doesn't support that ...
 
 
 
 

ACT mapping is technically association between automatable parameters and virtual (SONAR internal, global) controls. Control Surface plug-in does yet another mapping then, between these virtual controls and physical controls on your hardware.
 
For example, let say "Channel tools" "Mid Gain" is ACT mapped to "ACT Slider 3". Then some plug-in (ACT MIDI, Generic Surface, VS-xxx, APro, etc) maps "Encoder 8" on your device to "ACT Slider 3". In such case, your "Encoder 8" controls "Mid Gain" in "Channel tools" (when it has the focus).
 
That procedure is not plug-in specific. You can map any parameter, which appear in the list of "Automations" (click on "Automation Lanes" and try to add an automation for the VST to see the complete list). But you can not map parameters which are not exposed there (that means VST is not informing the DAW about them).
 
There was (most probably still are, I have not checked with Platinum yet) some bugs in SONAR which make the mapping difficult. On my site you can find workaround. As I have mentioned, the mapping is global and persistent. So it should be done only once.

Thanks!
Freeflybertl, how is VS 700 working in Sonar X3 and Platinium?
Can you map everything you want?

aixmusajo
Thanks!
Freeflybertl, how is VS 700 working in Sonar X3 and Platinium?
Can you map everything you want?

so far no difference noted between X3 and Platinum ...
 
you can map everything (using ACT) that is exposed to Sonar for automation i.e. map every module in the ProChannel to the channel strip control section - except 3 parameters in the new REmatrix SOLO, which are not exposed (yet) and I reported that w/ a problem report  ...
 
for details: http://forum.cakewalk.com/FindPost/2513811
 
of course, you can also control all other plugs via ACT, but some 3rd party plugs (in the FX bin) have long lists of parameters and sleazy naming, so remapping those is still possible but you can't (at least i would not know how) change the name of the displayed parameter to something more meaningful ...
 

aixmusajo
Thanks!
Freeflybertl, how is VS 700 working in Sonar X3 and Platinium?
Can you map everything you want?

just realized that ACT mapping only works properly with VST2 plugs ... VST3 seems to get confused because the bypass button  is now parameter 0 according to the genericpluginparams.xml ...
 
I'm getting that problem in X3e as well as Platinum - double checked: VST2 maps fine, VST3 does not ...
 
anyone else's ACT not ACTing as supposed to???
 
edit: the bypass button I talk about is the one added by VST3 functionality to the plugin and I think not part of the WAVES original code...

FreeFlyBertl

aixmusajo
Thanks!
Freeflybertl, how is VS 700 working in Sonar X3 and Platinium?
Can you map everything you want?

just realized that ACT mapping only works properly with VST2 plugs ... VST3 seems to get confused because the bypass button is now parameter 0 according to the genericpluginparams.xml ...
 
I'm getting that problem in X3e as well as Platinum - double checked: VST2 maps fine, VST3 does not ...
 
anyone else's ACT not ACTing as supposed to???

Ok thanks a lot FreeFlyBertl

I can confirm, ACT mapping is broken for VST3. I have tested with Nektar Elements:
VST2 - map ok
VST3 - it either assign wrong parameter during mapping, or does not map at all (in attempt to map "Global bypass").
 
I have only one (free) Wave plug-in, and the mapping is clearly broken the same way.