Step By Step Tutorial for LED button

[cupax]

Hello.

I'm a begginer and need a step by step tutorial how to turn on or off the LED light inside my controller's hardware button (X Touch One, set to Mackie mode).
I managed to program the hardware button to turn "Mute" on and off inside Cakewalk for the selected channel, but the LED inside the hardware button is always off, not following the Mute status of that channel.
What I want to do:
- I want to click the hardware button on my controller to "MUTE" the selected channel in Cakewalk while at the same time the hardware button's LED light turns on. Pressing it again it would turn off Mute and also the LED would turn off.
Please help. TNX.

[azslow3]

There is http://www.azslow.com/index.php/topic,336.0.html  (with example preset). Feedback is "advanced" topic.

In short, once you have "Mute" button, so actions list:
* <current> track mute
* set value <toggle>
append
* monitor <parameter value>

In the Feedback section (so, in the monitor) add single action:
* MIDI <use control> <value>.

In your particular case that should control LED.

[cupax]

Hi.

Thank you for your reply, but it didn't help me, it wasn't clear enough.
I believe the logic should be:
- monitor the value of mute (engaged or disengaged)
- if mute = engaged, then LED=on
- if mute = disengaged, then LED=off

How do you define the status for LED ON and LED OFF based on monitor reading of mute status?

[azslow3]

If you have implemented Mute control following "Quick start" tutorial, I think it should be clear how to add 2 mentioned Actions (one in Logic following by one in Feedback). I have mentioned options for these actions you need to change (leaving other options as defaults). I don't think I can be more detailed...

How monitoring is working in AZ Controller is explained in all details in already mentioned tutorial. Yes, that is lengthy thread with relatively complicated technic. But DAWs + controllers can't be explained in several words, especially feedback from the DAW. Usually that is programmed in C++ (python, JS, DAW dependent...) by (semi)professional programmers. AZ Controller can be used without such skills, but understanding what is going on is still required.

[Trebot]

I'm new to this but here's how I did it for my controller's loop button. I went to the logic tab and edited "loop on/off". I changed no existing actions. I added a new action "monitor". I set that to "monitor state" and set the state to "loop". Then under the feedback tab I found "loop on/off: state monitor". I added a new action. In the first drop down box I set 'loop(on)". In the second drop down box I chose "MIDI". In the third I chose "Note" then set my midi channel, the note number my button sends, a value of 127, and "0 sends on". I copied and pasted that action and changed 2 settings on this copied action: "loop(off)" and set value to 0. This may not be the best or easiest way but it worked.

[azslow3]

And that is correct for "Loop". Loop is so called "system state set", AZ Controller change it in sync with Cakewalk "loop". So this monitor can be anywhere in the Logic tab and the result will be the same.

"Mute" is different, there is no general Mute. Every strip has Mute button (and there are "Automatable mute" for strips and "Rude mute"...). So, there must be some way to tell which mute you want to control. In AZ Controller "Mute" is parameter you can make "current", using Strip Action. There you select the strip and the type of mute. Once "current", parameter can be used by Value and Monitor <parameter value> Actions. So in such case Monitor should be in the same Logic list, after Mute is selected.

For MIDI actions your solution is good general solution. It explicitly mention which MIDI message to send in which case. What I have mentioned is solution for Mute and Mackie: LED use the same MIDI message as the button send (some not Mackie controllers use different messages for buttons and corresponding LEDs), for such case there is <Use Ctrl MIDI> parameter for MIDI Action, instead of specifying it explicitly. And in Parameter Monitor (so, works for Mute but not for Loop) there is "value", so setting Value parameter of MIDI Action to "value" applies it.