I just wish... take a look at Max.. I'm sure there would be much more productivity from the users with a JS modular kinda thing. Not everyone have time to be a programmer, but many artists do like to use modular programs to make cool machines.
This is the one thing I miss from my Tracktion days, before Mackie bought it and completely destroyed the entire program. Every track's FX rack was a drag-and-drop, drag your own connections from one plugin to the next, whatever order you want, etc layout like the Buzz screenshot in that article. It was glorious.
we need to continue this development I want to make a point of saying that I absolutely HATE Max/MSP and PureData paradigm because of how incredibly frustrating it has been for me to accomplish what I set out to accomplish. Because Jesusonic is a written programming language first, and then jsfxgen turns it into a visual language, you get the best of both worlds. So please don't follow the example of Max/MSP or PureData, continue the amazing paradigm / model of jsfxgen. Edit: Putting frustration into words - the reason it can be so frustrating is because there is a huge number of stupid objects and workflows and workarounds for PureData/Max that only exist to solve the lack of a written language. You are constantly having to deal with the fact that you can't type out simple code. Yes I know there are "code" objects for both languages, but they are nowhere near as powerful and easy to use as jesusonic.
I agree with Argitoth. But, there is still one big limitation in JSFX compared to Max4Live. There is no access to Reaper API in JSFX. You are limited to creating pretty much the same kind of plugins like VST/VSTi plugins. There is no access to tracks, items, item contents. The integration to Reaper environment is very limited. Reaper has three separate programming environments: 1. ReaScript (Python / EEL) for non-realtime (or some "global background") actions. 2. JSFX (EEL) for realtime processing in plugin chains. 3. Reaper Extensions (C++) for non-realtime tools. Only ReaScript and C++ Extensions have access to Reaper API. But those are globally scoped. You can't instantiate ReaScripts or C++ Extensions per-project or per-track or per-item. And you can't route signals (audio or MIDI) to ReaScripts or C++ Extensions for realtime processing. (Well, you kind of can "route" items to background scripts, but that is a different thing). Max4Live components can be instatiated into plugin chains for realtime processing AND you have access to Live API (tracks, items, selections, create and edit MIDI items and notes, etc.). It would be very useful to have Reaper API available also in JSFX. jnif
--------------------- 2002 M Coupe Estorilblau 368S/74