Hello
Could someone please tell me why I have to press a button twice to trigger the function?
I use the Sherlock 14-bit MIDI plugin, which works very well with the generic device with Cubase 14 pro.
Knowing that this function will eventually disappear, I am trying to do some tests to configure a first page in the new midi remote but in Cubase 13 Pro so as not to modify my setup.
Seeing your screenshots, I see no reason for the bindings to fail. After all they’re just command bindings (even PLEs), I don’t recall the MR having issues with command execution.
Do you have the generic remote active at the same time, using the same MIDI Ports? Maybe it’s a message consuming issue.
Without knowing much about the mapping assistant, the first thing that comes to mind is that your button is of a latching type where you would rather have a momentary type.
Issues with NRPN were fixed by that time if I recall correctly.
Correct. When executing commands, the CC has to send something above zero, so if your device is set into toggle (I mean at the device side), indeed this could cause the issue.
Thanks to both of you, but I should point out that Sherlock is a plugin I use on a 24" touchscreen.
In this case, is it possible to switch between toggle and momentary mode?
Do I need to change anything in the button properties?
Value mode: invert minimum and maximum values.
The things you want to do don’t seem to need scripting.
When you press a button on your controller (from what you say it’s just a button element in the UI of Sherlock), what are the values of the midi message sent? Could you monitor them from inside Cubase and its midi monitor?
