2012/03/11 10:43:24
John T
I've no wish to be rude, and I hope this is taken in the spirit of honest criticism in which its meant. I think X1d is, on the whole, an excellent update. But the v700 implementation looks like little more than a box ticking exercise. To give just one example of many: on the pc4k channel compressor, instead of the the enable button being on a button, and being on the fourth of the EQ / SEND buttons, like all the previous modules, enable is a *knob*. And to switch between the two states - on and off - you have to twist the knob and it changes values between 0.0 and 1.0, flipping from on to off at some arbitrary point. I mean, what? There are many other such bizarre mapping choices throughout the modules. Also, the EQ has lost its global enable / disable control from the v700. So that's one that's actually got *worse*. Really incredibly disappointed with this.
2012/03/11 13:19:29
Seth Perlstein [Cakewalk]
John T


I've no wish to be rude, and I hope this is taken in the spirit of honest criticism in which its meant. I think X1d is, on the whole, an excellent update. But the v700 implementation looks like little more than a box ticking exercise. To give just one example of many: on the pc4k channel compressor, instead of the the enable button being on a button, and being on the fourth of the EQ / SEND buttons, like all the previous modules, enable is a *knob*. And to switch between the two states - on and off - you have to twist the knob and it changes values between 0.0 and 1.0, flipping from on to off at some arbitrary point. I mean, what? There are many other such bizarre mapping choices throughout the modules. Also, the EQ has lost its global enable / disable control from the v700. So that's one that's actually got *worse*. Really incredibly disappointed with this.

You know you can globally remap the modules, just like plugins, right?


SP
2012/03/11 13:27:42
John T
I didn't know that, no. How do you do it?
2012/03/11 13:31:41
John T
That would pretty much deal with my only objection (though I still think the defaults are, um, interesting:) ). But I can't work out how to change it.
2012/03/11 13:49:06
Seth Perlstein [Cakewalk]
John T


That would pretty much deal with my only objection (though I still think the defaults are, um, interesting:) ). But I can't work out how to change it.

Ah, you will love this! And I agree the defaults are a bit wacky, but remapping is a big part of ACT and is key to streamlining workflow, IMHO.


First, make sure the VS-700c's Channel Strip Control is in EQ mode and that you have the desired PC module that you want to remap selected and controlled by the VS-700c.

Then, select the VS-700c from the list of available control surfaces in SONAR's Control Bar ACT Module (will show by default if only one control surface connected to SONAR). 

Next, using your mouse in SONAR, click the ACT Learn button in that ACT Module once so that it is blue (this is the button labelled ACT).

Then, also using your mouse in SONAR, move the controls in the PC module in series that you want to map to the VS-700c. You can do one, two, or any number you wish.

Next, move the knobs on the VS-700c in series that you want to control the parameters that you moved in the PC module. 

For example, if you want to map the PC4K Expander/ Gate's knobs from left to right across the top four VS-700c knobs, move those four PC4K knobs first with your mouse and then move the four VS-700c rotaries in series from left to right.

Finally, click the ACT Learn button again in SONAR's Control Bar to take it out of lean mode. You will see a popup window telling you that you remapped x parameters with y controls. Click Yes to confirm the remapping or click No to cancel it and try again.

Now your PC module is remapped, and you can continue to remap controls in that PC module one at a time, or in groups. And the mapping is permanent so that whenever you open that particular module it will always be mapped like that, even after you restart SONAR, your computer, etc.

BTW, this is the same method for remapping plugins and synths, and it works with any ACT controller.

HTH.

SP
2012/03/11 14:28:28
listen
Thanks for the personalized walk through instructions - I will no longer be intimidated to do it....
2012/03/11 14:31:41
John T
Thanks Seth, that's excellent information. Never thought of doing it that way, I was trying to work out where the equivalent of the plug in window ACT buton would be.
2012/03/11 14:33:10
John T
You do realise what you've done though? I was in the Real Users' Complaint Gang briefly, but now I'm back with the Fanbois. Getting picked last for team sports, not invited to the kegger... it's terrible.
2012/03/11 14:48:41
Seth Perlstein [Cakewalk]
John T


Thanks Seth, that's excellent information. Never thought of doing it that way, I was trying to work out where the equivalent of the plug in window ACT buton would be.

Ah, right. Plugins do have an ACT Learn button built-in to their GUI, but PC Modules do not, hence the need to use the global ACT Learn button in the Control Bar. I prefer all of my mappings to match the layout of the module/ plugin (control 1 = Knob 1 from left to right, etc.) so I usually remap to taste. 


I know it can take a bit to remap all of your modules exactly how you want, but once its done, its done. And if you ever screw up a mapping, just remap over it. No harm, no foul.


SP
2012/03/11 15:09:31
John T
Don't mind a bit of setup and customisation, just didn't know you could do it. Maybe that's a good FR, actually, a little ACT button as standard on the PC modules.
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account