handling clip matrix

[julienb]

Hello,

I'm working on a patch to handle clip matrix.
I understood how to navigate inside the live.path.

I'd like to use a "structure", synced with my live set that stores:
- clipslot state (has_clip or not)
- clip state in each clipslot containing a clip (state: stopped, playing, triggered)
- clip ID (in order to fire it from my controller)

I don't know the best way to do this.
create a coll? create a jit.cellblock ?

This structure could be active (if I add a clip in my liveset, the structure know it) or inactive (I send a process to grab the clip matrix at the beginning, one time, and after, only clip state changes if it changes in Live)


any ideas? any tips? any good practice?

[Surreal]

have you looked at Live object model? there is a whole set of objects we can't get to yet and button matrix sounds like it will doo what you (and i) want.

that said, check the monome thread here for a patch that almost does what you want. (i don't have it checking for whether a slot has a clip yet.)

[julienb]

hello,

I didn't see objects that we can't access too (I probably missed that)
Live Object Model is very a must, indeed.


btw, with monome (and monome clone I did) everything already works fine... with a java code we did with Tom (http://code.google.com/p/monome-pages/)

btw, my main questions are about interface design & concept.
I can make a clipslot system to listen things, fire things. it is easy.
after that, I can copy-paste it as many times as needed (my "window" matrix is 8x6) but hardcoding isn't my way, usually...
Does it exist another way to automatically build that? to dynamically manage this concept?

[charles_2]

Hello,
I'd like to use a "structure", synced with my live set that stores:
- clipslot state (has_clip or not)
- clip state in each clipslot containing a clip (state: stopped, playing, triggered)
- clip ID (in order to fire it from my controller)

I don't know the best way to do this.
create a coll? create a jit.cellblock ?

Either should work, but I'd use either coll or table. You only need one variable for clipslot state, with four possible values (empty, loaded-but-stopped, playing, triggered), so you really only need a one-dimensional list:

index = (100 * Y) + X
value = 0,1,2,3

You can use matrixctrl for UI, if you need it.

[julienb]

hello charles_2,

coll seems to be fine, indeed.
I'll modify it by live.observing my clip matrix, and use it to fire from another controller.
great.
btw, it is a beta. when I began to make my patch, I have to be careful to save it progressively ... cause sometimes a big crash/corruption happens (not sure it is a bug, perhap my installation: I own MAX so the final version was replaced by the new one)

to feed the coll object at the beginning, should I make a 2 dimensional (1 dimensional.. cause y=f(x)) loop ? or should I modelize EACH button of my controller like a hardcoder nerd ?

I post this
If someone is interested to have discussions about interface design, about max, about live feedback and control...
just post