Native LFO

[antic604]

Hey people, check out tip 14 in this article:

http://little-scale.blogspot.com.br/201 ... -2017.html

I'll quote for posterity, but everyone should check the whole article/videos:

"A custom LFO can be made by setting up a new MIDI track with a clip containing control data. The output of this MIDI track is then routed to a virtual bus. While this clip is playing, the data can be mapped to any parameter on another track - in this case the level of a modulator in Operator"

Great, but 1) you shouldn't have to resort to "tricks" to achieve basic functionality, 2) you cannot really automate the "LFO" parameters that way: frequency, depth, phase, etc.

[Able_Belamy]

Yes, so much this - it's ridiculous that something as basic as LFO device isn't a native Live9 effect! I have Suite with Max4Live, but somehow I'm always anxious using it - it seems fiddly, unstable and takes ages to load. Maybe it's because I like my things nice & tidy and M4L devices all come with their own colors, GUI ideas and fonts, sometimes pictures in the back, etc. which just pisses me off.

+1 for native LFO device

The biggest downside of m4l for me is that it takes so long to load, even with a ssd. It kind of feels like it slows everthing down.
Also projects with m4l plugs take ages to load. It just messes up your workflow and feel.

[antic604]

Yes, so much this - it's ridiculous that something as basic as LFO device isn't a native Live9 effect! I have Suite with Max4Live, but somehow I'm always anxious using it - it seems fiddly, unstable and takes ages to load. Maybe it's because I like my things nice & tidy and M4L devices all come with their own colors, GUI ideas and fonts, sometimes pictures in the back, etc. which just pisses me off.

+1 for native LFO device

The biggest downside of m4l for me is that it takes so long to load, even with a ssd. It kind of feels like it slows everthing down.
Also projects with m4l plugs take ages to load. It just messes up your workflow and feel.

Yes, same here. There should really be a feature to 'convert' M4L devices into native Live9 devices, because I don't really care for the ability to fiddle with the routing / modular aspect of M4L devices, just want to have access to them and use them in my music. Only if someone wants to toy with M4L the instance of it should be launched. Instead - as you say - it consumes your memory & CPU, without any particular reason or benefit.

[S-N-S]

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

[Quez]

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

[Warmonger]

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.

[antic604]

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

Stealth brag? We all have Suite (or at least purchased M4L separately) since we complain how inconvenient it is to use it. In my current project LFO is THE ONLY thing I need M4L for and - as said - I shouldn't be paying big performance hit because of such a trivial thing. It should be a standard device in Live, all of its versions, especially since Bitwig has it (+tons more sophisticated modulation / routing options) natively. Thanks God for competition!

[Angstrom]

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.

[td6d]

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

[spektralisk]

+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).

[td6d]

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.

[alec.tron]

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

[td6d]

+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.