Open F0rth opened 8 years ago
Can you point me to some available documentation that describes such scripting and what people do with it? The last commercial product I used was Cakewalk, oh so many years ago; I wrote a lot of CAL "programs" for it, but they were for manipulating and creating MIDI events, and it was a Lisp-like language. I'm still aiming for a non-GUI mode for Sequencer64, and scripting would fit right in (and enhance its testability). Thanks!
-------- F0rth 02:08 Tue 22 Mar --------
It would be nice to have a bridge to a script language (lua ? javascript ?) a-la live or bitwig, so users could write plugins to support their hardware interfaces (launchpad, and so on).
You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/ahlstromcj/sequencer64/issues/16
There's small choice in rotten apples. -- William Shakespeare, "The Taming of the Shrew"
Just thought I'd pop in here to say I'd rather all sequencer64's features be exposed via OSC such that the system could be scripted from any language.
I think that's a cool idea. I will have to do some learning and wrap my header around OSC. Also, I want to stabilize Sequencer64 in a version 1.0 that is basically a feature-complete fork of seq24, and then branch out from there to a GUI-less version of Sequencer64. Thanks for your interest and feedback!
For the records, an example of a bitwig script to add launchpad mini support https://github.com/bitwig/novation-launchpad/ but OSC look far more appealing.
@ahlstromcj FYI ZynAddSubFX switched to a decoupled interface which uses OSC to control everything in 2.5.x. Maybe you can get some useful info from their code or contact them for any tips.
It would be nice to have a bridge to a script language (lua ? javascript ?) a-la live or bitwig, so users could write plugins to support their hardware interfaces (launchpad, and so on).