Hello,
I'm new here (as a lot of use, as m4L is new and still beta..)
I used a lot the Live API with python til the big announce of official support and m4L release.
I built my own midi controller (midibox based): http://www.julienbayle.net/diy/protodeck/
I'm now beginning to build a patch in max for live in order to create the interface between the soft and the hard.
I need to transmit pure CC value of my pots (easy)
I need to translate midi note sent with the controller in firing message for clip and other kind of trigger.
I need to get feedback from live to light up my RGB leds.
I'd like to know if someone could be interested by helping me in this part of the project.
If I understand how to observe, trigger etc, I cannot figure out yet how I can do a big observer for all the live set that reacts with:
- clips triggered
- clip presence in each slot
- clip position
etc...
any help would be appreciated
I posted that : http://forum.ableton.com/viewtopic.php?p=1005911#p1005911
I'm looking for a max/msp guru in order to finish my patch... anyone interested by helping a nice guy with a very big midibox-based controller named protodeck ???
I have some question about patch architecture.
Should I make a slotObserver abstraction included in a trackObserver included in a matrixObserver?
Or should I use a lookup table which stores all clip states and only send change to the protodeck??
I hope there won't be only people who will leech my opensource-base protodeck page, but that there will be people who will help me to improve this (open-source) patch :-)
protofuse
http://www.julienbayle.net/diy/protodeck