I am trying to approach creating a new Midi Remote script for an older control surface (Tascam US-428). It was fully supported by Cubase until version 11 & it just disappeared. Which is tragic because it was made to work with Cubase & was perfect.
I’ve got a JSON-based Remote script working quite well using the built in drag and drop MIDI Remote tool in Cubase.
However, it can’t send any feedback to the controller to tell it to turn on LED lights, switch bank modes etc.
My question is- am I looking at starting over completely, or is there a way to extend my JSON with extra JS script code to send messages back to the controller based on the state of the DAW? And/or utilize the information in this JSON in any way?
I can’t seem to find an answer anywhere. I’ve got Visual Studio Code running with autocomplete working, I just need some direction.
And this is exactly why I keep on using the Generic Remote definitions. The MIDI Remote Mapping Assistant is of no help when dealing with endless rotary faders (NRPN incr/decr messages management).
And life is short : at this point of mine, I no longer have the time to learn Javascript just for that…
I actually have a pretty solid script cooked up now (>700 lines of code so far).
Most of it’s working great, however I’m fighting a really strange bug… I should probably create a new post to discuss it…
The gist of it is that my EQ knobs don’t bind to the correct band until I turn the jog wheel (which I’ve assigned to FX sends). When I nudge the wheel, the EQ knobs suddenly switch to the correct band. Without debugging tools, I’m stuck