[SOLVED] REC 1 arm doesn't work with MCU (X-TOUCH Behringer)

[BobXX]

This apply with both Sonar and CbB.
Controller: Behringer X-TOUCH  last firmware (1.22)
DAW: Cakewalk (last version), Sonar (last version) and probably previous ones

In MCU mode (Mackie Control) all seems to work with the exception of the upper left button REC of X-TOUCH (REC arm, see photo),
even if the track is a proper one for recording, even if the arm of that track from CW/Sonar itself works and the button becomes lit for confirmation.

If I simply enter the Sonar "Preferences" menu and press that REC button... it works ! 😳

I understood that buttons sends CC 0x00 whilst the REC buttons of the other stripes send 0x01 0x02 0x03... etc (and they works).

I tried another configuration with "General Surface" or with the "AZslow" driver, but all the same that button seems to be ignored/filtered by CW before them,
the AZ driver monitor shows all the controllers commands with the exception of that one.
Maybe CW considers 0x00 a null command ?

Does anybody have clues/solutions ?
 

Edited August 14 by BobXX

[msmcleod]

Go into Keyboard Shortcuts in Preferences, and check what is defined for "MIDI Shift Options" - I suspect you've got yours set to Controller 0.

There are two ways of solving this:

1.  If you never use MIDI to trigger keyboard shortcuts, just uncheck "Enabled" next to the MIDI radio button; OR
2.  Set the controller to something different, say 120.

[BobXX]

43 minutes ago, msmcleod said:

Go into Keyboard Shortcuts in Preferences, and check what is defined for "MIDI Shift Options" - I suspect you've got yours set to Controller 0.

There are two ways of solving this:

1.  If you never use MIDI to trigger keyboard shortcuts, just uncheck "Enabled" next to the MIDI radio button; OR
2.  Set the controller to something different, say 120.

You're absolutely right!
The note was set to “C0,” which is probably equivalent to “0x00,” and MIDI was “Enabled.”
If I change it to Db0, the non-functioning button becomes REC 2 instead. 🤗

I simply deselected the option and the mysterious behavior was resolved. 🖤

**         Kudos for your hint and promptness   **

Edited August 14 by BobXX