Stephane Morisse

As of now, IMHE (for 'experience') the LFO from 'control devices' folder and M4L api LFO from 'building tools' wave don't reset by starting transport as stated in the LFO~ subpatch in the building tool version.

There's an abstraction to observe transport and resync in the LFO version, sending a 0. to the phasor phase to resync, but it doesn't work.

I try to build complex spatial paths using them and it's a nightmare.

MBP non retina 2 x 2.4 Ghz 4 Go RAM OSX 10.8.5

As of now, IMHE (for 'experience') the LFO from 'control devices' folder and M4L api LFO from 'building tools' wave don't reset by starting transport as stated in the LFO~ subpatch in the building tool version.
There's an abstraction to observe transport and resync in the LFO version, sending a 0. to the phasor phase to resync, but it doesn't work.
I try to build complex spatial paths using them and it's a nightmare.

MBP non retina 2 x 2.4 Ghz 4 Go RAM OSX 10.8.5


lfo-transport-resync-bug

I've found that transport sync of phasor~ in M4L is generally problematic, in particular at start. This can be verified with following test: open the phasor– help file and copy the subpatch 'using phasor~ with a metro' into an M4L device. Now with repeating start/stop of Live you may notice that sometimes the very first click from phasor~ is missing (left channel), in contrast to the click from metro (right channel).

LFO transport resync bug ?