Weird LFO behaviour - is this a bug?

Learn about building and using Max for Live devices.
Post Reply
re:dream
Posts: 4598
Joined: Fri Dec 28, 2007 9:42 am
Location: Hoerikwaggo's sunset side...
Contact:

Weird LFO behaviour - is this a bug?

Post by re:dream » Thu Mar 21, 2013 6:37 am

So I have L9 and the latest version of M4L.

I have a track with two instances of M4L running next to each other. The first controls the panning of the sound, the second is mapped to a macro control governing sample repitching on a sampler . The second LFO is set at a sync rate of two bars.

When I save the set, and open it, the sync rate on the second M4L is wrong. It is set at 1/48th.

Then I re-set it to 2 bars, save the set, re-open it - and voila, it is back at 1/48th.

I have notified Ableton, but I would like to know if anyone has encountered the same problem.

Valiumdupeuple
Posts: 1134
Joined: Mon May 31, 2010 12:36 pm
Contact:

Re: Weird LFO behaviour - is this a bug?

Post by Valiumdupeuple » Thu Mar 21, 2013 10:32 am

Not this one exactly, but for example, there's a bug if you map a lfo to the parameter of another lfo. This has been report during the beta phase but it's not resolved.
(btw, you have no hidden automation somewhere that would cause your problem ? )

re:dream
Posts: 4598
Joined: Fri Dec 28, 2007 9:42 am
Location: Hoerikwaggo's sunset side...
Contact:

Re: Weird LFO behaviour - is this a bug?

Post by re:dream » Thu Mar 21, 2013 11:04 am

I realized after I posted this message that there's another thread about this on the forum

viewtopic.php?f=1&t=190624

It's very simple: the M4L LFO does not save the values of the LFO rate * if the LFO is set to sync*.

It does save them if it is set to Hz.

Apparently you should open the thing up in the Max editor and change the parameter. I don't know how to do that but I will have to find out.

Valiumdupeuple
Posts: 1134
Joined: Mon May 31, 2010 12:36 pm
Contact:

Re: Weird LFO behaviour - is this a bug?

Post by Valiumdupeuple » Thu Mar 21, 2013 4:10 pm

I'll try to have a look at the patch if I have the time.

Post Reply