im pretty sure the 'ring' is going to be controlled by the secret handshake between Live and the APC, thats the impression i got from Jesse on the other thread.

Im confident one of the boffins here will reverse engineer it using MFL, to allow other devices to use it.

I don't know it if *will be done* but it should be somewhat easy to do, given that
a) Max supports transparencies, alphachannels, that sorta thing.
b) m4l will support floating windows
c) It'll be cool in itself to sorta "mess with" the gui, hehe.

Tone Deft wrote:
especially after dorking around with automap for too long and the notorious 128 parameter limit.

i've gotten around this by specifying my own protocol via midi. i use sets of 3 messages to get 9 bytes that describe what i'm doing. this allows me to send functions from my midibox such as getTrackDeviceParameterName(track, device, parameter) and send it back to a midibox via sysex. non-string data is sent back via the same protocol. i actually am able to query, listen to, and control anything i want. any events triggered by mouse or by the midibox is automatically reported (if you want it reported) back, so live is slaved to the midibox and the midibox is slaved to live.

it works on a "tier" system (can't think of a better name) that specifies a category of you are controlling (master, track, return), what aspect you are controlling (play button, track device, clip, etc), specifically what to control (device parameter, clip loop, etc) and how to control it (increment/decrement w/scale value, on/off, toggle, etc), all wrapped into easy functions like setTrackVolume(increment, scale value).

doing it this way gives me access to 128 parameters on up to 128 devices per track.

im pretty sure the 'ring' is going to be controlled by the secret handshake between Live and the APC, thats the impression i got from Jesse on the other thread.

Im confident one of the boffins here will reverse engineer it using MFL, to allow other devices to use it.

I don't know it if *will be done* but it should be somewhat easy to do, given that
a) Max supports transparencies, alphachannels, that sorta thing.
b) m4l will support floating windows
c) It'll be cool in itself to sorta "mess with" the gui, hehe.

Wouldn't the joke be that discovering the secret handshake could be done by just hooking up a print object to the APC in Max for Live?
Wishful thinking on my part..

Tone Deft wrote:
especially after dorking around with automap for too long and the notorious 128 parameter limit.

i've gotten around this by specifying my own protocol via midi. i use sets of 3 messages to get 9 bytes that describe what i'm doing. this allows me to send functions from my midibox such as getTrackDeviceParameterName(track, device, parameter) and send it back to a midibox via sysex. non-string data is sent back via the same protocol. i actually am able to query, listen to, and control anything i want. any events triggered by mouse or by the midibox is automatically reported (if you want it reported) back, so live is slaved to the midibox and the midibox is slaved to live.

it works on a "tier" system (can't think of a better name) that specifies a category of you are controlling (master, track, return), what aspect you are controlling (play button, track device, clip, etc), specifically what to control (device parameter, clip loop, etc) and how to control it (increment/decrement w/scale value, on/off, toggle, etc), all wrapped into easy functions like setTrackVolume(increment, scale value).

doing it this way gives me access to 128 parameters on up to 128 devices per track.

crazy man, makes sense. then your interface into Live is LiveAPI?

the tier system makes sense, then it's just a matter of bit mask logic in the micro.

"Obsession is a great substitute for talent." - Steve Martin on learning the banjo