Not quite, from a quick look. That suggestion seems more like a way to add hook scripts to certain patterns to be executed when the time is right. My suggestion also includes controlling Renoise as a whole, and being able to run renoise-scripts noninteractively, initiated from another program.
So that we for instance also can have “Live for Renoise” or “Max for Renoise”…?
Just for doing some batch commands from the outside is not really worth implementing a complete scripting engine for.
If you would say to add an internal scripting engine and use OSC libraries inside them, then you are talking more serious because then you can also use outside interaction…
I guess I liked the idea of Renoise as an interpreter, so it could be used just like bash, perl etc on their scripts.
I don’t know what’s going on in the world of music software, except a little about trackers and Renoise in particular, but I guess Live and Max are some sort of interprocess communication protocols, where a single instance of Renoise is running and interacting on the Live/Max-com channel?