There’s a user pref folder in Preferences with mapping examples that have nothing to do with python. What are you writing about here?

Why is all this crap so freaking hard???

http://www.assembla.com/wiki/show/live-api

I got the code from that site to somewhat work with Live 7.0.12, after having changed the library paths in the __init__.py script according to what my Windows box wants to see.

Where do I download the Live API from? I thought I’d downloaded it from http://www.liveapi.org/, however this appears to be code which uses the Live API rather than the API itself. Within the code that I downloaded there is no reference to the MIDI mapping functionality (such as build_midi_map) which is exactly what I’m after for an application that I’m writing.

Also near the start of your article you mention “a hidden menu containing options to open a python console and reload scripts”. How do I access this menu?

Is there documentation for the Live API?

Cheers, JOe

To make Ableton recompile the updated python code, just select another control surface, and then get back to yours in the control surface selector.

I keep the preferences dialog box open all the time to cmd-tab to it and press up, then down arrows. It reloads the code immediately.

Also, I wanted to point that it’s a pity that your techno experiments (mp3′s) are no longer available. I would very much like to check them. I’m a techno geek myself — playing, composing and building hardware with my dad and always interested in what others do.

Our latest development is the monome-like device. The schematics is the same, but the buttons / leds, casing, rubber etc all different. I’m still programming it (updating firmware to support native blinking) and writing the Ableton control surface driver for my needs. Just to let you know…

Good luck!