I've taken the live.observer version and totally stolen it for my next patch...

It just works! No glitches... It's perfect!

Thank you!

Cheers D

be aware that live.observer could use more cpu than you expect. That's why I show another way.

glad you use it anyway :-)

Olivier

Max for LIve training sessions in Paris : http://www.apaxxdesigns.com/Max%20for%20Live/MaxForLive.html

Do you think live.observer uses more cpu per se or is it totally dependent on the refresh rate?

Also the get length value means something different depending on whether looping is on/off. And whether warping is on/off.

Havent had time to try this but maybe it'd be possible to get the initial playing position, then update/calculate using tempo but check the position (at a low polling rate) and see if anything has changed eg scrubbing/looping/follow action etc. Plus checking for tempo changes of course.

You think this would work? It might give better resolution feedback with less api calls?

OT Do we really need 3 (>3?) forums for M4L?