observing clipslots/stuff and almost all in a liveset ??

[julienb]

hello,

I just finished my protodeck controller.
Now comes the time when I have to build its interface with Live... of course, the interface will be a m4L patch.

I have to:
- map midi events from protodeck to live
- map live feedback to protodeck

if I imagine how to "translate" midi message from protodeck to trigger for live, I'd need help about observing things from live.
By observing, I mean:
- detect/get coordinates of the clip in a clip creation in a track, in all the clips slots
- detect a clip triggering
- detect the position of the playing clip in a track
- etc
If I understand how to do that in a particular slot, I cannot figure out how to do that for all the clipslots.
it may involve a kind of loop...

I'd like to know if some of you have ideas, tips, part of patches to do that.
what could be the architecture of this kind of patch?

any help/idea/tip/word about that would be appreciated

[monohusche]

one way of doing could be to create an abstraction for a clip slot observer which takes column/row coordinates as parameters and outputs the various events plus the coordinates.

then the messy bit would be to dynamically create all the observers in a loop using jscript within a bpatcher which collects all the outputs from the various dynamically created observers.

the max help describes jscript, have a look.

[julienb]

hello
thanks for the answer

indeed,it was the way we did it while live API wasn't official yet (you know, with all python stuff)
so I can figure out it

I thought that there was a tip with object observer like a kind of "all observing" parameter given to this object.

I'll try to build that asap!!

thanks a lot

[julienb]

I'm a little bit stuck...

if I'm ok with listener in a code, I cannot figure out how to do this in a patch.

for instance, should I make a big loop polling things everytime?? I guess Answer is no!!
indeed, I could make a big polling when I connect the protodeck controller. but even in that case, How to make a kind of "loop" ?? uzi? metro + incrementing value?

[monohusche]

I guess, you wouldn't need polling as in "traditional" programming as live.observer is already taking care of that. have a look at the live.observer help, you feed it a parameter to monitor (such as "is clip loaded"), and it will fire automatically if the value changes (e.g. adding or deleting clip). the only thing you would have to do is to "kick off" observation by feeding live.observer the path to the clip slot (right inlet) and the value to observe (see LOM).

for that initial setup, you need the loop (across all visible tracks and all available scenes)...check out the M4L abstractions under Max/patches/LiveAPI...

lots of practical use cases...

hope that helps,

nick

[julienb]

okay with the LOM (precious document!)

I guess I don't have to create a lot of live.observer, only one, right?
I could use a kind of Lookup Table which would be feeded with the live.observer results and which feed midi message to my controller to light led

observer => LUT => midi messages => controller

