AZSlow

AZ Controller plug-in for Cakewalk SONAR => Discussions => Topic started by: AWRontheRISE on January 23, 2026, 03:50:58 PM

Title: Are these things possible with AZController?
Post by: AWRontheRISE on January 23, 2026, 03:50:58 PM
Hello,

Been using SONAR for years, but very new to AZController.  I'm beginning to play around with AZController with my Behringer X-Touch Mini and just wanted to ask if what I want to do is indeed possible?

1. Can I map encoders to send level knobs across several tracks?  I've used the quick start to map the encoders to send level knobs on the GUI, but have only been successful controlling send knobs on one track at a time.  I would like to avoid having to "focus" on a track.  I think there is maybe a way address each track by assigning an offset from the first track, however I have not got that working so far. 

2. Can I control VST effect parameters in any way, without the requirement that the VST panel be in focus?  I was thinking maybe by using automation lanes it might be possible.

3. Can I accomplish 1 & 2 AND have feedback to the LED indicators on my physical device?


Thank you,
Aaron
Title: Re: Are these things possible with AZController?
Post by: azslow3 on January 23, 2026, 06:23:15 PM
Hello Aaron,

With X-Touch Mini I suggest you try my preset for it: https://www.azslow.com/index.php/topic,377.0.html

And general answer on all your questions: yes  ;)

But there are details...

For 1. you need to decide sends from which tracks you want control (global position, offset in WAI, offset from focused, by name). And then which sends on this track.

For 2. possible, but in most cases not practical. You will need to configure exact track, FX and parameter for each control. ACT dynamic mapping is faster. Sure, when you always want control particular parameters of particular effects (f.e. your EQ of choice), controlling directly, sometimes for several tracks in parallel, make sense. Original Cakewalk Mackie plug-in is using this approach.
But note ACT dynamic mapping support "locking". So you decide which plug-in you control and "lock". You then can focus / modify other effects, the device will continue controlling the plug-in you have locked (my Mini preset is using locking).

For 3. when preset for AZ Controller is configured "nice", you have feedback for encoders and buttons independent from what they control. They just indicate current value, whatever it is. Note that in some cases there is no "value" (f.e. you trigger Cakewalk Command, they don't have values even when that make sense, like with toggling visible elements)
Title: Re: Are these things possible with AZController?
Post by: AWRontheRISE on January 23, 2026, 08:23:49 PM
Thank you for the quick response!

Since controlling VST effects sounds tricky, I think I may handle that in Gig Performer instead.  I can then use the Gig Performer Relayer VST to bring the processed Gig Performer audio into SONAR.  This will be used with the X Touch Mini.

As for the many Sends I have in SONAR, I'm going to use the 24 encoders on my Novation Launch XL MK3 to attempt to control 24 send knobs on the SONAR GUI, with feedback.  I also would like to use the Push function of each encoder to enable or disable the send (or set to zero) if possible.  This will be to set levels for multiple headphone mixes.  I plan to have a custom preset on the Launch for each headphone mix.

Title: Re: Are these things possible with AZController?
Post by: azslow3 on January 24, 2026, 08:50:23 PM
Not sure how good Gig Performer in controlling VSTs using XTouch, if you want control fixed number of particular VST parameters that is not hard to do directly in AZ Controller. If you create some "modular synth", some container VST is reasonable way to go (for FXes Cakewalk has own container).

For Novation, AZ Controller is the way to go (in case you want control Cakewalk). Other plug-ins simply don't support the number of controls it has. But do this by "send number". Even so it is possible to do by names, there is some long standing bug which mess send names. I mean "WAI track X send Y" works find, "WAI track X send to 'Drum bus'" can be buggy (depends from FXes with side-chain inputs used in the project).
Title: Re: Are these things possible with AZController?
Post by: AWRontheRISE on January 25, 2026, 05:24:27 PM
I've a couple more questions now as I'm starting to try and build a simple project to help me learn to use AZ Controller.

1. What is the best way to select a specific track "by name"?  I almost have something working in the image below, but I have to manually switch between "Tack 1" and "Track 2" from the drop down menu in the image to make it work.

https://ibb.co/93smVgnL


2. Can I also select a bus "by name" in the same way I can select a track by name?  (I would like to move some Send knobs on some busses too)
Title: Re: Are these things possible with AZController?
Post by: AWRontheRISE on January 26, 2026, 02:44:28 AM
I answered my questions above and got those things working.  Now I'm working on adding feedback so that when the Send knobs are moved with the mouse, CC messages are sent to the Launch to keep the Encoder LEDs synced.
Title: Re: Are these things possible with AZController?
Post by: azslow3 on January 26, 2026, 10:08:41 AM
Ring feedback example approach is in https://www.azslow.com/index.php/topic,130.0.html
Normally you use "<Use Ctrl. MIDI>" in the MIDI Action, note you need to set "Value" option (default is '0', so constant).
That simple is just in case rings internally react reasonably on 0-127 values (AZ Controller map values 0..1, used in Cakewalk for all parameters, into 0-127 MIDI range). But many LED rings required "special mapping" (check the documentation for Launch). Sometimes it is like Mackie encoder rings, in this case "Prod. spec. send" "VPot" may work. But it is also possible create a "function" which does required conversion, Software State with the number of segments, "Set State" "from value" for it. And then use conditional MIDI for each state. If there are different "modes" (pan, left-to-right, right-to-left, etc.), a bit more evaluation is required...