That’s interesting. Could it be where the keycommands connect to? (Primary Parameter Increase/Decrease, Primary Parameter Fine Increase/Decrease - these are for volume, and Secondary Parameter Increase/Decrease, Secondary Parameter Fine Increase/Decrease - these are for pan)
I got curious as well! In fact I thought I could gain access to some hostValues this way. In the very end, I saw that there were other ways more compliant with the API’s context, so I forgot all about it
It’s more powerful in regards to feedback to the device (i.e. to put displays on screens, light pads etc.), and you can do things like map clockwise/counter clockwise turns to different actions - which you can’t do in the surface editor.
It basically allows you to write additional code to manage the actions between input and the output of the controlled values.
On the whole it’s much more powerful yes, but it depends on your requirements. The surface editor is very powerful and quick too, and you can use both methods to create a hybrid remote.
What I mean by that is that you use the API to define a control surface and more intelligent mapping pages, but you can then add to that surface with new pages via the surface editor interface within Cubase.
I think the old Generic Remote works well for devices where you want a long list of triggers without screen representations. i.e. for external touch device controls running apps which only need a CC trigger related to a command. And things like Streamdecks etc.