AZSlow
AZ Controller plug-in for Cakewalk SONAR => Discussions => Topic started by: helgenr1 on July 10, 2016, 03:43:35 PM
-
Hi all,
just wanted to let you know that I'm currently working on a preset for Softube Console 1 controller. Actually it is almost finished and I'm currently testing it. The Preset is used to control the channelstrip of the selected channel. I will improve the preset and post it here or send it to azslow for posting it in the Presets section.
Thanks alot for this fantastic control surface plug-in!
Best,
helgenr1
-
Thank you for the information!
Please do not be disappointed in case you do not get many comments, I have learned that is "normal" ;)
-
Hi AZ,
I'm progressing slowly but fine. Currently the "Console 1" is able to control the ProChannel of the selected channel / bus. I've also just finished ACT mode.
I come across a little issue with the HW Controller sending "Value: 0 OFF" for button "off" instead of "Value: 0".
(button "on" is "Value: 127" as expected).
For example: if I create a condition value = "0" it doesn't react to a value = "0 OFF". It means I cannot use the off state of the button (while it is working fine with the other HW controller).
Do you think it is possible to create a workaround in AZController? For example an option like "ignore OFF", which if enabled would ensure that any incoming "Value: 0 OFF" equals "Value: 0". Or is there another solution?
One more question: do you think it is possible to make also 3rd party ProCh modules available as Strip target? For example the CA-2A compressor and the Concrete Limiter as well as the Pc4k S-type channel compressor?
Ideally it would be possible to control the 6 controls of the FXchain module (it would be enough to allow only one FXchain module per channel).
Cheers,
helgenr1
-
I'm progressing slowly but fine. Currently the "Console 1" is able to control the ProChannel of the selected channel / bus. I've also just finished ACT mode.
I come across a little issue with the HW Controller sending "Value: 0 OFF" for button "off" instead of "Value: 0".
(button "on" is "Value: 127" as expected).
For example: if I create a condition value = "0" it doesn't react to a value = "0 OFF". It means I cannot use the off state of the button (while it is working fine with the other HW controller).
Do you think it is possible to create a workaround in AZController? For example an option like "ignore OFF", which if enabled would ensure that any incoming "Value: 0 OFF" equals "Value: 0". Or is there another solution?
If control trigger "Note" event, there is no way to prevent "Note:Off".
If control trigger other event, for example CC, you can avoid "Note:Off" behavior when the value is 0 by changing the control type from "Pad" to something else.
One more question: do you think it is possible to make also 3rd party ProCh modules available as Strip target? For example the CA-2A compressor and the Concrete Limiter as well as the Pc4k S-type channel compressor?
I will need the number of parameters and exact name for the last parameter (in the "Automation" list). That is how I detect modules (I don not have CA-2A nor other extra PC).
Ideally it would be possible to control the 6 controls of the FXchain module (it would be enough to allow only one FXchain module per channel).
If I remember right, there is no way to detect FXchain.
-
I'm progressing slowly but fine. Currently the "Console 1" is able to control the ProChannel of the selected channel / bus. I've also just finished ACT mode.
I come across a little issue with the HW Controller sending "Value: 0 OFF" for button "off" instead of "Value: 0".
(button "on" is "Value: 127" as expected).
For example: if I create a condition value = "0" it doesn't react to a value = "0 OFF". It means I cannot use the off state of the button (while it is working fine with the other HW controller).
Do you think it is possible to create a workaround in AZController? For example an option like "ignore OFF", which if enabled would ensure that any incoming "Value: 0 OFF" equals "Value: 0". Or is there another solution?
If control trigger "Note" event, there is no way to prevent "Note:Off".
If control trigger other event, for example CC, you can avoid "Note:Off" behavior when the value is 0 by changing the control type from "Pad" to something else.
Thanks alot for the hint, I assign these buttons as Slider now and they work like a charm!
One more question: do you think it is possible to make also 3rd party ProCh modules available as Strip target? For example the CA-2A compressor and the Concrete Limiter as well as the Pc4k S-type channel compressor?
I will need the number of parameters and exact name for the last parameter (in the "Automation" list). That is how I detect modules (I don not have CA-2A nor other extra PC).
Ok, here they are:
PC4K S-Type Chan Comp:
7 parameters in total.
Last parameter: Output
PC4K Exp / Gate:
7 parameters in total.
Last parameter: Side Chain
CA-2A compressor:
8 parameters in total.
Last parameter: Side-Chaining
Concrete Limiter:
6 parameters in total.
Last parameter: Bass Boost
Rematrix Solo:
6 parameters in total.
Last parameter: EQ Q
PANIPULATOR:
6 parameters in total.
Last parameter: Pan Flip
Bark of Dog:
5 parameters in total.
Last parameter: Mix
Ideally it would be possible to control the 6 controls of the FXchain module (it would be enough to allow only one FXchain module per channel).
If I remember right, there is no way to detect FXchain.
Ok, thanks alot!
Cheers,
helgenr1
-
For PC modules, try with the test version (322M) in the Download area.
-
Hi,
Thanks for implementing these modules!
I tested the PC4K comp and gate/exp as well as the CA-2A compressor and Concrete Limiter. All work perfect! There is a slight typo for CA-2A compressor: it is called "CA-2A copressor" in the AZ interface.
I will test further after the weekend.
Cheers,
helgenr1
-
Well now that I defined 4 possible track compressors, I run into issues where feedback is working only for the first defined compressor correctly. For example: enabling the S-Type Bus Compressor is not correctly feeded back to the Hardware knob (while PC76 U-Type works fine).
I think I may be doing something wrong here. This is the Action list of the Compressor on / off button:
- Set status
'MODE:1 Track' - Selected Track Volume
'MODE:1 Track' - Filter, PC76 U-Type Compressor shift 0 parameter 2
'MODE:1 Track' - Toggle
'MODE:1 Track' - Parameter Value Monitor
'MODE:1 Track' - Filter, PC4K S-Type Bus Compressor shift 0 parameter 2
'MODE:1 Track' - Toggle
'MODE:1 Track' - Parameter Value Monitor
'MODE:1 Track' - Filter, PC4K S-Type Chan Compressor shift 0 parameter 1
'MODE:1 Track' - Toggle
'MODE:1 Track' - Parameter Value Monitor
'MODE:1 Track' - Filter, CA2A copressor shift 0 parameter 1
'MODE:1 Track' - Toggle
'MODE:1 Track' - Parameter Value Monitor
'MODE:2 Bus' - Selected Bus Volume
'MODE:2 Bus' - Filter, PC76 U-Type Compressor shift 0 parameter 2
'MODE:2 Bus' - Toggle
'MODE:2 Bus' - Parameter Value Monitor
'MODE:2 Bus' - Filter, PC4K S-Type Bus Compressor shift 0 parameter 2
'MODE:2 Bus' - Toggle
'MODE:2 Bus' - Parameter Value Monitor
'MODE:2 Bus' - Filter, PC4K S-Type Chan Compressor shift 0 parameter 1
'MODE:2 Bus' - Toggle
'MODE:2 Bus' - Parameter Value Monitor
'MODE:2 Bus' - Filter, CA2A copressor shift 0 parameter 1
'MODE:2 Bus' - Toggle
'MODE:2 Bus' - Parameter Value Monitor
'MODE:3_ACT' - ACT B13 + (Bank)x3
'MODE:3_ACT' - Toggle, timeout touch
'MODE:3_ACT' - Parameter Name Monitor
'MODE:3_ACT' - Parameter Value Monitor
Well, alot of redundancy... but I think it won't work without. Do you have any idea?
While I was typing the action list into this message, I thought of how handy a clipboard functionality for AZ controller would be. I would make copying the action list into notepad or elsewhere somehwat easier.
Cheers,
helgenr1
-
Your action list in fact looks strange... You can export preset and SPP file and attach it to post, that is better way that clipboard (since has the whole information).
Let say in MODE:1, you try to toggle 4 compressors on button press. Also you need only ONE Value monitor in the whole list.
Publish your preset and I will correct it.
-
I used only one parameter value monitor before, but this didn't work either. I think the issue is, that I assume, there is only one compressor at once in the channel strip present, but I don't know which one. So what I want to achieve is the following: regardless which compressor is present, I want to be able to switch it on or off or change parameters (with the same hardware control).
I'm still learning the concept of AZ Controller, so there might be some heavy errors but all in all this Preset works already fine (only this multiple compressor choice setup isn't working atm). I have to find a logic for naming the hardware knobs / buttons, too. This is rough wip.
I've attached the Preset, it would be great if you could have a look at it!
Here is a picture of the Controller:
http://www.softube.com/images/Console1_Top.png
Cheers,
helgenr1
-
I have modified Comp_OnOff control only. I have also changed it back to "Pad" type... Why you need it in as "Fader"? Does that button in toggle mode, I mean
does it send "0" when you de-press it or when you press it? In the second case, you are right, it should be "Fader".
-
Hi!
The comp on off hardware button has two states: led on (value 127) and led off (value 0). So the Pad mode isn't working correctly as it is toggling every 2nd button press only. If I set it back to slider it is working as expected.
I see you make this work by setting the condition "Selection" to any for the first compressor type and to "invalid" for compressor type 2,3 and 4.
I applied the same principle to the rotary knob controls for other compressor params and could greatly reduce redundancy. While I see the "invalid selection" approach is working great, I have no clue why :) Could you please explain?
I installed latest build and in this build the comp modules PC4K S-Type Chan Compressor and CA-2A Compressor are not showing any (named) filter parameters now. They did in the previous build. Even if I blindly select a filter parameter, it won't control anything.
Cheers,
Helge
-
I do not remember I have changed anything for PC4K, but in my CA-2A name definition was a type... So at least CA-2A should be "redefined". To see compressors and parameters, you need a project which have them. Also you should focus the track which has them, otherwise they are "invisible" for plug-in and so not shown.
"Selection: invalid" has the following logic. "Try to find some module in ProChannel". If it is found, "Selection" is set to "valid" and so other selecting actions are not executed. If the first module is not found, an attempt to find another module is executed. And so on.
Value and Name monitors work with whatever parameter is selected, including ACT and PC modules. So you need only one set of them. The only exception is for "Automation arm", and here the reaction is not trivial (to display correct value from one of two monitors).
-
Thanks alot for explaining, I think I get the idea now :)
Please find attached my reworked version of the Preset. I reassigned the controls for the CA-2A and so far all is working. I have to test more.
I can't seem to get rid of several detached logic controls. If you have a hint for that one, please let me know.
Cheers,
helgenr1
-
I had no problem deleting all Detached controls in your preset (select it in Hardware tab and press delete). So somehow I can not reproduce your problem. Is "Delete" button is not enabled when you select these controls?
-
I think only the UI_ named controls are detached and not used for now (5 total), but even if I delete these on the Hardware tab, I still see quite some detached controls on the Logic tab: Detached 35, 36, 38, 39, 40, 52 and 53. I think these are not bound to any hardware control or at least I don't know how to find out to which one (so I could delete that control on hardware tab). The current Preset is attached.
Cheers,
helgenr1
-
Detached are only logical controls which are indicated as "Detached XX". These you can select in the lower box of Hardware tab and delete there.
To delete Hardware controls, the best way is to detach and delete the logical control (to avoid it is hanging as "detached"), then delete hardware context (still in Hardware tab) and then delete the control (in the Options tab). A bit complicated, but that is not every day operation...
-
Thanks!! I didn't notice that I can delete the detached controls in the lower box of hardware tab.
Cheers,
helgenr1
-
Since from the beginning AZ Controller was developed with MPK mini in mind, and this controller has 4 hardware "presets" which are easy to switch, there is a concept of Hardware Controls, Hardware Contexts and Logical Controls. Single Hardware control can have several contexts (presets) in which DAW (AZ Controller) see it as different Logical controls. The knowledge that real control is still the same is used to correctly process knobs with non direct modes (catch or instant).
All that is not used in presets published on this site. Most hardware controllers have sufficient amount of controls to organize "software modes" (without changing hardware presets).
-
Preset is ready, I posted it here:
http://www.azslow.com/index.php/topic,324.0.html
Cheers,
helgenr1
-
Thanks for sharing! I have moved your post into Presets section.