AZSlow
AZ Controller plug-in for Cakewalk SONAR => Wishes => Topic started by: bbergen on December 14, 2015, 03:45:19 PM
-
Getting my Novation Launch Control this week, what do you suggest I read up on since you do not have a preset already for it like the one that I use for my FaderPort?
I'm getting it to control only my Pro Channel eq in Sonar Platinum.
-
I suggest I prepare the first preset for you, it will take less time for me then explicitly explaining which part of the documentation you should understand and that approach let you concentrate on more music related tasks ;)
To start using the result, you will need to understand at least principal of Novation Launch Control (NLC) MIDI assignment (Novation Lauch Control Editor) and how to assign controls in AZCtrl preset (Quick start tutorial). In practice, any factory preset will work on NLC side and you do not have to edit something. And "Quck start" tutorial will take 5 minutes at most to complete. For assignment within preset I give you, you need to understand just a small part of it: touch control, select corresponding control in preset and press "Assign MIDI". Plan 10-15 minutes to assign all controls. I also can connect to you with TeamViewer to help with that task in case you have some problem (will take ~5 minutes).
But... before all that we should agree with layout. NLC has 16 knobs (not endless), 8 pads and 4 buttons. 2 template switching buttons can not be used for DAW controlling. Pads have Red/Greed LEDs, buttons Red LEDs.
PC EQ has:
* 4 full bands with Freq/Gain/Q, On/Off switches, LH and HF with Shelf switch
* HPF, LPF with Freq/Slope and On/Off switches
* EQ type
* Gloss
* EQ On/Off
In total we need 16 knobs and 11 buttons. And NLC has sufficient controls for that. But controls are places in 2 rows and 4 separate buttons, so it is up to you to decide which knob/button does which function. You can decide that during assignment, but I need to know which (3) switches you want assign to buttons to program LEDs correctly.
LED. We basically have On/Off. Off is LED off. Which color you want for On?
NLC has normal Knobs. That means when you change track they will be not "in position". There are several approaches to deal with that:
1) parameter jumps to knob position when you start changing it.
2) knob should be moved to current parameter value before it does any changes.
3) knob change current parameter smoothly from whatever position, but when value and position mismatch initial resolution is lower (till/if they are matched)
4) endless encoder imitation with dead zone (value is not changed when you turn the knob left in the right part and turn knob right in the left part)
MIDI knobs have resolution 128, depending on purpose that can be too coarse, especially for the Frequency. The only variant with hi resolution support is (4), but practical combinations are (2,3,4 coarse)+(4 fine) with "Shift" button (we still have 1 button free for that!). So without shift pressed you set coarse value, with shift you fine tune it.
While you can change the settings later (5-10 seconds per knob), what you prefer to have initially?
Once you give me the answers on these 2 questions, I will prepare the preset.
-
I have color-coded knobs on order which should arrive at approximately the same time as the NLC.
I'll post a pic so it'll make sense once I have color-coded the NLC to match the PC EQ.
Thanks so much for your help!
-
I have started preparing the preset (since it is not big, I am also close to the finish... just need colors and control mode), and I propose to use Shift for buttons. That will free quite some buttons/pads you can use for other purpose later.
Proposed combinations:
* EQ On/Off, Shift: EQ Style
* HP On/Off, Shift: Track focus. When track focus is enabled (default), you control EQ on the strip (track/bus) which you focus in sonar. When it is disabled, you "lock" the EQ you currently control.
* LF/HF On/Off, Shift: Shelf
* LP On/Off, Shift: Gloss
Shift will function as shift when you use it (press other button(s) while it is pressed) or CapsLock when pressed/released alone.
LED under pads with Shift combinations will show correct current status based on Shift. We can also use colors for coding, for example EQ On/Off LED: Off/Green when means On/Off and Dark/light red + Dark/light cyan when indicates the style.
What you think?
-
Sounds great, you are wonderful!
;D
-
The choice of colors is limited (only 2 LEDs per pad), I have assigned what I think is reasonable. Also I have constructed preset in "object oriented" style, so changing Knobs reaction can be done in one place for all knobs (the same for LEDs, except special cases with Shift, EQ Style and Track focus).
WARNING: in case you already use AZCtrl and you are going to insert yet another instance of it into Sonar, you can hit nasty Control Surfaces presets bug in sonar. NEVER open property pages of 2 instances simultaneously. NEVER save preset without typing correct name for the preset. You will always see the same preset name in all instances, but they will use whatever presets you set. So, everything works fine but looks funny. Make a backup of all your good AZCtrl presets periodically in case you change them (from Utilities/Cakewalk Plug-in Manager/Control Surfaces/AZ Controller/"Export..."). You will overwrite presets at some unlucky moment when you forget about the bug...
You need 0.4r2 AZCtrl, still in Test downloads section (it could be released long time ago).
Using approach described in "Quick start", assign MIDI to all controls with names "B:" for buttons/pads and "K:" for Knobs. Do not assign anything to other "controls" (with underscored names).
Keep in mind that I have constructed the preset without a possibility to test it, especially LED reaction. So there are some bugs for sure, just let me know and I fix them.
EDIT: preset updated 20.12.15
EDIT: preset updated 21.12.15
EDIT: preset updated 22.12.15
EDIT: preset updated 08.01.16
-
Received the Launch Control today and re-knobbed it.
How's this for knob and button assignments?
Top Row Knob 1 - HP Slope
Top Row Knob 2 - Low Freq
Top Row Knob 3 - Low Gain
Top Row Knob 4 - Lo Mid Freq
Top Row Knob 5 - Hi Mid Freq
Top Row Knob 6 - High Gain
Top Row Knob 7 - High Freq
Top Row Knob 8 - LP Slope
Bottom Row Knob 1 - HP Freq
Bottom Row Knob 2 - Low Q
Bottom Row Knob 3 - Lo Mid Gain
Bottom Row Knob 4 - Lo Mid Q
Bottom Row Knob 5 - Hi Mid Q
Bottom Row Knob 6 - Hi Mid Gain
Bottom Row Knob 7 - Hi Q
Bottom Row Knob 8 - LP Freq
Button 1 - HP On/Off - Green On/Red Off
Button 2 - Low On/Off - Green On/Red Off
Button 3 - Low Shelf Enable- Green On/Red Off
Button 4 - Lo Mid On/Off - Green On/Red Off
Button 5 - Hi Mid On/Off - Green On/Red Off
Button 6 - High Shelf Enable - Green On/Red Off
Button 7 - High On/Off - Green On/Red Off
Button 8 - LP On/Off - Green On/Red Off
-
I can change the color in the preset, but I can not do the assignment. Have you tried that alignment already?
-
Not yet, was waiting until I received the controller.
Will try it today.
-
Ok, I give, what do I do with the .spp file that you attached earlier?
-
Ok, I'm not seeing anything under Last MIDI Event.
I guess that means it's not going to work with AZController...
-
Ok, I'm not seeing anything under Last MIDI Event.
I guess that means it's not going to work with AZController...
ANY MIDI controller can work with AZ Controller ;)
1) check that SONAR see it.
1.a) check that corresponding MIDI IN is enabled in Preferences/MIDI
1.b) check that you can record it into MIDI track (it will probably produce some CC, but still you should see something in PRV after recording)
2) check that some AZCtrl instance (as I understand you have several instances!) has LC as the input. You can access AZCtrl property page from Utilities Sonar menu, here you should see all defined.
SPP file you "Import" using Cakewalk Plug-in manager from Utilities menu, select "Control surfaces", "AZ Controller", "Import..." and select SPP file that. It will add "Launch Control" to the list of AZCtrl presets. Note that you need test version, 0.4r2.
We can organize short TeamViewer session tomorrow to setup everything withing 15-20 minutes.
-
It wasn't until I inserted a midi track on a blank project assigned the LC as input did any midi events get recognized.
Now AZController is recognizing midi events.
All the knobs and buttons are transmitting on Ch. 15 as follows
Knobs - 1st Row
1 - CC21
2 - CC22
3 - CC23
4 - CC24
5 - CC25
6 - CC26
7 - CC27
8 - CC28
Knobs - 2nd row
1 - CC 41
2 - CC 42
3 - CC 43
4 - CC 44
5 - CC 45
6 - CC 46
7 - CC 47
8 - CC 48
Buttons
1 - N:9 Value:0 OFF (value 127 when pressed)
2 - N:10 Value:0 OFF (value 127 when pressed)
3 - N:11 Value:0 OFF (value 127 when pressed)
4 - N:12 Value:0 OFF (value 127 when pressed)
5 - N:25 Value:0 OFF (value 127 when pressed)
6 - N:26 Value:0 OFF (value 127 when pressed)
7 - N:27 Value:0 OFF (value 127 when pressed)
8 - N:28 Value:0 OFF (value 127 when pressed)
I can change all of them to whatever you'd like with the Launch Control Editor...
-
I have updated the preset, so re-download / re-import it.
Everything should work, I have made all assignments and I have changed colors.
One difference: buttons 3 and 6 are "Shift" and "EQ On/Off" respectively. May be not the best "Shift" placement, but you at least can check how all that works.
-
Everything works as you said it does!
Woot! Woot!
Are you using full brightness for the buttons?
According to page 3 of the LC Programmer's Reference Guide, each led can be set to four values for brightness.
0 Off
1 Low Brightness
2 Medium Brightness
3 Full Brightness
For the on state, can we use the yellow color instead of green for button 3, use Low Brightness for all buttons except 6 and Full Brightness for button 6 to differentiate their functions by sight?
For the off state, can we use the amber color instead of red for button 3, use Low Brightness for all buttons except 6 and Full Brightness for button 6 to differentiate their functions by sight?
-
On a side note, I wish Cakewalk would add an option to use "friendly names" for controllers.
I put in a request for that feature, maybe you could too?
-
Are the up and down buttons supposed to change tracks?
The up is sending Ch. 15 CC114 value 127 when pressed.
The down button is sending Ch. 15 CC115 value 127 when pressed.
Can we use the right and left buttons for on/off instead of button 6?
The right button (which could be on) is sending Ch. 15 CC117 value 127 when pressed.
The left button (which could be off) is sending Ch. 15 CC115 value 127 when pressed.
That way we could use buttons 3 and 6 the way I had originally imagined with the following color change:
Button 3 - Low Shelf Enable- Yellow On/Amber Off
Button 6 - High Shelf Enable - Yellow On/Amber Off
and use them all at full brightness.
-
Just noticed an irregularity, when I hit the stop button on the transport control on the screen in Sonar, the LC changes from the factory template mode to the user template mode and the lc stops working as intended until you hit the factory template button.
There are no midi events associated with the factory template button here's what's associated with the user template button:
SysEx:<00 20 29> 2 a 77 0
-
Ok, took care of the SysEx/User Template Button issue by disabling System Exclusive in Sonar.
-
I have updated the preset:
1) On/Off colors are changed to LowRed/LowGreen
2) Shift colors are Amber/Yellow (and so for buttons with Shifted functionality)
3) EQ Style colors are Greed/Red/Amber/Yellow (full).
4) Up/Down move strip focus
I have not changed Left/Right since you write Left has CC115, but you also write down has CC115...
Note that buttons have one LED only (red).
Once you clarify that, I can move:
a) Shift (current 3) to "Left"
b) On/Off and style (current 6) to "Right". Style and On/Off are forced to use the same color, Red. Not sure buttons have intensity, I hope so.
c) 3 and 6 change to your original proposal
About SysEx and preset, check in Sonar preferences:
1) MIDI Playback and Recording: unset "Echo System Exclusive" and any ports under
2) Project MIDI: unset (in case you do not need it) Transmit MMC, MIDI Start/Continue/..., MIDI Sync Output ports, Transmit MTC and MTC Output Ports.
-
Oops, left button is Ch:15 CC116 value 127 when pressed.
right button is Ch:15 CC117 value 127 when pressed.
I apologize.
The double checked what messages the up and down buttons are sending and what I wrote is correct but they are working in opposite order with the preset, up is going down and down is going up.
Go ahead and take them all back to full brightness, the low brightness is kind of useless.
-
Preset updated. Changes:
1) normal pad colors are again Red/Green (full)
2) Style colors: Black, Yello, MidAmber, Amber (so, different from normal)
3) Pad 3 - LF Shelf
4) Pad 6 - HF Shelf + EQ Style with shift
5) Up/Down fixed
6) Left is Shift now
7) Right is EQ On/Off now
Left/Right are indicated with Red when On. No light when Off.
-
This is working incredibly!!!
Can you make one color change to buttons 3 & 6?
Button 3 - Low Shelf Enable- Yellow=On/Amber=Off - Both colors at full brightness
Button 6 - High Shelf Enable - Yellow=On/Amber=Off - Both colors at full brightness
Not quite sure what purpose the shift button does now, how about the left button turning gloss on/off instead of being a shift button...
-
One other thing, since this preset is geared towards the LC controlling the PCEQ, what do you think about renaming the preset to LaunchControl-PCEQ so if you add this preset in your builds, it will be evident that this is a specialized preset?
-
This is working incredibly!!!
Can you make one color change to buttons 3 & 6?
Button 3 - Low Shelf Enable- Yellow=On/Amber=Off - Both colors at full brightness
Button 6 - High Shelf Enable - Yellow=On/Amber=Off - Both colors at full brightness
Not quite sure what purpose the shift button does now, how about the left button turning gloss on/off instead of being a shift button...
Shift is still used for:
a) Follow focus/do not follow focus
b) Gloss
c) EQ Style.
So, there are is 1 button (left, which is currently Shift) and 3 functions required to cover all.
When a button has shifted function, it is lighted Yellow/Amber when Shift is pressed. In case I change 3/6 colors, that will be easy to overseen.
Also (I know you do not want it now, but just in case...) to add more functionality we need the Shift. For example Shift+Up can switch between EQ and Comp mode. I think it is always good to keep something in reserve, and in case we eliminate shift, we loose such reserve.
What you think?
One other thing, since this preset is geared towards the LC controlling the PCEQ, what do you think about renaming the preset to LaunchControl-PCEQ so if you add this preset in your builds, it will be evident that this is a specialized preset?
Good idea!
Just one note: I am not adding manually made presets into builds, I just post them on forum in the Presets section. In builds are code generated presets only (like Faderport) which was easier to construct for me using "C" (due to complexity, but mostly historically).
-
Ok, I understand what you mean, in that case, can we just change 3 and 6 as I suggested and make the shift function buttons low brightness?
-
Also, I sent you a PM
-
Ok, I understand what you mean, in that case, can we just change 3 and 6 as I suggested and make the shift function buttons low brightness?
The preset is updated (btn 3 and 6 Amber/Yellow, EQ Style on 6 Green/MidGreen/Red/No light). Note the new name (of file and preset)
Also, I sent you a PM
Answered ;)
-
Thank you, thank you and thank you!!!
-
Thank you, thank you and thank you!!!
:)
I forgot to remind you about Shift use with Knobs. In current configuration, knobs in shifted mode work like fine tuning endless encoders with "dead zone". I have found it useful for my MPK mini, but you can try other settings:
a) open AZCtrl property page (SONAR utilities menu)
b) switch to the "Logic" tab
c) in the "Logical Control" drop box select "((None)) _fSetValue". You should see 2 actions, one with "Shift:Off" and another with "Shift:On".
d) Select the second one (with "Shift:On"). In the "Action configuration" you can adjust "0.2% per tick" to adjust granularity (fines).
e) Select the first one (with "Shift:Off"). In the "Action configuration" you can try to change "Catch" to "Direct" or "Instant". You can also change the response curve from "Linear" to "Convex".
The effect is immediate (no preset save/load required), use any knob to test the result. But "Logic" Tab will switch to this control action list, so you need to reselect "_fSetValue" for future adjustments.
There is a way to avoid switching for particular knob: in the "Options" Tab "Hardware controls" section, find the knob in question, change "Rotary" type to "System" and press "Save" near it. That will work correctly for knobs, but not for pad/buttons
I am personally a big fan of "Instant" "Convex" combination. It works best when the knob is near center position. "Instant" takes away annoying for me "no reaction" till the value is matched. "Convex" gives more precision in the middle (where I normally need it) while reducing precision toward ends. Sure that does not work nice with "linear" parameters like frequency...
At the moment, the settings are common for all Knobs. Just to make them easy adjustable globally. But it is possible (and easy for me, also I can write how you can do this with several clicks) to make different settings for each knob separately.
In case you still prefer "Catch" approach. I can make some Pad change the color (or/and blink) for some time (let say 2 second) in case you use any knob and it is in "Unmatched" region, once "Matched" the pad will revert to normal indication immediately.
-
Thanks for that additional information!
You guys have a Merry Christmas!!!
-
Today (I have 00:15 here) is mother-in-law birthday... And only then Merry Christmas 8)
-
I don't know how to word this but I'll try...
Is there a "refresh rate" setting available.
I was working on eq'ing a Kontakt piano library while the track was playing and the response was lagging quite a bit.
-
Another question, can the controller software determine if a track is frozen (effects are frozen too) so all buttons and knobs will turn off when that track is highlighted?
-
This time I have bad news for you, sorry... So, the answers on both questions are "No" :(
I am limited by Sonar API and plug-in reaction.
For the first question. Theoretically, everything is happening without delay. I mean the controller input is triggering AZCtrl as soon as you move the control and AZCtrl requests parameter change without delay. Unfortunately, plug-ins are sometimes reacting slow on Automation change requests. I am not sure about the exact place that is happening, either Sonar is "rendering in advance" or has some internal locks or plug-ins themselves use updates not instantly. Note that changing parameters in GUI goes different route (GUI is a part of plug-in).
Freezing is simply not exposed for Control Surfaces. Unlike the first problem, that is more or less strait forward to change on Sonar(!) side. But I have no power to do that.
-
(I had to leave while writing the last answer)
A bit more positive info ;)
When I control some parameters, I get big "video lag". I mean if I rapidly change EQ frequency (in EQs GUI or by surface, not only in PC EQ), not even "Now time" is updating during playback. But the frequency is changed as expected and after a while the screen is updated. So please check that you really have significant to you lag in audio and not just in graphics. I have old and slow computers and I was thinking that is logical consequence of that. But may be there is something in Sonar on purpose to prevent audio drops (rapid asynchronous graphic changes can take significant CPU/GPU time).
While freezing is not seen from Control Surface, there is some generic trick for the problem. There is "Control Strips visible in" option in the Sonar Control Surfaces preferences. You can say CS work with Console View only, then decouple visibility between track and console views in the Track Manager and hide unwanted tracks from the console view. After that, CS does not "see" hidden tracks at all (also "Next/Previous track" buttons skip them!) while you still have mouse control in the track view.
Unfortunately, Sonar has several bugs there. For example "Strips/Hide frozen" is not working for MIDI/Instrument tracks. And even in case they fix that, CS is still observe tracks hidden that way. The only way to really hide something is explicitly mark it as hidden.
Note that you can follow track view, hide tracks there to still have full console. Till you use folders that normally works fine.
-
Ok, thanks!
The lag was substantial on soft synth audio tracks but not recorded audio tracks.
Thought I'd ask.
Thanks again!
-
I haven't figure out what to disable to prevent this from happening but on one template in particular (my mastering template), when I press the play button on the screen transport, it switches the LC from Factory Templates to User Templates.
Any ideas?
-
Found it
Preferences > MIDI > uncheck "Zero Controllers When Play Stops" did it.
-
Happy New Year!!!
How is it possible for me to change button colors?
I want to change buttons 1,2,4,5,7 & 8 to red = on and no color = off.
I have printed labels for all the controls and waiting on some new color-coded knobs, better than the ones that I had already ordered.
Once they're in, I'll post a pic.
-
Hally New Year!
I try to explain first, in case you want modify yourself. But I can modify the colors and upload the result. I just have not understood which from these 2 variants you prefer by "is it possible for me" statement ;)
Button/Pads colors are controlled from Monitors (Feedback section, everything started with "B:", so all feedback lists except "_Track focus"). Since colors represent different information, lists are not completely the same. General idea:
a) set state (variable) "Color" to required value dependent on conditions.
b) send corresponding comment to LC (implemented in _fColor2LED in the Logic, you do not need to modify it since all possible colors are already there)
One helper function (in the Logic list) is "generic On/Off" for Pads "_fPadLED On/Off" (HMF On/Off, LMF On/Off, HF On/Off, LF On/Off). Another is for pads with shift function, "_fPad LED With Shift" (LP On/Off +Gloss) . Other pads/buttons have explicit lists.
And so:
1) for HMF/LMF/HF/LF On/Off change colors in "_fPadLED On/OFF" (in Logic)
2) for LP On/Off + Gloss change colors in "_fPad LED With Shift" (in Logic)
3) for other change colors in the corresponding list (in Feedback).
-
Thank you for the explanation.
Had a chance to play with it and it's simple enough.
I appreciate it!
-
I have updated the preset... and I have just realized that you have updated the last message ;)
-
What does the shifted function of the HP button do?
What exactly is track focus in this particular instance?
Is it meant to fly out the eq display while in ProCh view?
-
What does the shifted function of the HP button do?
What exactly is track focus in this particular instance?
Only one strip is Sonar can have "focus". The one you normally click, the one you see in the Track Inspector.
Shift+HP toggle following it. Let say you click on Guitar track. You can control its EQ then. Now let say you want adjust/edit VOX while still controlling Guitar EQ from LC. You press Shift+HP while the focus is on Guitar. From that point till you again press Shift+HP your LC should control Guitar EQ. Independent from what else you do in Sonar (well... in case you do not insert/move tracks before Guitar...).
Is it meant to fly out the eq display while in ProCh view?
Unfortunately that can not be controlled from surface.
-
Thanks for the explanation!
My newer/better knobs came in today from the UK.
The labels aren't the most perfect labeling job ever done but hey, it works!
Here she is:
-
Nice Knobs ;)
-
;D
-
Thanks again for this fine app and creating the LC preset for me!
It works great!!!
-
I am glad to know it works fine.
In case you spot some crashes, please let me know. Unfortunately I have seen some with ProChannel under Mackie Control preset, also with MC native plug-in. My guess it does not come from AZCtrl directly, probably parameters monitoring related somewhere inside Sonar. Extremely rare and not reproducible so far, so any reports can help (me and Cakewalk) to find and fix the origin.
-
Just noticed that the HP slope pot works in the opposite direction that it should.
What do I do to fix that? (don't want to lose my button color settings so I'd like to make the change on my end)
-
Open "_fSetValue", click on the first Action "Catch Linear, timeout touch".
Click on "Copy" button (on the right).
Change to "HP slope", click on the last Action "Call ((None)) _fSetValue". Click on "Delete" button.
Click on "Paste" button (so, you have replaced the "Call" with "Catch Linear").
Keeping pasted Action selected, check "Reverse" box (at the bottom).
I think "Fine tuning" (with Shift) is not interesting for this parameter, so I have not copied it.
-
That fixed it, thank you!
-
Just for future reference for someone that might use this preset, sometimes the LC goes into User Template mode and I haven't been able to drill down the exact reason why, I thought I had it but it happens, sporadically.
My workaround is, by using the Novation Launch Control Editor from Novation, I copied the factory template settings to all 8 user template positions and now it's a moot point. It works correctly whether it's in factory or user template mode.