2PacIsAlive / liveapi

Automatically exported from code.google.com/p/liveapi
GNU Lesser General Public License v2.1
0 stars 0 forks source link

LiveAPI doesn't work on OSX #4

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
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 nikolaus...@googlemail.com on 18 Apr 2008 at 10:31

GoogleCodeExporter commented 9 years ago
yes, it would be quite interesting to know what the issue is here. i remember 
the liveapi.org site had some 
discussion of this but since the site is now offline i cannot seem to recall 
what the problem was...

Original comment by jeanpie...@gmail.com on 1 May 2008 at 10:59

GoogleCodeExporter commented 9 years ago
and unfortunately archive.org doesn't seem to have much of the old liveapi.org 
site indexed

Original comment by jeanpie...@gmail.com on 2 May 2008 at 5:56

GoogleCodeExporter commented 9 years ago
The development for OSX seems to be stuck. The error above - as I understand it 
- is because the python that 
Live uses doesn't know sockets. There is a file called LiveApiOSX and they seem 
to try to get aroung that, but it is 
still not working here.

Any help would be appreciated very much.

Original comment by nikolaus...@googlemail.com on 27 May 2008 at 10:14

GoogleCodeExporter commented 9 years ago
I couldn't get LiveOSC to work on 6.0.10, 7.0.3, or 7.0.7 mac. However, I did 
get
APIMidi (http://www.assembla.com/wiki/show/live-api) working without any 
difficulty.
A MIDI interface is obviously not as flexible as OSC, but you can still access 
all of
the API bits.

My own project has hundreds of clips per column so the API as uploaded won't 
work;
however, I've already been successful hacking the python a bit to use CC values 
as
part of the clip selection.

E.g.:
CC #1 value 0 = clip 1
CC #1 value 127 = clip 128
CC #2 value 1 = clip 129

Mike

Original comment by mklaure...@gmail.com on 14 Jul 2008 at 2:35

GoogleCodeExporter commented 9 years ago
hello Mike,

I am very interested in your modifications

Original comment by oliviers...@gmail.com on 27 Jul 2008 at 10:36

GoogleCodeExporter commented 9 years ago
would you like to share this custom version ?

thanks a lot

Original comment by oliviers...@gmail.com on 27 Jul 2008 at 10:38