I have never found Live devices to be more CPU friendly, less likely to cause issues and the sample based ones automatically can save their samples in a Project, but the CPU consumption is on par with NI, Ohm Force and U-He products. Actually I think the Nomad Factory stuff I have uses less CPU? I have always been perplexed by this, but embedded plug ins aren't really doing anything that differently than AU/VST when it comes to the actual code, (an FM synth is an FM synth etc.) it's the interfacing that's different. Not talking efficiency as much as little things like being able to turn off a plug in inside Session View ( I don't use Arrangement View live ), without having to use a Rack which then requires a second MIDI track for program change messages, which all adds up to more CPU used to try to conserve CPU?? Don't think this is any different for embedded plug ins, but I could be wrong, only use Drum racks AFA Lives included plug ins, and not live.
Ableton's own devices are made in a way to not use up CPU when they're idle. Some of them, like beat repeat, do use up CPU if they're performing calculations while idle.
The 3rd party ones do indeed behave much like their VST counterparts. All integrated 3rd party devices are essentially VST's in a new coat.
One reason not to get M4L for me is I need to dive into building in Reactor first.
Cycling is playing into that. They just released Vizzie, which is a set of Reaktor-like modules for Jitter (Video Performance). Similar things are in the works for MFL and its safe to assume that MSP will get these modules too. The modules are simplified to the point where you only have to connect Video/Audio signals. Much like Quartz Composer for example.
I'm not suggesting it'll change your mind. But it will give MFL and potential builders enough fodder to approach something like the Reaktor Library type of devices.
What I meant is an editor that shows the position of a MIDI Clip in bars/beats/ticks and length in beats/ticks, that allows you to get medieval on your MIDI.
That what your talking about?
Yes, that is exactly what it is. You get an entire clip in list form with all the relevant info. Time, length, pitch and velocity.
In LiveControl, the list editor takes the form of a step sequencer.
In the near future, it'll probably result in a touchscreen clip editor that is richer than the one in Live.
Couple things here. M4L from Cycling 74's perspective is brutally cheap. I don't know if this is going to help them be convinced to allow Ableton to go with a free Runtime? I'm OK with a $75-100 Runtime, this makes sense.
Max/MSP is expensive and kind of covers the cost of a Runtime that way I think, M4L is cheaper, and the Runtime version will be immensely more useful to people. Probably not a popular opinion, and personally I'm brutally broke these days, but I get that businesses need to thrive.
Yeah. And considering all the pluggo content that comes with it, even 100$ would be rather cheap.
Still, as witnessed earlier, the gap between not having it and getting it for 300$ is still large enough to downplay the importance of MFL.
That said I have high hopes, a little failure gets the blood going and that makes me think 9 is destined to be a game changer. <-- Hopefully in Ableton's favor, I have a suspicion that we could easily see a DAW from NI pop up that's performance oriented in the next couple years. Maschine, Reactor, and Kore are already geared that way. If not from NI, then at some point developers are going to notice that people very regularly own a standard old fashioned DAW like DP, Cubase etc. and Live. = nice market share! = room for competition.
That's the whole point of this business for them isn't it? We approve or disapprove with our wallets. Part of my point earlier about it being 2 years since something significant happened implies that they had a lot of time to think and rethink what they're doing.
That long list with feature requests they used to mention, its not fiction. It actually exists.
We have no clue what they'll prioritize, but we can definitely guess what is on top.
