Cycling 74 » Topic: clip position, two better ways to ? http://cycling74.com/forums/topic/clip-position-two-better-ways-to/feed Wed, 19 Jun 2013 05:41:58 +0000 http://bbpress.org/?v=2.2.4 http://cycling74.com/forums/topic/clip-position-two-better-ways-to/#post-47064 <![CDATA[clip position, two better ways to ?]]> http://cycling74.com/forums/topic/clip-position-two-better-ways-to/#post-47064 Sun, 06 Dec 2009 14:56:57 +0000 Olivier Sebillotte Thanks to gavspav and Andrew on ableton forum I made a small path to explore 2 ways to get easily a clip position.
I made it with live 8.1b1, I am not sure it wil work with 8.1

enjoy

Olivier

– Pasted Max Patch, click to expand. –

]]> http://cycling74.com/forums/topic/clip-position-two-better-ways-to/#post-169211 <![CDATA[Re: clip position, two better ways to ?]]> http://cycling74.com/forums/topic/clip-position-two-better-ways-to/#post-169211 Sun, 06 Dec 2009 19:05:59 +0000 S4racen 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

]]> http://cycling74.com/forums/topic/clip-position-two-better-ways-to/#post-169212 <![CDATA[Re: clip position, two better ways to ?]]> http://cycling74.com/forums/topic/clip-position-two-better-ways-to/#post-169212 Sun, 06 Dec 2009 19:21:04 +0000 Olivier Sebillotte 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

]]> http://cycling74.com/forums/topic/clip-position-two-better-ways-to/#post-169213 <![CDATA[Re: clip position, two better ways to ?]]> http://cycling74.com/forums/topic/clip-position-two-better-ways-to/#post-169213 Sun, 06 Dec 2009 20:19:08 +0000 gavspav 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?

]]>