[teilo]

This is not a valid comparison.

Bitwig gives you no access to their DSP technology in its scripting language, so it is not remotely comparable to Max in that regard.

Max, on the other hand, gives you no access to Ableton's UI or API.

I have both, but prefer Bitwig. But there is nothing out there quite like Max. Not even Reaktor covers the same territory.

I am hoping that the next big thing in Bitwig will be to open up their DSP API, and give us the ability to create our own Grid modules, and, beyond that even, our own native instruments and effects. But I do not believe that extending their Javascript API is the way to do this.

[leethargo]

How does Max compare to PureData today?

I remember reading the book by Miller Puckette about DSP as applied to music, featuring examples in PureData, some 10 years ago.

Back then, I thought that PureData was the open-source version of Max, while Max offered basically some polish and GUI conveniences. But now, I read about Max much more often than PureData.

[pottering]

"Max, on the other hand, gives you no access to Ableton's UI or API"

You mean Max standalone?

Max For Live sure does "give you access to Ableton's UI or API".

https://docs.cycling74.com/max8/vignettes/live_api_overview

[teilo]

I stand corrected.

What it doesn't give you, however, is access to the control surface internals, i.e., to create new control surface "drivers" inside Ableton itself. But of course, that's currently the ONLY thing Bitwig lets you do with their API.

[jdgoesmarching]

I just got into learning music production and have been using Bitwig 8-track that came with my baby synth. I love it so far, honestly just for the aesthetic and the little tool explainer that appears at the bottom when you hover over anything.

If I stick with this for long enough I’ll spring for the full version but $400 is a steep price.

[holy_city]

technically there is a DSP scripting language in Bitwig that isn't public but you can find some examples floating around online.

That said mixing DSP + UI is hard, and if you want to make the scripting user accessible it makes sense to keep them totally divorced.

[teilo]

It's just a matter of proper separation of concerns, and the creation of appropriate levels of abstraction. It can still be done in the same language.