1
MilkyTracker Feature Requests / Re: Lua/Python script plugin support
« on: November 19, 2022, 11:04:26 »
Well, perhaps nitrofurano's silence on this topic, and your off-and-on focus (in openMPT) might indicate that it's a feature which certainly adds possibilities, but does not solve urgent actual problems end-users are having.
I think we're pretty much on the same page: a scripting-engine requires a lot of sparetime effort/maintenance for a subniche of endusers.
I had some off-and-on lua experiments with milkytracker too.
Implementing a midi-importer is one thing, implementing a script-engine which allows endusers to write importer-code is something exponentially bigger.
Having that said, I do like the idea.
If you ever feel like writing down a universal module scripting-api standard let me know.
I can imagine running the same pattern-scripts (`writeNote(..) getCurrentRow(..)` e.g.) or sample-scripts (setSampleValue(instr,sample,v) e.g.) in different trackers (by just implementing the same functions).
I think we're pretty much on the same page: a scripting-engine requires a lot of sparetime effort/maintenance for a subniche of endusers.
I had some off-and-on lua experiments with milkytracker too.
Implementing a midi-importer is one thing, implementing a script-engine which allows endusers to write importer-code is something exponentially bigger.
Having that said, I do like the idea.
If you ever feel like writing down a universal module scripting-api standard let me know.
I can imagine running the same pattern-scripts (`writeNote(..) getCurrentRow(..)` e.g.) or sample-scripts (setSampleValue(instr,sample,v) e.g.) in different trackers (by just implementing the same functions).