BlackCat Scripting Plugin
This might be interesting to some:
PS: I edited your post a bit, to make the original link show up better, and also to add a link to the official product page at bluecataudio.com.
I've been bumping into Lua more often lately, because I've been doing a little scripting in Steinberg's HALion (sampling and synth platform), Native Instruments Creator Tools (adjunct software for Kontakt developers), and ProtoPlug (which you had mentioned in another post in this forum).
I imagine Blue Cat Audio picked AngelScript a long time before the more recent momentum around Lua.
Cubase 12 Pro, Win 10 Pro (x64), several different midi controllers
There are some other LUA scripter possibilities out there, for example, the opensource ProtoPlug is free and provides midi and audio scripting in LUA.. (HINT HINT, the license there permits someone like Unify to re-use the code that is there, I know at least one other product that is using this scripter engine to get started, but in my opinion ProtoPlug could use a more complete API for handling midi.
Information here: https://www.osar.fr/protoplug/api/
More info here: https://www.osar.fr/protoplug/
Source here: https://github.com/pac-dev/protoplug
In addition KushView Element has been adding its own LUA scripting, its still in development but some of it works with hardly any documentation.
In addition Soundigy MidiLab has a plugin which basically is basically using the above-mentioned ProtoPlug code, plus some additions added to it...to provide Lua midi and audio scripting in their standalone or their plugin version.
I would love to see Unify embed LUA scripting directly into it as a built in midi plugin. But at the very least, ProtoPlug can be used right now today...and probably Kushview's will be quite nice when its done but putting Kushview inside of Unify is overkill and complicated.
I have been thinking about scripting for a long time. The question of which script language to use is a tricky one, because whatever is chosen, there will be some who would prefer a different one.
Also, if Unify did have a scripting capability, what kinds of scripts would you want to write? Can you give some specific examples?
The only reason to consider LUA is because LUA ProtoPlug is already out there, is open source and the license permits what work that author did to be reused in other products. Soundigy MidiLab is doing that for example, he grabbed the code for Lua ProtoPlug and is building up on that. For whatever the reason, KushView Element is also using LUA for the scripter they are working on, I don't know if he is using ProtoPlug as starting place or not, but I think he wants to take it in more directions enabling cool GUI access to other KushView Element objects, etc. its still under development honestly, its there, but no docs, nobody is using it yet.
I have made a lot of use in LogicPro's Scripter specifically for articulation management, handling keyswitching duties and similar things where its just necessary to have that much exact control, or overcome limitations of LogicPro's articulation set features. I have some of them on gitlab and can point you to them if you want to see them.
In Unify I think it would be good to be able to also control Unify itself...which Apple's also allows in a limited way. For example, in Apple's Scripter, you can create in script an automation parameter that will be exposed to its corresponding LogicPro track as an automatable parameter which can be used together with Scripter. Unfortunately Scripter provides hardly any other ways to control LogicPro itself. But Anyway, inside Unify, I could see it being useful to be able in Script to control how layers are turned on and off and various things like this that would make it possible to do advanced instrument trickery that some people might think of. So in Unify it would be useful not only for filtering/generating midi and audio, but also to interact with some of Unify's controls.
That's enough for now. Feel free to reach out privately if you want to have an ongoing discussion.