2pacisalive/liveapi

Automatically exported from code.google.com/p/liveapi

liveapi's Issues

LiveAPI doesn't work on OSX

I can't get LiveAPI to work on OSX. I read that it is possible, but....

What I did:
Downloaded LiveAPI, put the _LiveAPICore and LiveOSC folders in the MIDI Remote 
Scripts folder.
Started Live.
__init.pyc__ is created, LiveOSC is created, when it comes to 
LiveOSCCallbacks.pyc, it stops.

So I started debugging. I logged the stderr and stdout and got the following 
error msg:
"No module named socket."

So I tried "import socket" in the python console, worked fine. Maybe the socket 
include file is not in 
the search path?

Original issue reported on code.google.com by [email protected] on 18 Apr 2008 at 10:31

Runtime error Microsoft Visual C++ Runtime Library

What steps will reproduce the problem?
1. Copy the four LiveAPI modules into the Resources\MIDI Remote Scripts 
folder
2. Startup Live (tried with 6.0.10 and 7.0.1)
3. An error message pops up:

---------------------------
Microsoft Visual C++ Runtime Library
---------------------------
Runtime Error!

Program: ...s\Ableton Live\Ableton\Live 7.0.1\Program\Live 7.0.1.exe



This application has requested the Runtime to terminate it in an unusual 
way.
Please contact the application's support team for more information.


---------------------------
OK   
---------------------------

I'm on XP SP2. Should I install something else?

Cheers, ff

Original issue reported on code.google.com by [email protected] on 14 Dec 2007 at 6:01

mixer_device calls don't always update in Live

> What steps will reproduce the problem?

send "panning" or "send" messages to LiveOSC over OSC.

> What is the expected output? What do you see instead?

I expect these messages to update the corresponding control in Live 
everytime. Instead, it seems to update roughly one-in-three times.   I've 
verified that it isn't my OSC messages with the following test:

in LiveOSCCallbacks.py playClipCB:

...
LiveUtils.launchClip(track, clip)
LiveUtils.launchClip(track+1, clip)
...
the above works everytime, whereas:

...
LiveUtils.launchClip(track, clip)
getTrack(track).mixer_device.volume.value = 0.5
...
seems to work one-in-three times, as does reversing the above two lines, 
at which point the launchClip is also inconsistant. 

Therefore my preminition is that that mixer_device is a slow call and Live 
is 'timing out' (?)  but I dream of better behavior / hope I've just 
screwed something up or am missing something.  

The conceptual part I don't get is that I assume a MIDI controller would 
be able to update live on such a message sent from e.g. a MIDI switch.  

> What version of the product are you using? On what operating system?

Live 6.0.10, Live 7.01

Please provide any additional information below.

I'm looking for information, I missed out on the LiveOSC website when it 
was around.  I'm curious if:

-this is a known issue / something that others have experienced 
-what the best workaround is, if any.

Perhaps I need to create some sort of listener, and verify this control 
changed, and if not send the message again.?

Original issue reported on code.google.com by [email protected] on 9 Jan 2008 at 5:08

LiveOSC not responding

What steps will reproduce the problem?
1. Copy _LiveAPICore and LiveOSC to the correct folder
2. Start Live
3. Select Control Surface "LiveOSC"
4. Run the sample "simple_osc_client" (I have Python 2.2.2 installed)

What is the expected output? What do you see instead?

I expected the tempo to be set at 80. However, nothing happens.

Also, using Sysinternals Process Explorer, I see no network activity 
whatsoever in live's threads.

What version of the product are you using? On what operating system?

Live 7.0.1, XP SP2

Original issue reported on code.google.com by [email protected] on 14 Dec 2007 at 6:56