Ermi, i’m not familiar with your production style, but this doesn’t just stop at devices. Theoretically, with a little ambition, such a scripting language could extend to such things as what instrument is playing.
For instance, lets say you have a complex drum programming sequence, but you want every time a snare hits for an EQ to drop the highend by a certain percentage. Or perhaps you could make every kick push the low-end and every snare do a filtersweep down.
The idea is simply to be able to interconnect all the different aspects of the software in a freeform and potentially dangerous way I like the idea that we could create a bizarre contraption that adjusts the master out or pan of tracks or whatever we want based on the current position in an instrument envelope. Perhaps the script is so crazy it crashes the software, so what, it was my fault for making a crap script. Back to the drawing board.
It lets us do weird things the developers haven’t the time to make easy for us.
And anything is faster than copying and adjusting envelopes for every single hit of an instrument on every single track
perhaps even using the actual player commands as “variables” or definition of, would be a method to use to save us remembering a whole new load of words.
an SQL style language would work well for pattern editing… i mean the pattern is just a big table with typed fields. would be a yummy way of doing advanced edit type stuff without a mouse… sigh
Z80? what the f****!?! ok… my new vote’s for qBASIC…
ECMA standard would be my suggestion. JavaScript/Java/Actionscript2/C++/C#. These languages are immediatly readable by total newbies if written easily. MyObject.myProperty = myValue; Perhaps ditch stuff like semicolons and have python-style blocks, such as tabs instead of {} and linebreaks instead of semicolon.