AZSlow

These controllers are not "hardware MIDI" controllers. They communicate throw NI software, which in turn represents itself as MIDI devices.
NI has so called "DAW integration mode" which this preset (and official DAW integrations) use. Till it is activated, NI represents the device as a "simple MIDI controller".
Note there is MIDI mode switch, to control synths directly and with different (configurable in Kontrol) messages. "DAW controlling" MIDI communication is fixed.
All possible messages and the set of LEDs which a DAW can get/set is listed in the first post (can be outdated, the information is 5+ years old). NI Machine can use more (not a surprise...).

AZ Controller is sufficiently flexible to react differently on different values for the same CC. So there was no problem to configure 4D.

"Tap tempo" preset is a fancy workaround, effectively it is a "computer keyboard macro" which is working with corresponding Cakewalk dialog.
As any other preset, it can be "merged" into KK preset. But sorry, there is no easy way to "copy/paste" between presets. It will have to be reproduced manually (so created new control and TapState Software Set and re-creating all corresponding Actions in it, including Feedback for the Timer).
"Export text preset" is a good way to have the reference, or another AZ Controller instance (not Cakewalk can mess with presets, better use AZCInstances and transfer preset throw "Export/Import binary preset" in case you want more then one AZ Controller).
O

Hello Alexey,  Thank you for doing all of this. I think it's time to get you another coffee! or flowers (for the Wife Of coarse) sorry I don't remember.

I have a Komplete Kontrol s88 MKII.  I had the MKI prior and I had it setup just the way I wanted.  With the MkII they replaced the RWD and FFW with METRO AND TEMPO That would be no problem but the buttons are not recognized so I can't assign them.  I tested this M32 preset just to see what you did and to my surprise a lot more buttons are exposed and function on my s88 MKII Including the actual shift, undo, redo, 4D press, etc.  none of this was exposed before.  However, I had already setup the 4D rotor with functions I like, and I can not change currently with this preset because the CC messages previously were separate for Left, Right, Up, Down, Rotate Left, Rotate Right, and press was not exposed.  Now with this preset Left right uses same CC with 1 or 127 same with up down, same with rotate. 

My question is,  1st of all,  how did you get the other buttons to be exposed? and 2nd, Is there any way I can change the CC values myself, I looked at all the documentation until my eyes closed and I could not find a way.

Lastly I tested out the tap tempo preset and it is brilliant but I saw no way to incorporated it into my existing preset.  So I brought the Alphatrack back out and set a touch control for the tapping and it worked flawlessly, the only problem is My Alphatrack has been the source of many crashes and unexplained slowdowns etc. I have to retire it for good this time.  Is it possible to assign a button like "quantize" on Komplete kontrol to the same tap tempo function from the preset.  It seems like it will be a lot of work if it's even possible to keep everything else in tact.

Can you let me know if any of this is possible?

Thank You

Edit:  I did a little more digging and I believe the two different ways that the controller sends the messages is why there are two different ways that CC's are being sent. so I'll live with the one that suit's my needs but I am still curious if I could get the tap tempo assigned to a pad of my choosing.

Trying to download the azcontrol software installer and it is blocked saying it has a virus.

Good day, could you please tell me if there is a configuration file under the Behringer wing?

Thanks Alexey.

I will go ahead and implement this scheme in the full system.

By the way, I have been working to eliminate the use of MIDI-OX and loopMIDI in my system.
I used these two utilities to provide a flexible way to route, merge and distribute the various MIDI streams my system requires.

You may remember that I use a number of additional GUI based buttons ('Chameleon' app) to switch a number of core functions in my mixer and tape machines (e.g. I have a RECORD mode and a REPLAY mode).  These buttons sit on top of the Sonar GUI.

So I have increased the number of AZ Controller instances from two to six. (previously I had a RECORD instance and a REPLAY instance).  The additional instances allow me to read and set the additional GUI based buttons via AZ Controller.

The new method works really well and has also allowed me to reduce the number of hardware MIDI ports to just two pairs (between the PC and my PICs).
The system response time has improved as has the reliability.

My final upgrade, in planning, is to replace the six old MOTU ultralite audio interfaces (Firewire based which Windows 11 struggles to support) with three MOTU 16A audio interfaces (Thunderbolt). 

We shall see!

Best regards
Robert

Hi Robert,

It looks good. You are right, I forgot to remind about priorities. But that is usual for any monitoring, if you want something happens in predictable sequence, you need correct relative priorities.

Alexey.

Hi Alexey

Thanks for the advice.  I got a test preset working which I have attached.
It acts to prevent fader values from being output for a short time whenever the envelope/offset button is pressed.

Could you have a look at the preset please and let me know if there are any unnecessary actions.

You will see that I set the 'Monitor Timer' and 'monitor offset' - 'Monitor Command feedback' at a higher priority that the fader monitors.  This is necessary to stop the fader feedbacks from being sent whenever the envelope/offset button is pressed.

Regards
Robert

Hi Robert,

Create a separate control, let say Inhibit, with the only Action:
Monitor Timer Once

In the feedback of that Monitor Timer, put:
Set state Inhibit OFF, set engine state



In the structure before, at the end (so near "... actions which send MIDI based on Offset On/Off"), add
Set state Inhibit ON, set engine state
Monitor Reset Inhibit::Timer in X cycles/seconds

Adjust X to whatever you need, note that "seconds" are still the number of cycled, for 75ms Refresh Frequency (I remember you have it smaller).

--------------
The explanation: original "OffsetMode" monitor is triggered on any change. So it is a good place do set Inhibit=ON. Another "Timer Once" is never triggered by itself, it can be triggered by "Reset monitor" only. So we schedule its execution after required time, to reset Inhibit into OFF.

If you want, you can place "Timer Once" into some existing control. I have proposed a separate control for clear naming only.

Alexey.

Hi Alexey

Some time ago you helped me to set up an AZ control which would report on the state of the Sonar Envelope/Offset button.  This works just fine thank you.  I use the software state 'Offset' for this purpose as you set out in one of the earlier posts on this topic.

I want to set up an associated function so that, when any change of software state 'Offset' is detected, then another Software State (let us call it 'inhibit') will set to ON for 50ms then set back to its default state of 'OFF'.

The purpose of the function is to prevent feedback outputs from all faders and pans when the Sonar Envelope/Offset button is pressed but just for 50ms.

It is any change of the state of the Sonar Envelope/Offset button I want to detect and then execute the action described above.

Is this 50ms time limited change of state possible using AZ Controller?
If 'yes' can you help me with the control structure please.

Regards
Robert

Ok no problem, my memory is the same as yours especially in my daily job! I'll look into it in my free time and try to figure it out myself!
Thanks again,
Christian