However, in a previous message I had already answered the question.
new midi remote access multiple pages on a touch screen
From what I understand Sherlock sends midi NRPN messages on channel 16(BF)
CC63 and CC62 NRPN MSB and LSB
and CC06 and CC26 NRPN value(MSB/LSB values)
Each page sends a combination of NRPN MSB (63) and LSB (62) followed by Data Entry (06 & 26) to send the value.
But this only concerns changing pages, I think I’ll check this evening.
I don’t understand, I don’t get any data on Midi Monitor.
On the other hand, I know when the preferences menu for midi filters Karol Obara the creator of the Sherlock Plugin asks to insert
Afterwards, I sometimes get midi errors at startup.
Could this be related?
https://forums.steinberg.net/t/use-midi-remote-with-a-touchscreen/918483
but if you close the session and reopen it everything returns to normal
I tested with MidiView
and here’s what it does when I trigger Woodwinds with the generic remote
And when I tested it with the new MIDI remote, here’s the result for switching from Brass to Strings by clicking twice.
I’ve just created a tiny midi controller sending (using loopMIDI) a NRPN (ch16) MSB 57, LSB 29, Val 16304, same as I see in your first screenshot, and then assigned it to Edit→Mute command. I see no issue, mute toggles every time I send this message (once). Tested both on CB13.0.55 and current CB14. So I really don’t what can be the issue here unfortunately…
Are you clicking the same button twice?
In your second screenshot, you’re sending two different NRPN parameter numbers.
Thank you both so much for taking the time to answer me.
I will continue to use the generic device for now because everything works perfectly.
And I’ll try to dig a little deeper to understand and/or wait for future developments in MIDI Remote.
Thank you again very much.
@Freudon I don’t know whether or not this is helpful but I had similar sounding issues with a controller - I sometimes had to press a button once and sometimes twice before cubase responded.
When I put Midi Monitor on it I discovered the controller was sending the values 0 and 127 on alternate presses. I was trying out scripting so had to deal with it there but might be helpful for your situation too?
More info here, good luck.
Thank you very much, but what script did you create?
I was playing around with scripting anyway - I’m assuming that you’d prefer to stick with the Mapping Assistant given the scope of your task.
I was mainly making the point that my controller was outputting two different values for presses of the same key when viewed on MIDI Monitor. I have to confess that I don’t understand the multiple values you’re seeing on MidiView.
