Which DAWs Allow & Don't Allow You To Develop For It ?

[THE INTRANCER]

It's probably a boring question / topic but hell, it might be of interest to someone.

By the thread title, I mean scripting for the program vie seamlessly integrated extensions, scripts, plugins, enhancement addons bla bla bla... you get the idea...

The first person to mention Reaper gets shot.

[highkoo]

ImageLine is kind of suprisingly tolerant of people posting random hacked together widgets for FL over at their Looptalk forum.
I think skinning is the one thing they dont 'like' people doing.

[moss]

OK, let's start with Reaper then

1) Reaper: Allows to modify everything (and I guess that is your issue with the software, that you have) - APIs can be coded with C++, Lua, Python, Jesusonic; documentation is kind of wild and lacks some updates but there is good support from the community

2) Bitwig: Open API for developing controllers extensions but can also be used for different tasks. Code in JavaScript and Java. Best documentation I know so far.

3) Ableton: Similar as Bitwig but in Python and no public documentation at all. And there is M4L for plugins.

4) FL Studio: Has an API for MIDI controllers. If I remember correctly it is JavaScript.

5) Cubase: C++ API for MIDI controllers but not public. There is a new controller API in the works which will be open.

That's the ones I am aware of.

[chk071]

The first person to mention Reaper gets shot.

It's probably the DAW which allows the most in that regard though.

Why even create such a thread if you're not interested which DAW allows the most?

[antic604]

Studio One appears to have some scripting mechanism (other than Macros), which allows for creation of extensions like this:

https://s1scripts.wixsite.com/colortoolbar

[antic604]

The first person to mention Reaper gets shot.

It's probably the DAW which allows the most in that regard though.

Why even create such a thread if you're not interested which DAW allows the most?

I think everyone knows Reaper is the most flexible in this regard, so no point in discussing it. The OP's asking for DAWs other than Reaper, basically.

[CinningBao]

You can create your own scripts to handle MIDI for the MIDI FX Scripter plugin in Logic.

You can write your own bidules (modules) for Plogue Bidule with the Bidule SDK (available on request).

[kev2525]

5) Cubase: C++ API for MIDI controllers but not public. There is a new controller API in the works which will be open.

That's the ones I am aware of.

Hi Moss, have you heard any further news on the release of the cubase API? It seems they announced it a while ago, but after that not a single update. It was originally announced as part of Cubase 11 AFAIK.

[ReleaseCandidate]

The only open source DAW (worth trying out) is Ardour.
https://github.com/Ardour/ardour

Waveform has Javascript Macros
viewtopic.php?f=22&t=500416
and Cakewalk a deprecated, badly documented scripting language.
https://www.hexachord.net/cakewalk-cal-scripts/

[Blaster]

Renoise has Lua scripting: https://github.com/renoise/xrnx

[moss]

5) Cubase: C++ API for MIDI controllers but not public. There is a new controller API in the works which will be open.

That's the ones I am aware of.

Hi Moss, have you heard any further news on the release of the cubase API? It seems they announced it a while ago, but after that not a single update. It was originally announced as part of Cubase 11 AFAIK.

I only know the official statement: https://forums.steinberg.net/t/midi-rem ... ent/158426
Which basically says: it is ready when it is ready.
One might guess that 11.5 is round the corner and it might be part of it.