Anybody could get the waves plugs well mapped with Act?

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.

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 ...
 

Thanks. I will report this.
 
I think there should be temporary a workaround to manually edit the xml files  ... to me it looked like it got cofused by the numbering of the parameters ("global bypass" being #0) ... but need a little time to try

UPDATE: this applies only to WAVES plug-ins - I could successfully map FabFilter, David Bendeth, etc as VST3 !!!

aixmusajo

FreeFlyBertl

CWBRN-31715

Hi FreeFlyBertl!
Can you explain what this means please?
Thanks a lot!

I have officially reported this issue to Cakewalk (see also here) ... and when trying it again with the just installed Braintree version and BOZ VST3 plugs, I had to realize it is problem specific to WAVES VST3 only ....
 
So I send an email to WAVES as well - however, if it turns out that's indeed a WAVES issue and not an ACT/Cakewalk problem, then it'll cost me a lot of money to be "fixed" as I have just run out of WAVES upgrades/support for most of my WAVES plugs ... d**n ...

azslow3
Hmm... I could reproduce it with iZotope Nektar elements. Is that also wave plug-in? Or do they have similar bug by "coincidence"?
Also for me, it case I just select "Global bypass" and one control in "ACT Learn" mode, after I press again "ACT Learn", it asks "One control and one parameter...", but "Ok" does not revert to normal mode ("ACT Learn" is still highlighted"). As I understand how all that works correctly, that process should not be influenced by VST at all. I mean, in case it is possible Automate some parameters, it should be possible ACT map it. The "magic" is happening in SONAR.

Hi Az,
Thanks for getting onto this. I don't have iZotope (but I'm sure Cakewalk support has it!) ... so it's good you spotted that, especially as all other VST3 I have surprisingly worked. I'll add your info to the official bug report.
 
BTW, I have encountered the same oddity with the "ACT Learn" remaining active ...
 

aixmusajo
Thanks Free!
Anybody tried to ununstal the waves in vst3 and reinstall them in vst2?
Did you have the same problem with sonar X2?
Thanks!

No need to uninstall VST3 - you can have both VST3 and VST2 installed ... just disable the auto-hiding of VST2 if VST3 is available feature in Preferences/VST and switch plug-in layout to default and you cat try with WAVES VST2 ...
 
However, I have tried VST2 (see posts above) and VST2 works as regards ACT mapping... BUT be careful, WAVES officially supports only VST3 for Sonar (been reminded of that today by WAVES support) and there were issues with VST2 WAVES in X2/X3 (GUI related issues if I remember right) ...