Hotness i assume. I have to admit, though i’ve been super up on scripting for renoise before, i wasn’t ever interested in manipulating pattern data through scripting. You get ridiculous things like algorithmic music, avant garde junk that is truly just random notes, glitchy breaks that are truly just glitches. The list of terrible results goes on and on.
However, if i understand you right Taktik, is there a good reason why a script executing on each individual effect chain is more complicated? It’s a question of querying a given node of the song xml and getting its children after all, and allowing some kind of IO on those children.
My first post on this topicwhine
Leaving xml parsing to the script seems kind of out of whack with reality if this was ever intended to execute continuously. But i assume it wasn’t? I think about selections entire songs in length and something in me curls up and dies.
For an API to facilitate this kind of scripting, i’d expect the script to be given access to an array of relevant nodes parsed down to object structure, not have to perform its own xml parsing. Sequence and properties is all it’d honestly need.