It would be great if we could have midi script editor for those of us who have programming background and want to manipulate MIDI tracks more efficiently and want to have more flexibility. I assume, if this is developed, VST developers would produce and ship their own scripts with their VST products! This would open a whole new world to midi functionalities in Cubase. Think of this as a script/text version or the current LE.
Kontakt has since the early versions ( 2009 or earlier) this feature to its users.
Scripts can be seen as small plugins. They are quite similar to the MIDI effect plugins you can use in sequencers but differs by being integrated into the sampler and this provides some benefits. Unlike MIDI effects, scripts have access to some internal Cubase features which in addition lets them ( my ideas maybe vague, sorry!):
my shorthand notation: NEP ( note, event, or part). The event can be volume, etc.
- change volume/panning/tuning of a specific NEP
- fade in/out a specific NEP
- specify which midi channel or patches should be used for playing back a specific NEP
- All the parameters in the current GUI logic editor
- and more of course!
- Users can save the script and apply it to many tracks. Just imagine you have a script and now you can apply it to desired MIDI tracks by pressing a button!
- Save MIDI automation as a script and load it and apply it to the desired track. This will speed up and resolve the issue of applying the same automation in Cubase.
To do this a pythonic language (let’s call it: Steinberg programming language) for MIDI should be developed by Steinberg that will be like readable text. A script basically consists of a number of text lines with instructions to the Steinberg Script Processor (SSP). The SSP interprets your script and executes your instructions when it receives notes or MIDI CC, or NEP.
Just a long term idea.