[m4L] finding the clip position and use it for warning zone

[julienb]

hello,

I'd like to use the position of the playing clip in a considered track for warning me : hey, this clip is finishing.
it could be a ratio between the total lenght of the clip and the current position:

current position / total lenght = end zone ratio
if end zone ratio > special value, it warns (led blink or ...)
here, the led becomes red.

so I did that:



it works but it has to be improved and probably, fixed!
any ideas? words? fix? improvement?


there is probably a better solution, but as I didn't find properties like position value etc, I have to build mine.

[Trypset]

man more power to you. I have no idea how to even start something like this. I'm still practicing getting the actual "sound" I want.

It's nice to see how Ableton can be so advanced...

[julienb]

man more power to you. I have no idea how to even start something like this. I'm still practicing getting the actual "sound" I want.

It's nice to see how Ableton can be so advanced...

héhé
it could be fine if there was a kind of "position property of the playing clip" in the Track object

[julienb]

no more idea about that?

I'm sure I'm not the only one interested by that

[#1thelark]

I don't know if this helps, but you wanted ideas, didn't ask for smart ideas :

Maybe theres some kind of exact time measuring running in the background, so you could get the exact time for the "start clip"-event and compare it to the actual time... that would give you the possibility to measure the time gone since the start of the clip > comparison to track length > start blinking if measured time is less than X seconds away from the full length of the track.

Just my 2cts.

#1thelark

[S4racen]

Hi Julien,

Have you seen Olivers patch over on the cycling 74 forum, i'm away from my computer so can't tell if you've incorporated it, i don't remember a metro object in it?

I'm using it to the calculate when half a beat from clip end. if the clip is looping then nothing happens (gswitch) but if it's not looping then a call fire another clip dicated by a live menu with the options of play above, again or below... With this i have follow actions at clip end... Is that what your aiming for or is it a feedback led thats going to your Protodeck?

Cheers
D

[julienb]

no that isn't.

the clip position would be a value that could be observed.
for example, this value could be read in the track path of LOM.
it would provide the clip position.
the workaround sucks, but could work.
it gets the length of the current clip, and the position can be deducted by using the BPM and a metro that start when the clip is started...
ok, it sucks.
with a LOM like that, we should have this value too.

[benbracken]

clip has a currently undocumented property, playing_position. Its absence from the MFL ref is an oversight and will hopefully be there for the next Max update.

-Ben

[nbinder]

Your patch has exactly the problem I was talking about in the other thread: It is NOT a reliable method to get the playing position of a clip. If you don't use loops, never use the "jump" buttons and always start on the first bar it does work... but abandoning all three is unacceptable. You might get around all that, but then you will have to observe all those possible events as well.

C'mon Ableton... you already HAVE a property of a clip (or of the currently active clip slot of a track) for the playing position: It is displayed on each track anyway! Make it available in the API/LOM!

[nbinder]

clip has a currently undocumented property, playing_position. Its absence from the MFL ref is an oversight and will hopefully be there for the next Max update.

-Ben

Really? Can't wait to test it.

[julienb]

Your patch has exactly the problem I was talking about in the other thread: It is NOT a reliable method to get the playing position of a clip. If you don't use loops, never use the "jump" buttons and always start on the first bar it does work... but abandoning all three is unacceptable. You might get around all that, but then you will have to observe all those possible events as well.

C'mon Ableton... you already HAVE a property of a clip (or of the currently active clip slot of a track) for the playing position: It is displayed on each track anyway! Make it available in the API/LOM!

+++++1
my patch is only a beginning
it has to integrate several things more.
but it could work
but it should be a thing in LOM !

I'm happy other guy are interested too

[julienb]

I forgot to write in this thread I asked this in the feature request: http://forum.ableton.com/viewtopic.php?f=3&t=130610

[yop44]

Hi Julien,
sorry if I misunderstood, but why don't you consider playing_position property of a clip?
Ther's a little delay in values, but it works fine.

[julienb]

Hi Julien,
sorry if I misunderstood, but why don't you consider playing_position property of a clip?
Ther's a little delay in values, but it works fine.

guys, ok. I have to change my glasses!
in the LOM doc I read, I didn't see playing_position property ...
hey ... wait ... there isn't !
strange...!

btw, I built that for those interested.
it has to be fed by the track number, and you'll ever observe the current playing position.
as soon as the playing position is near from the end (the end ratio is all yours), it provides 1, and everytime else, 0.

----------begin_max5_patcher----------
1744.3oc2a00aaaCE84Tf9efPH.6kzLwOk3dX.c.q6sUf85ZQfrMSh5jkLjT
ZSaw9uOQRIGEGaKRaRws8hUnjpzkGc+3bOj86u9UWDsn5QQSD3m.+I3hK9d2
YtPcN4YtX3DWDsN6wkEYMpaLZY050hx1nq5uXq3wV0Ed+6dGH+VP68Bvxh7M
fMUM4s4Ukf7lxenEjWptjnbE3aUkhOT99+3s+9u8q.QQiX6CqHuTrr5gR0SD
Mb1aqJaKyVKTul2VmmUr8eP4CqqdnsPzpLt3gSmuRcuUK9zaPoQieNM4eS8b
fwWu8t2j0t797x6toVrrUiFz3ztqCnbr7.BBUG3WGC93nWcd4vaFpN4e+5WI
O1c3pyGOisBMg9GHYmBPlRjHGKlp.v3XugiZq2l4CM5XN.Iis6s+dHyd3rCe
MkujH26SzVms7u.cu5Eh5H27UkbReUUgEPt72Tj5uS8v2zRwW5rwWBCEUYqV
KZZ.wWmXOL.2GLf1dy56r8qaD54ZTzSyKKfHl1ogFqfmDn2.IIPjcm3knzl5
pMh51uB1Tj8UowMjC4HPF3WpJVYAtAicMtQvpLuDp1ECqxe.YGD3PN26pEr.
TbhXDZeXD7vXzhrx6ht5bwJjJPDRRm+Hw7OKttZQin9yGMij0XF4H9UmMdkv
LCubuuU1lMxZ1xR5tIwE24weHUBKrNsNiN6tTxvub6Am84EkNcfWtrX84fSw
JhBX9riSeq.7op7R2fTLuDt0CQzTifHuFscSSQU2qwIwbDmGyoYIiiUPDGFl
z3cF181CP38wlZBuoy0ihD2ysxa.0AYf+juz.sJvsU059zpJaxWIpEq.Jd56
uYLrSnsiQmBscHuGwTbq3ppfD3bBe2lWKTf0ZQacE3K2KJepG27FPSaVcqXk
OgND+TfNhVIfdnKgL+P2Gh11seDnNqiHui5.L4TvCFeb6MdrGvEOz1NpkECZ
kCOQU+mLw8RQTkCFkzKXwvuyVp35NiV.dCzM00QP+viVCRDrlNs+pWMkRG11
WA5H8qJoBd0K7QrGV5yQ3QXY5V9k4YWopScSd4Jwitrk+T22xuF2v5lMvnYu
keu0FK2igePsFkP17Srt4KYabSBJHcx.xStEMHQm9FpYWSmcXZyXVfmUKGPm
qO4.3nyg6QvQ8LrYpZzL8fR1qEkdRE6icqh8EBaRglvOtS+DLTzKMEUME0A+
rmshJKtaYUQUs91iuFSQbxU64OfyHsle1gUfRRME9rWaPpt5S2uzYNYg3wM0
fKuE9iWdKxkfEySJzS0JekL+oUenbhDq1Vlll5whPoTsF8zPQJ7NQKnPTd2Q
U2wV2Jh6KHoAJbR+Ju+e908gf8059L.UTEwlDTnV1mOIsHG5SQ7jOEIFZDPg
BhvpGCl1m5pDnujWERU3DVWCLMIHq8iKCAwbuEB1SeloWai3.jVupsBH8uto
oKAuRw4FvkvQq1A3RzTqznsgnXm27+fOmdsOPwdr4eWKlDNwihI06fMHlT5+
B1+HdQNIL0Sc1NHmDgFFlDmQpLx9vIhAoxtxQo0fpaCPX++YGkfw9PJtA7Zf
tp+jhy15.tLDE57PT8B3xzatKHOLB95XdY3XuwKSCWopnwTa2pI5aSsTp6tW
uUuK4E1ACapdnd4fsOH4BXzKbknoMuLSsaBGcW7meW2muZkn7YxssNe0lpth
i8VB3iG9Sq4FGyHiKMHFmbmkZnwAsw3XXhThJpds.52Ra6LBknyhC2NxM3sQ
NCx8Wsc3MgjnlRT8VOiscfSrZnIFsb4Hr76fxLQ5BlPFc6n4ynwPaQ5drEqD
4DRFF3DSltiq7Ab3Y1BzHjRSVZLVq9Hd6H2DmhMApoo16TmpbI358IHio+e.
w3QD81L.xUeHHHW47H0SwGSI23Yajwsap84JosItvPXX.NnQFGw13K2XbwFk
kkDNjaZiKNHFG2nZpAwzLhdUXn9YDSDVvLMnIl17GkJEtZZXy55BPBeLWnTc
otmOhq24jZEle9HbrtZHFJeJpQtoLnW7QjaHToYRHiMZ4H27IxnbUVmGsmrm
d+ZxGs2M48eBfi5eXmQ8ZB0OucFEWjQyzcomMWDALpdFJPLALqlQXpmI0qDf
mrXK21DfTthOcurtiG4NyFMoYGFNyRElltlBlDtO3SabXq66iyuFxXLJSpyp
decwUEZTibmsOce1zvDlaDIGXXHfsqfIGv3PgoaDpQHWXXUaFILXf74LR0Rb
X74LiaDNP08LxmCGF5LXiD4ZWOy4x33FU.IMbFWr6Mt9dl568AxhcauOXipc
PBC+UhQdijvjdlXjLaDb3PtoMtvnAHwnZGjymkp7DcG9GmV3fgB
-----------end_max5_patcher-----------

[S4racen]

I thought you'd seen that sorry mate.....!

Should have sent you a link to it... That's about how i've got mine set up but i'll look into the different objects you've used as it looks a bit cleaner.....

Cheers
D