Accessing Key Commands sub-categories in MIDI Remote API 1.3

[Freudon]

Hi,

I’m working on a custom MIDI Remote surface (WPF/C# + JS) and I can successfully trigger commands using categories like "Transport", "Edit", "Audio" etc. in my assignments.js.

However I notice that in the Functions Browser, all these categories are nested under Key Commands. Is there a way to access the full Key Commands hierarchy programmatically, or to trigger any Key Command by name/ID directly from the MIDI Remote API 1.3?

For example, is there an equivalent of mHostAccess.mCommandContext or similar that would allow triggering arbitrary Key Commands?

Thanks for your help.

[m.c]

@Freudon

is there an equivalent of mHostAccess.mCommandContext or similar that would allow triggering arbitrary Key Commands

No.

Check the HTML example I’ve posted. It contains pretty much what you want to accomplish.

An HTML-based MIDI Remote demonstrating additions in MR API 1.3

Here’s an HTML-based MIDI Remote surface, mainly for demonstrating the addition of the Plugin Manager in MIDI Remote API 1.3 (introduced with Cubase 15.0.20) which I was very happy to see! Plugin Manager lets devs have access to all the instrument/fx plugins and insert them to instrument/fx slots, by using their UIDs as provided by the API. The mechanism is straight forward, however, there’s always a place for snippets, so I decided to provide one. At the same time, in this surface I’ve built,…

In the upper section of the HTML view, you will see a button named “Commander”. This does what you want, so you can inspect the code at the MIDI Remote side (js) and see how it’s implemented.

[Freudon]

Thanks a lot, m.c., for taking the time to reply—that’s great.

[Freudon]

Hello m.c., we looked at the JS for your “Commander” and found 2,042 orders, whereas we retrieved 1,454 using the official API 1.3.
Could you tell me what these additional orders represent?

For now, we only have a single menu level, but everything—all 1,454 commands—is finally there.

[Freudon]

Hi m.c., regarding my question about the discrepancy between our command lists: I took a closer look at your Commands.js and figured it out—the ~600 extra entries are the UIDs for your plugins (Process Plug-ins) and your personal PLE presets, which are specific to your machine. So, my native command list is actually complete on my end, and my own presets are added via my scanner. Question resolved—thanks for your help anyway!