Hello everyone, I’ve been using the Sherlock plugin for quite some time now, which offers many possibilities for Cubase commands as well as numerous PLEs, macros, and LEs.
The problem is that it’s using the old generic remote and it’s impossible to get it working with the new MIDI remote.
So, with Gemini’s help, I created a window representing the same thing—20 pages of 192 buttons—integrated into Cubase with the new MIDI remote.
I’m facing a problem that Gemini hasn’t been able to solve yet:
I have my 20 pages, and I’ve configured access for the first 10 pages. It works perfectly, and the window changes each time. My problem stems from the fact that I can use the first 120 keys with channel 1 and numbers 0 to 119; after that, the cursor returns to key 1.
So to summarize, I have access to my 20 pages, but only to 120 of the 192 buttons on the touchscreen.
If Cubase’s remote MIDI is imposing this limit, I’ll have to completely rethink the ergonomics because I have a huge number of macros, PLEs, and LEs for a large orchestral template.
Another question I have in this case is whether it would be possible to have subpages to compensate for this lack of buttons?
What MIDI Messages does the hardware send? From the screenshot, I would guess, it sends MIDI Notes with different Pitches. With MIDI 1.0 standard, you can have only 128 Pitches.
It’s easy to read the MIDI Channel of the original Generic Remote Device from the source XML file.
Thanks for your feedback, Martin.
What would be the procedure in MIDI? Couldn’t we use RPN/NRPN values to get a larger quantity, or is there another way to do this?
The WPF window was created in Visual Studio, and the files are in XAML.
Another thing I don’t understand is why it doesn’t work if I put keys 1 to 128 on channel 1 (note 0 to 127) and 129 to 192 on channel 2 (note 0 to 64).
The cursor focuses whichever object has the very same MIDI message as the one it hosts. This means that when you hit a key (?) which you expect to have a different note, it actually doesn’t.
I checked the UI object, just in case there is indeed a bug, but I didn’t find something.
Here’s for example screenshots of assigning to note 127 on channel 1, and another note, 83 on channel 2. No issue.
In this instance, I wasn’t referring to the Sherlock coupled with the generic remote, but to the new WPF floating window created in Visual Studio and which now looks like this but is not configured at all yet
At which messages do “pages” refer to? Generally, it’s a good idea to have plenty of room to work with. So, if you have pages on channel 16, then, sure you can use channels 14 and 15. Just in case you accidentally setup a midi message identical to a previous one( a page one in this example).
Well, I’m going in circles. I finally have my 192 buttons, but I had to start from scratch, and I can’t assign my page buttons anymore; they’re going to the key channel.
