is growing the controller api a popular demand around here?

[Quack Quack]

I was a bit surprised to see minimal api commands for the arranger. Being able to create,move and edit clips around the arranger especially if the clips had IDs would make it possible to create entire songs from the API alone. Wondering if the devs were aware or requests for growing the API.

[Milkman]

So you want to use Bitwig, the DAW, but you dont want to use all its carefully, passionately developed features and instead you want to use a robust API to do production work from some other application? Huh. Maybe just develop your code until its more like a host and an arranger, and just generate music that way without BWS in the middle?

[monolithx]

I was a bit surprised to see minimal api commands for the arranger. Being able to create,move and edit clips around the arranger especially if the clips had IDs would make it possible to create entire songs from the API alone. Wondering if the devs were aware or requests for growing the API.

Regarding AI vibe coding usage and infinite whishlists on all audio gear forums, they should... or die.

[oluf]

Yeah, this would be very welcome. I had been working on a multi-modal (voice, cli, eventually gesture) control system that was initially targeting live, but would much rather work with Bitwig as I am on Linux.

[] Peter:H []

I think it's a legit request. Bitwig consists of an UI which is a window into Bitwig the playback engine. Following the MVC pattern (or derivatives) it would be cool to be able to create different views/controls ontop of the engine.
But I think it will not happen - because with a legit API Bitwig the company would undermine futur earning opportunities if all over sudden people would be able to build usefull stuff and offer it to others.
I remember that there was a user who hacked a native bitwig device back in the Version 2 days by changing the DSP Code which is based on Bitwigs Nitro Scripting language. Nitro is still there but afaik the possibility to access and tweak Nitro Source Code of a device has long ago been blocked ... Imagine people could write sth like the spectral plugins on their own... Therefore I think we are not going to see a fundamental extension of API capabilities into teritory the OP requested.

[apoclypse]

I think a better controller api for more access to the DAW from a controller would be nice. I don't really care for or about extension for generative purposes. I just want to finally be able to see the piano roll, waveforms etc in a controller like Push. I don't know if its possible now.

[chamania]

i actually think controller API and documentation are the most important thing of a DAW, since they all lack extremely in that area, we are stuck forever it feels like.
Bitwig is already pretty much leading, we are still stuck in the past tho.

[knob_monster]

peter is spot on about them protecting device sales. but look at how max for live carried ableton. restricting the api just hurts adoption long term bruh