the lut could be a coll object (I opened a thread for that : http://forum.ableton.com/viewtopic.php?p=984982#p984982)


the feature of "creating/removing a clip update to my controller" isn't the major thing I'm looking for.
I mean, I can force a "scan" of the liveset at the controller connection or when I want to...

[julienb]

I did that:

Code: Select all

----------begin_max5_patcher----------
1399.3oc0ZssaiaCD8Yu.6+.gw9XRflgT25as+FEKBjsUcztVRFVxsocQ+2q
HGJakD6DJZRosH.QXnt3gGMyYNbn9wm+zhkqpeNuYI6WX+NawhezMxB0XxQV
zOvhkkYOudWVi5BWVk+W0q91x6zmqM+4V036y9NCXHie5T+QcUaUVYt5z+5g
hrcreqd2lSmuXi5LcOs6CSNMZ0wxhpc4speM9vmUSw+ndVPvCACt55is8WNz
O79r10OUTs8wC4qao4GFlzcarPNmNH+OzMD6q82D8fZ+684zcrbI6qpS8ue9
SxicGt61goCEUsVAQQWFhfwAQAF.QgQxC7APj0vv55xx7AS3S3P6gr0eu4dv
JnP3cnHTnl7owJ.I1mHQy57pbaQBt2QBQp71XXPfyfhqkabOyNP.tLHfti7P
vin4sBD33CgeH4gLM+VvnikqxOXEbfNIl.M.NRSUwDAFvkpX8XKWkUscoOxh
dJq4w06J1aEhE3+rHTQnHRTLrhTOlEcrZeG0JqXCKvFvPj58vGNFpPgPELDE
YRo36lwLJA2+PRLNH9XJynbLYrv+jw.nvJHNYpHiKyaZx1l+VPp6pXewJbhG
NUEsPf3bHEMQSthWMeTS2eVQHwicR1G+8x9RzfCHODCFRH4BRoq.Z6J9y7G5
7zmrBwR7OhER4f5USMFDyKIhaqaqYRP6wl716XayaWWerpkQhqsBDS8dBZOH
Bpxg.srqYHCcWc1FUYDKfIzMKK8846IU25EmZPn1sVS7578EU1Qhg9mtGIdK
jvIdrmCl7PMQTLUZGPHZZpIZslSz+qhqWGktIG+Dn47VkJff2K7EQvD0or+2
qT.C7NfgIjPgfetEJP8izFLD7uPAMFpyW0pF7Gq0piss0UWbt9QJKGcU8HN0
cw9+OGU06BBX2R+ifH+GAPjz7TUcqnj4Ronjro6LR+xllC3eI0nJdRfJbJL0
y6xy6u8FVEKE5+s4If5KPrR8COxmatgLkpYWcqcLq9eed3zFApwBu1W1apPM
v8egZMEiHdRqTORIxcy8hxiku385Pb5rr4tek9qD7sTZTLLLZRkR6V3CtH7k
581eGfyD9YlPQs7P1WPljQ6QEklkqxMcxDKnkMl.yjZA4mDRfcqjKw+JEnPN
d.LnS.S+2CRKaEamMHTr26OPeXTTrw6yB0EwKgTzM0UDr5MevQpeZ4IdE90T
e7v59mb+VSxfy+7axaZKpxZK5VrxfqpqTIafS9TwlM4UufwqrXy95NBjl91+
Cx4lPugRCrduW3l61uxgtraK+DnXnEtcHs3IYfbukSbaYoTCc6Qg1XHNvswt
nKm51u1gthaGMZ2V6nZAiCrbCZCFi1vnBR.UXAlpH3PZ+keoEm1+ALQHuRkk
SlRnQAPxl9Nt2DtILwHmStKsyfyI2xygbAWIX.lGjyrHUbrNmPDppvjp2t5y
VtgE1H2FGsaCHPNJsN5AVtIIBLITP.151wwCcaokanyLhEVtGqizsgToiRe3
Y7Hn2vINcrQxKFMCrt9bBIiJN7sVBpqUxOBnPskah4M4kfXzuD3jVPA8Qxx4
hSVtg8KzD2F.KIXP5q7fq2IvWZESuHzEMic0KBzSSILIflR3P2VZ4l2DoFkE
mLOEISLgYTUJc5cNHxnTuQm4EDQLDz6acdHhSaXJdago5E.3tvTzHvFRrrXi
dKeOa3Fm1HxYLzxB6HsKg8HeHNotMXqLJMc7oPDvUtcfIjE37nnFLhlUMElA
myHkbvMpjK14B49XWNxR1WdhtygmsbCRaTehhs0qouy9gVNwqMJ1E3150TiY
GZMgM2Zzcaom2JUqLN5j0D1jnQWm6TOhdgJxTWEWaDARpkNc+pqzAHWrMhxA
5N7e.KRj5cB
-----------end_max5_patcher-----------

when track and clipslots change, it get has_clip value. it is a beginning. I guess it could be improved but ...
I'm adding the observing things right now . . .

[julienb]

Storing (id,x,y,has_clip) where id is the object id, x track number, y scene number and the has_clip property value...

but observing the clip in the lookup table (coll object) isn't easy for me

Code: Select all

----------begin_max5_patcher----------
1809.3oc2b0ziaaCD8rCP9OPHrGRA1cg3mhp2ZO2i8VPvBYa0cUisjgkbxlF
z+6UjCks75unnIkWTDr1lxxlO93LuY3P57yO9gIQSqdMuNB8qnOilL4msWYh
9ZpqLo6BShVl85rEY05aLZV0xk4kMQ2adyl7WazuweTU80MqP+Y1zE4nuWz7
BZ1hhUOUunpoV+RTcSVS91O3hhx7YUaJ0eZR2UWsNut8qOqonp7oieK+UUYS
Y1xbcu9aqKxVf98pEy29EWLW+NUS+6GDhni9EuNeVCLr4x3GiuGg0ORHIpmX
zGiQeo6CVtYYQ4h7F8vG2GD0E+iFDXQ6mZ2cWsoo612d4UYMydon74d8rfvU
cFOA.PJ4vttOl0cj95+6G+f541mt+5m0Jl+jZtAlkdE8CzKY05qD4BcytDcS
RnpgI7ngtU7P3oaLNUS2rzdz89cs+n6k400YOmeHcSQXTLB6B4xkWhbYBolb
E5Ap90X4I4VxQ4Vxo3V7Y3VJ39v4zS0yGPscuAzCM+XUN7UEEg9h+o857Fzc
XzcDzcTzcLmn+jnAPiwWCMRzlnRrlFE8oQuxVmTS3Zj.3hnP6ISS0lYLFETt
S24I6etnYc1ruh9zq+hSjA+htrZEPvsUNhhgBsFAgp4tD1MQKb1h7r0tPqrv
6JJhAWQlNLAkEXWwx7u2NvNBEUsXgSLzEy6QvzYeH.E6zG4mMVAdXLK6LLK2
zkIjS0yCHVw889a2WPc12xm+TKOz1oOk0zrtX5lFHO2I6lAlDkubZtlyhgqX
l475L3lxUJAjLDwo4QdjOlOHmSJfqMDXP1nBxgwtOJsWnRJ2+F7ZxpMAIDAQ
chvHGmvXdLJsI7SJPXI1PXAKxT8CtkKIyK1UmKDCGVVivrHmcrj+Yh5Y4k4t
xDzfyDTtI7A0aTwobedvwkVfCetsP.ULjzFkbnr+AdMWqDylV4cmxufSBtpa
Gc.5sFekKSGsBuSyJeNDJul.UEyQwNI7lFbNi.JtLXg7PFriPjJmMiXzvaFA
4mZVJz6AyHGUfXgWABGC0kfIFKEnStxm16BcmS7DkOZJ0P8GX2pk9Xzipa+m
SBRzDu38QOmfDCrnHZNJAaofT.SedQw2xerEou3DiICOioKWAJEpP4PHrf3G
9bUSERwYOUm2bO547F8tMffDJchCSCt+ogCgxEg4haj+4hpr45fHNvRDgWrz
NuZulX.CMtEFZWa.wSK1WT5lBFI7Z8DX4qDfrnIA1VJ.ADIrQKwAIabBH5bB
mjvutkNtvrr92Oqaw47DH3fG0ynQSD+uHMAR7HjXkNKA466rDfBv4BEhGgrD
zTn4vMvIAVyZ5lllpxiNTuTRkCNjNECgr5d7VDSu0F3pNnDXQ3M.fxTSg5jH
j2pzDURMvVw3TcAFMdRlZ1OpaT472cJb9zObZylwW9v2.6wCXJDyFusalBG5
Fy1Mu2N16+8aNHA8vzvGzyXHh4iZXuAltY6XuX4lk6Mi2mmHWxHDiA6O7oRf
rEcc8.N3kTl12v7Xnw9Mi1W44524C7EmOfS+gcyGoguF+x2aSH1kWnIaP0QL
q2wd0s0zlNVA8Hohdk58FjcvpL0t86z51ji.IA1hhzdq6WN5bTCZJxoCATxH
ribPHKnvQVskJPICOFSAeH8wB+sGIccWqdi2ve0UaVOq6ataWHQ3cc+775lh
xsZEed2Fyg5AxWJlOOubOIzkEyWU0JfT2sE9X0XiAFA8actIb6g8a.zIfcar
UD0EXCKCj0Jm10xOvlXCrUGb1gw1rXskDGaRHJcaKu.62BnS.a4fMRL.0rAi
8Z4G11JXqN4eCC1hX.nvw1Vct75ZMhFICG1cFIBbeXqZ4GXysRIgLTXShS56
RBCB+4RhsSIgOXaa.nTJblqErss7CrIVK.hGDayj8YarzyrM1ZXSFFaqMRHf
sMQxg7P1qkD9ArjjdXqtgKk42gqzlQa5vMsfAqTq+XLzzsFw4HoqnVDCndWq
QzgP5n+.AN1YTHiMcKuf5Ta.Ml5p3ClzyBQ2ZD0LSbVxj0G0TekynUYCfEth
Z9dbM2absUZH3AKhfwbEPgsytMrj409AyVYVq1VrggYu.Nc2RtH3v2FvwrZ1
lL7YaPtE9gx0IpoZMhvlvcE1lerwfK1aZECA4SD56L1WoyRDVMSHczuiXpo6
1F9Az7vX9zwtz39lOTuE61Jtl4pxrj1WYV5qTvUm9uKKjPStIBITqjfoxaiJ
mclo3qyLsKESuYlRCDroP8DHlhB1AaeEM1JsYVpidWL3vURiYaa4sr0v1HIf
GVEm.zJnm9I3Tqo9gBvMsFwD4nNmHm4+fH11vOdpXaz3XXGCrigeSs8a4GSd
qVBKw0znTUyoGrE9xDgaEr4DGEXvP8P52xO5hI1XjvuMYTyspt.T9sIPnUfi
vtZvotP6S+GP9bkfW
-----------end_max5_patcher-----------

[Surreal]

i think you will have much better fortune when we have access to all of M4L. the control surface portion looks like the way to avoid writing per clipslot.

[pukunui]

The best way to observe a large number of properties without tears is via the JS API object. My APC40 observer patch went from a nasty 160 odd voice poly~ to about 10 lines of code.

We hope to have some more examples of this in the not too distant future.

-A

[julienb]

to get fired clips & playing clip, there are properties from track object
it works very fine
it provides the "y coordinates" of the clip as soon as it is fired or playing. x coordinates being thé track number.


nothing yet from live.observe and adding removing a clip

just hope too

[matcham]

The best way to observe a large number of properties without tears is via the JS API object. My APC40 observer patch went from a nasty 160 odd voice poly~ to about 10 lines of code.

We hope to have some more examples of this in the not too distant future.
-A

would you share this "APC40 observer" patch ?
I would really love / need to see more JS examples..

thanks in advance

MathieU

[julienb]

The best way to observe a large number of properties without tears is via the JS API object. My APC40 observer patch went from a nasty 160 odd voice poly~ to about 10 lines of code.

We hope to have some more examples of this in the not too distant future.
-A

would you share this "APC40 observer" patch ?
I would really love / need to see more JS examples..

thanks in advance

MathieU

I'm sure andrew works around beautiful and tricky JS examples for the release date!

[Bugayev]

The best way to observe a large number of properties without tears is via the JS API object. My APC40 observer patch went from a nasty 160 odd voice poly~ to about 10 lines of code.

We hope to have some more examples of this in the not too distant future.

-A

Where are the existing examples of JS API?

Thanks

Nick

[julienb]

I guess we have to wait for several days before getting them...