Ableton Forum

I have uploaded the device file for the updated LFO MIDI object at the link below, I also included a screenshot and vague explanation of how to do it:

http://jgarcia.hungry.jp/project/fully- ... -lfo-midi/

thanks you

agree - every time I come back to use this device I end up writing this

in the words of Geoff Boycott - "rubbish"

now I remember this problem - you can automate rate as long as it's not syncd

WTF

Jdudeo wrote:I have uploaded the device file for the updated LFO MIDI object at the link below, I also included a screenshot and vague explanation of how to do it:

http://jgarcia.hungry.jp/project/fully- ... -lfo-midi/

thanks for joggging my memory on how to "fix" this - bigup

Just noticed the same problem is at least partly in Robert Henke's LFO2.
If you map it to some contol, the mapping is not restored later when opening the live set.

It still seems to be a problem here that the sync rate is not saved with the project with the nativ M4L MIDI LFO (seems to work for the "normal" native M4L LFO though). Or did I miss an update? Can anyone confirm?

you should download all max4live packages on your account.

1.they've updated every max related packs

2. Max audio and midi LFO are working like they should, automation both for sync and rate and everything is there when you relaunch your project


The most always annoying thing is about ableton which doesn't give us a way to check if our packs are up to date.

Long time requested, I wonder why ableton team doesn't move about this. Really guys this is all pissing us off.
No, ableton users have to think from time to time to compare their packs with the ones on ableton website, how lame
They could avoid a lot of complaints if users know they can update this or that to resolve such things like max lfo mess.

well that was not the point sorry for this little off topic

thx for the info.