Ableton Forum

M4L defo needs to be better "optimized"so it feels more intergrated into Live

I'm fine with the M4L LFO since I have Suite, but it sucks for everyone who has the Standard version of Live.

Please unlink LFO and other devices from Max4Live. It is ridiculous to load whole M4L for something so trivial, and M4L devices are known to be CPU hungry.

I think even a habitual Max user might appreciate a few official devices being given native versions to increase efficiency. Especially considering that many of the native devices were previously prototyped in Max (EG:the grain delay). So there is precedent.

hypothetically:
if The LFO and Convolution Reverb Pro were discovered to be used in 70% of Suite-user's sets, and 25% of all users say "I wouldnt trust them on stage" then it might be good and more efficient to lower their resource usage via any means necessary.
Again, thats hypothetical, but Ableton already have usage data streamed from the app and can do questionnaires for the non-usage.

Angstrom wrote:I think even a habitual Max user might appreciate a few official devices being given native versions to increase efficiency. Especially considering that many of the native devices were previously prototyped in Max (EG:the grain delay). So there is precedent.

hypothetically:
if The LFO and Convolution Reverb Pro were discovered to be used in 70% of Suite-user's sets, and 25% of all users say "I wouldnt trust them on stage" then it might be good and more efficient to lower their resource usage via any means necessary.
Again, thats hypothetical, but Ableton already have usage data streamed from the app and can do questionnaires for the non-usage.

I'm not sure you need surveys and user data to figure out things like a native LFO device are a very wanted/needed feature in a music production program
If you want any signal at all, look at this thread

+1 and not just for LFO but for other types of modulators as well like Envelopes, Sequencers, Followers, KeyFollow and maybe other bizarre stuff + possibility to alter every modulator output further by the transfer curve (per each mapped param).

Finally it's time to crack open this topic again!
So M4L is completely integrated into Live as of Live 10, which might solve our problems.
I've opted out of the beta program a long time ago, anyone here able to try out the new LFO device?
I'm super curious if the loading times are the same as the native-native devices now or if there is still a notable difference.

+1 for native Live LFO/s without work-arounds or M4L.
c.

alec.tron wrote:+1 for native Live LFO/s without work-arounds or M4L.
c.

To my understanding it's still running on the M4L engine but they implemented the program into Live.
I'm still curious if the new devices load up as fast as native Live devices. I haven't seen that anywhere yet.