Can multiple button properties be assigned to pages, e.g., note and program change?

[Freudon]

Hello everyone, I’ve finally managed to create my Sherlock 2 in the new remote MIDI of Cubase 15, freeing myself from the limitations of the old remote generic.And so I was able to assign 20 pages of 240 buttons, 10 of which are already wired and operational.

My question is purely technical and for those familiar with MIDI remote control.

I first created a page in which I assigned my 240 buttons in the following order:
channel 14 (notes 0 to 79), channel 15 (notes 0 to 79), channel 16 (notes 0 to 79), and channel 13 for pages 1 to 20 that is, 240 + 20.

I then created my 60 bottom keys for common functions then I duplicated this page up to 20.

all my pages activate Macros, PLEs, LEs and many other Cubase functions

But for the 11th page, I need the program change to activate my expression maps, which are already all linked and configured.

This worked on my old Sherlock, but when I change the button property settings, nothing happens, or rather, I lose some of the existing assignments.

Below is my old page

Could the problem be that the pages were duplicated to keep the 60 bottom buttons and avoid creating 1200 buttons and that the button properties were on note and not program change, and that midiremote doesn’t understand?

New WPF window

[Freudon]

Should I perhaps create a new page with all the buttons assigned to program changes?

Despite all this, it remains complicated because I created these pages with the help of Gemini and I don’t want to break everything, and despite the various tests performed, it’s impossible to access the program changes.

[Dave_B]

Each mapping page is independent. Your mapping for pages need to be replicated across pages so they do not become obsolete when switching. I’m using two buttons on the SL-MK3 for that very purpose. The page+ and page- are in the same position on all pages.

[Freudon]

My page buttons work perfectly; it’s simply the configuration on page 11 where I want to change the note buttons to program change, and it’s not working and is causing bugs on the other pages.

Could this be related to the filters in the preferences?

As you can see, my 20 buttons are assigned; this is the empty space where I’d like to put program changes to trigger my expression maps.

[m.c]

MIDI Remote doesn’t handle Program Changes. If possible, alter your original PC messages to CC messages, this way they can be assigned.

[Freudon]

What does this mean exactly?

That I have to modify all my expression maps, and I have a lot of them.

for example a simple

a much fuller one

I use different parameters depending on the CC32 banks for Spitfire etc…

[Freudon]

So if I understand correctly, I modify the PC function into a note in the expression maps and I assign my keys to my notes.

[m.c]

Hi, not sure I understand… MIDI Remote doesn’t handle expression maps as far as I know. What are your plans for these buttons inside the MIDI Remote?

[Freudon]

I simply want to apply the same principle as on my old touch controller, that is, trigger articulations remotely like legato, staccato, pizzicato, etc., but not with program changes since the new Midiremote does not accept them.

[Freudon]

Okay, it finally works with the setting on Keyswitches rather than PC, but now I have overlapping zones between my keyboard and my touchscreen; it’s a real headache. I saw that Babylon Waves had notes that triggered either at the bottom (-1 and -2) or very high (6 and 7) for updating keyswitches in the new expression maps of Cubase 15.

If this is the only solution, either I have to rethink all my expression maps or I get the Babylon Waves license.

[m.c]

Still I fail to understand. From what I see, you need a dedicated page for articulations in your external utility. This doesn’t have to be included in your MIDI Remote, since articulations are handled outside of the MIDI Remote concept.
So from your external utility, you’re sending MIDI, be it either CC, notes, or even Program changes. I see you want that your PLEs are handled by it. This is all good, MIDI Remote can do this and you’ve already done that. But since it doesn’t handle articulations, what’s the point of having another page inside the MIDI Remote for this? You can for sure keep the page to your external utility, and send the messages you want for articulations.

[Freudon]

My external utility is a WPF floating window in which I already have 10 pages that work perfectly with PLEs and macros. This 11th page is only meant to be used when I’m working on a track with expression maps, where I can either manually enter articulation changes or use this remote control page live.
With this modification of switching from PC to Keyswitch notes, it now works, but I end up with overlapping notes.

I have two types of tracks: either with separate articulations (for example, page 3 of Woodwinds) where I have PLEs that call up tracks,

or with keyswitches (expression maps), and I want to be able to select my articulations remotely and which would be on this page 11.

The problem is that these expression maps were designed specifically for PCs.

And now the triggers overlap with my keyboard. Another small technical problem: the page we created is connected to 3 channels: channel 14 for notes from 0 to 79, channel 15 0 to 79 and channel 16 0 to 79. Don’t ask me why, it was Gemini who made me create the code this way, otherwise we couldn’t get it to work.

I’ve added notes for reference; I can change them up to note 66, and after that it triggers a sound, but I think that’s normal. My keyboard also triggers articulation changes in the lower part, which I don’t want.

My old page included many joints on a single page for convenience.

Otherwise, the solution might be for me to dedicate one page to woodwinds, one to brass, and one to strings, but that would be much less practical.

Gemini also suggested active subpages, which would be ideal, but I’m afraid of breaking everything we’ve put in place.

I’m not sure I’m being very clear with my broken English, and please excuse me as I’m French.

[Freudon]

The triggering of a sound on note 67 is related to the fact that the keyswitch track I tested stops at F#3, which should correspond to note 66 if I’m not mistaken.

I created a good portion of my expression maps myself, but I also downloaded some from the internet.

I noticed that on the Babylon Waves website, where you can get expression maps for all the major editors, they seem to have modified everything for Cubase 15, and that the triggers are often located at the very bottom, from C-2 to B-1, but also at the very top, from A#6 to C8.

This change is mainly due to the new expression maps in Cubase 15, which are closer to Dorico’s, but perhaps also to the problem of the midremote not recognizing program changes.