M4L control is a collection of M4L apps and abstractions designed to help anyone create their ideal set-up in Ableton Live, using whatever hardware devices they have available.
The idea is that you drop in one M4L device, named M4L Control Hub, which queries the Max 4 Live API for the IDs of all objects within the set, and stores them within appropriately named Coll and Value objects accessible to any other M4L device. The device then uses these IDs to set up appropriately named Send, Receive and Value objects for every major function and value within the Live API.
There is also a collection of satellite apps which communicate with the M4L Control Hub and set-up individual controls and configurations on your hardware device. For instance M4L Device Control, an app which allows you to set the Appointed Device, this is the highlighted device or device with the blue hand, and then control it using 8 macros.
In the pipeline there is also a Clip Launcher, Mixer, new version of Live Clip Chopper and a Midi Input Device for Drum Racks and the like.
Although so far apps can only be controlled by Midi Mapping or the monome, the plan is to develop a mapping device which allows the user to plug in any Midi, OSC or HID device and be able to map any of the controls to any of the functions within the Live API.
This will also allow users to create custom apps for the monome using a few buttons for functions from the Live Mixer, some to control a Live Device, some to Launch Clips and some to Chop Clips. These configurations can then be saved with the live set, but also stored as presets and dropped into any new set.
Although this is still some way off I have abstracted out as much of the code as possible along the way, providing small functionally concise and well commented chunks of code which can easily be edited to create any set-up you'd like, providing you've got a little bit of max experience or are willing to learn.
So as I've finally got a stable base to start building the Clip Launcher and other apps on top of I thought I'd release the main M4L Control Hub device with all of its abstractions. Hopefully it'll prove useful for creating any other device you'd like using the Live API or for learning about it and exploring it.
I've also included the first device I've built with it: M4L Device Control, and a version for the monome.
This app maps the first 8 macros of the Selected Device to faders on the first 8 columns of the monome. For the moment the other functions are midi mappable, however I'm planning a function row with lots of extra goodies, pattern recorders, storing a few device ids to recall quickly without moving around the tracks etc.
To get this to work drop the M4L Control Hub onto any track, then drop either the M4L Device Control or M4L Device Control Monome Patch onto any track.
Click Go on the M4L Control Hub patch to start everything.
If using the monome patch then click the Connect Button.Download here:http://post.monome.org/?PostBackAction= ... entID=3439