Danjel van Tijn

I am trying to make use of the liveapi python scripts to communicate with ableton live via max.

I go the liveapi pythons scripts from here:

http://liveapi.googlecode.com/svn/trunk/src/

I downloaded the max/python stuff from here: 

But it did not include the actual py.mxe externals so I had to download that from a beta directory.

When I ran the example patch it said that python24.dll was missing. I searched for the dll and then put it in my windows/systems32 directory and then the test patch worked.

Now I am stuck :P Maybe it is just my lack of understanding of how this all works together. I guess I should have abelton live running first, then my max patch? Which python script do I load into the pyext object? How do I actually use it?

I want to do stuff like get list of current clip/scene/track names, clip status, etc. This is all for interfacing to a midi controller I am building.

I think there are a few other people trying to do this so if anyone was willing to put together a quick step-by-step or simple tutorial it would be super useful.

I go the liveapi pythons scripts from here:
http://liveapi.googlecode.com/svn/trunk/src/

I downloaded the max/python stuff from here: http://grrrr.org/ext/py
But it did not include the actual py.mxe externals so I had to download that from a beta directory.

I want to do stuff like get list of current clip/scene/track names, clip status, etc.  This is all for interfacing to a midi controller I am building.

maxmsppythonableton-live-totally-lost

So I think I am getting a better idea now thanks to another thread:

https://cycling74.com/forums/index.php?t=msg&goto=107132&rid=0&srch=liveapi#msg_107132

I guess I still use a pyext object to load one of the LiveOSC python scripts (which one or do I do several?)

http://liveapi.googlecode.com/svn/trunk/src/LiveOSC/

Looks to me like the different scripts are calling each other via "import" just like includes for C code. If this is the case, I just need to understand a bit more about how python manages the different files. I think some from this directory are needed too:

http://liveapi.googlecode.com/svn/trunk/src/_LiveAPICore/

Then I set up a udpsend and udpreceive object so that I can send the python messages and receive them (and callbacks).

Leopold Frey demonstrated with a simple patch the way to form the messages to send to live:

This link shows all the OSC messages available for control in live:

http://liveapi.googlecode.com/svn/trunk/src/LiveOSC/OSCAPI.txt

Looks like there are some useful things for me such as receiving track/scene/clip names. I can also see how it is easy to use this to form some type of automapping of core parameters.

I guess I still use a pyext object to load one of the LiveOSC python scripts (which one or do I do several?)
http://liveapi.googlecode.com/svn/trunk/src/LiveOSC/

Looks to me like the different scripts are calling each other via "import" just like includes for C code. If this is the case, I just need to understand a bit more about how python manages the different files. I think some from this directory are needed too:
http://liveapi.googlecode.com/svn/trunk/src/_LiveAPICore/

This link shows all the OSC messages available for control in live:
http://liveapi.googlecode.com/svn/trunk/src/LiveOSC/OSCAPI.txt

Looks like there are some useful things for me such as receiving  track/scene/clip names. I can also see how it is easy to use this to form some type of automapping of core parameters.


At 4:59 PM -0700 12/18/07, Danjel van Tijn wrote:

>So I think I am getting a better idea now thanks to another thread:

Yes, glad you found that all old thread Danjel - keep up the work, 

I'm sure important and useful things will come of it. Personally I 

got sidetracked from my initial playing around, and never got the 

202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X / Major 

At 4:59 PM -0700 12/18/07, Danjel van Tijn wrote:
>So I think I am getting a better idea now thanks to another thread:
>
>https://cycling74.com/forums/index.php?t=msg&goto=107132&rid=0&srch=liveapi#msg_107132

Yes, glad you found that all old thread Danjel - keep up the work, 
I'm sure important and useful things will come of it.  Personally I 
got sidetracked from my initial playing around, and never got the 
time again to look at it...

Dan
-- 
Dan Nigrin
Defective Records
202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X / Major 
Malfunction
http://www.defectiverecords.com
http://www.jackosx.com


Actually I have gotten some good info from the ableton live forums:

http://www.ableton.com/forum/viewtopic.php?p=603351#603351

Sounds like the project was abandoned due to the instability, weird configurations and cpu hogging.

I guess I might have to wait until Live finally natively supports OSC.

Also, whatever happened to the Ableton+Cycling74 project??

Sounds like the project was abandoned due to the instability, weird configurations and cpu hogging. 

I guess I might have to wait until Live finally natively supports OSC. 

Maxmsp+python+ableton live = totally lost