With Cubase 15.0.20, we are shipping the latest MIDI Remote API version 1.3, and I’m happy to say that the API documentation is now up to date as well.
API 1.3 extends DirectAccess, first introduced in API 1.2, and adds a number of further improvements, including platform filters in device detection, extended DirectAccess introspection, plugin manager support, object type name lookup, surface display string access, and command binding capability checks.
As an addition to the documentation, there is now also a browser-based Playground for trying out MIDI Remote scripts directly in the docs. Please note that the Playground is brand new and currently in alpha state, so expect rough edges and use it at your own risk.
Could there be any hope in the near future for the ability to add a “Non-Graphical Device”, that is essentially just a mass routing portal list of MIDI → Mapping Assistant… Akin to the old Generic Remote?
This documentation is very welcome, with the addition of logging host objects/params.
The mPluginManager is a great great addition!
I want to comment on the new getParameterProcessValueType method. This was a dream for me, in order to properly map knobs/buttons of my controllers, without too much effort.
Finally, the get/setDisplayValue is dope!
Playground? I will give this a shot, sounds very interesting
Great progress, especially mPluginManager. Three remaining blockers for AI integration: track creation, audio region rendering, and external process communication (HTTP/IPC beyond MIDI). Looking forward to v1.4.
It extremely turns me off reading about API updates, but absolutely nothing (since three versions) for the midi remote editor. We normal users still have no support for displays, LED rings etc. For how the whole thing was advertised once, really nothing useful had happen since then. Even more frustrating is the fact, that API and midi remote editor is not compatible, not to mention that this editor is really a sad joke.
Really how hard can it be to add display support for the editor? At least add one display that follows the MCU standard, add a option for a sysex header and most people would have a display. Do the same for LED rings and you would have covered the most common midi controllers.
