4 ms·
The lack of tools isn't the problem. The problem is that Max reimplements basic CS concepts badly, eccentrically, and unintuitively, for no real benefit, while
by TheOtherHobbes 7y ago
The lack of tools isn't the problem. The problem is that Max reimplements basic CS concepts badly, eccentrically, and unintuitively, for no real benefit, while adding a huge extra cognitive load.
Max for Live highlights why this is bad. If you can find the unofficial docs, it's much easier to access the LOM using Python - or pretty much any standard language - than to do all the string/list/symbol splitting, prepending, filtering, combining, and so on you're forced to do to make anything non-trivial happen in Max itself.
I think there's an open niche between Max, which is just plain weird and difficult in too many ways, and the low-level world of Juce and C++.
I'd love to see a scriptable industry standard plug-in architecture with a super-easy "just works" set-up for graphics, DSP, MIDI and timing, based on a modern high-level language, but also fast.
WebAudio is somewhere in that niche, but - aside from being browser dependent - it's still too close to the metal for most users. Some of the plug-in construction kits are too high level. Faust is good but still very specialised.
I suspect there's a sweet spot between the extremes, and it's not currently been catered to.
- qmmmur 7y agoAgain, you're missing the point. Max and pd were developed for composers and musicians to execute live performances of institutionalised academic music (as well as its long history of connections to IRCAM in Paris). It does that perfectly.