What I see on the MIDI monitor is a constant stream of messages; about 1300 messages in about 10 seconds
Yes. Most probably in Play mode. The cursor is updated using sysexes.
I must ask: Why don’t you inspect the code of the script instead of tracking MIDI? It will be much easier.
The MIDI messages i was seeing were sent with Cubase in Stop; besides sys exes there were a lot of control change messages on channel 1 and 2, much more frequent than sys ex
I must ask: Why don’t you inspect the code of the script instead of tracking MIDI? It will be much easier.
Thanks for the suggestion, I’ll take a look at the code, but I’m not sure it will be easier for me; while I know very well the MIDI protocol my knowledge of programming is next to nothing 
You must understand that the demo remote doesn’t follow any known protocol at all, no MCU, no other. This makes reading the code necessary for many aspects of it.
Upon initialization of the script, there are 100s of messages sent from Cubase, in order to populate all the collections lists, the controls involved, pretty much anything you see on the display.
Thanks again, I’ll look at the code and try to understand the script
I was looking at the messages way later than the script started, not sure how much, but probably an hour later
Good job! 
Probably next week I’ll bring up an update for the Novation SL MK3 too. It has these 4 displays, so it will be a bit easier to handle browsing. Still, wishing for something similar for vstPresets 
Cool! this is going to be powerful
My navigation is done with four pads: two for collections, two more to select the plugin, and one to load it. It’s very efficient. That said, it requires creating several collections to unlock its full potential. And If you’re interested in my code, I can send it to you.
Yes, I also hope we’ll have the same thing for VST presets; that would be really great.
In any case, it’s a huge step forward for the user experience!
Want a suggestion on this? Add two more for the plugin categories. This way you add browsing for “reverbs”, “delays”, etc. Makes browsing even easier, without perhaps the need of separating plugins into multiple collections just for different categories. If you download the code of this thread, have a look at the fetchAllCollections and removeInstrFXMainCat subs. Just to have an idea on how to approach this addition, if of course it matters to you
That interests me because I haven’t been able to access the categories. I admit that would be a better way to navigate. If you have the code for that part, I’d be interested
Sure.
We’ll try to apply this with Claude in XAML.
If I understand correctly, you can remotely place the plugins in the inserts.
Correct. And also change the plugin of the instrument slot.