yeah ive been searching and looking at other patches, wracking my brain. what i think im going for is a way to make a patch that uses one of live's midi preferances (where you select control sdurfaces) that way it work much like a midi controler. the only way ive seen iot done and used in the past is with midi remote scripts (liveOSC, pages, apc, livid, etc) so we may be poking in the wrong direction. as of right now we have faders, but they are on a midi track in live going to..... where? a plugin? a vst? thats not what we want. we want live to pick up the midi and recognize and ultimatly assign the CC or note to a part of live's API. You feel what im sayin?
if we were able to get the midi oput dropdown menu to pick up things like "Network 1"(OSX native midiu over tcp/ip", IAC midi driver (like in pages and liveOSC), or even Max 1 (max/msp's dedicated midi i/o socket.... because currently the only shit that get discovered is other .amxd plugins. Why is that? @elquinto or @tehn or @RABID is there a breif explanation of this behavior?