Who wants access to Ableton's Python API? .. You? .. Ok!

[ST8]

Strange. Downloaded the latest ZIP, and it is working again. Let's see for how long.

Its best to keep track of whats going on on the monome forum. I do break things from commit to commit
http://post.monome.org/comments.php?DiscussionID=4607

[nbinder]

Okay... as I don't have an account there (yet), here is a huge bug:

If you set the loop start/end and the clip is not playing, it will set the start and end OF THE CLIP instead of the loop brace.

[carrieres]

hi,
is this a dead project ?
it seems that the links on the first page has changed to http://code.google.com/p/liveapi/
there is no news since a lot of time
best regards

[julienb]

it was about access by hacking scripts, now Ableton support the Official Live API through Max for Live.

just read that: http://www.ableton.com/extend

[carrieres]

can i still use it with ableton live 7 or 8 ?
thanks

[julienb]

it works til 7.0.15, if I remember correctly.
after that, there are some modifications to do.

but you should consider live 8 + max for live that provide a nice way to hack everything you want with the pretty high-level graphical language of Max!

[carrieres]

but there is no python ...

[julienb]

I guess you can wrap python to Max if you really love python.
but you wouldn't need python to control live with Max for live...

[yannxou]

Hi, anybody still using the LiveOSC python script?

I cannot succeed getting the clip.color property and it always returns 0..

[julienb]

max for live is supported, this python side doesn't seem to be... so I really advice you to use max for live & javascript.. it is VERY fast.

[ST8]

The project is not quite dead ive just not been able to get the original repositories updated to link to the latest versions.

A current working LiveOSC for mac (Live 8 upwards) and windows (Live 7 upwards) can be found at:
http://monome.q3f.org/wiki/LiveOSC

I'm running on mac with Live 8.1.3. It supports listeners which means you dont need to poll for clip status / device parameters / etc /etc. See the above link for everything thats implemented.

@yannxou
i'll try and check that out tonight and see whats wrong.

[3phase]

The project is not quite dead ive just not been able to get the original repositories updated to link to the latest versions.

A current working LiveOSC for mac (Live 8 upwards) and windows (Live 7 upwards) can be found at:
http://monome.q3f.org/wiki/LiveOSC

I'm running on mac with Live 8.1.3. It supports listeners which means you dont need to poll for clip status / device parameters / etc /etc. See the above link for everything thats implemented.

@yannxou
i'll try and check that out tonight and see whats wrong.

Live 8.13?? the stable version for special users?

[LoopStationZebra]

Live 8.13?? the stable version for special users?

lol. Yes. Well, actually, we all have it except YOU.

[ST8]

oops, must be 8.1.2

[yannxou]

@ST8: Thanks, I'll keep checking for updates in liveOSC. After evaluating both Python and Max4Live (even with javascript) I prefer the Python alternative which I feel more like a real programming environment.

I don't know which method has better performance but if you just want to communicate with Live to build a new interface, I see some advantages of Python over Max4Live:
1. Users do not need a licence for Max4Live.
2. Once the Python script is configured as a control surface it works for all projects and there's no need to load a Max4Live patch every time.

One thing I don't really feel comfortable though, is how the callbacks are implemented, but that's a problem of Live itself I guess. For example, I'd like to see a global callback for clips like 'clipChanged(int track, int scene, int property)' instead of needing to add a callback for each property on each clip which forces the need to rescan all clips and add/remove new callbacks to newly added/removed clips each time a track/scene is added/deleted...