Runtime error Microsoft Visual C++ Runtime Library

[GoogleCodeExporter]

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 freakf...@gmail.com on 14 Dec 2007 at 6:01

[GoogleCodeExporter]

Added:
It seems to happen only with the LiveTelnet module.
I also get a stderr.txt on my desktop then. I've attached the file.

Live uses MSVCR71.dll version 7.10.6030.0 from Microsoft® Visual Studio .NET.

Original comment by freakf...@gmail.com on 14 Dec 2007 at 6:31

Attachments:

• stderr.txt
• stdout.txt

[GoogleCodeExporter]

I'll take a look at what's needed to get this working with a modern version of 
Live.

Original comment by cramitn...@gmail.com on 31 Dec 2007 at 6:59

[GoogleCodeExporter]

hello,

any ideas?

I have the same problem with live 7.0.1

Original comment by julien.bayle on 10 Jan 2008 at 5:44

[GoogleCodeExporter]

it occurs if you raise an Exception in the body of your module...
I can't figure why but importing inspect raises, even with a correct sys.path

Original comment by dee...@gmail.com on 15 Jan 2008 at 12:11

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

OK i have figured from a debug script that it was not able to find the module
_LiveAPIcore, and so generated the runtime c error.

now there are a few references to this in the liveosc and livetelnet 
directories as -

from _LiveAPIcore import *
# and this
from _LiveAPIcore import LiveUtils

the thing that gets me is _LiveAPIcore is a directory, not a module.  so how 
can you
import from a directory as if it were a module?  have i simply put the 
_LiveAPIcore
folder in the wrong place?  where is it supposed to be?

i can see that if i wanted to, i couuld replace all the references to the
_LiveAPIcore module in each other moduile with an absolute path instead, but it
obviously wasn't designed like that.  thanks again for any help.

Original comment by queg...@gmail.com on 4 Feb 2008 at 10:52

[GoogleCodeExporter]

the question over where _LiveAPIcore is supposed to go may seem stupid, but im 
pretty
sure it isn't covered in the installation documentation.

Original comment by queg...@gmail.com on 4 Feb 2008 at 10:59

[GoogleCodeExporter]

hehe, its funny i just found this document -
if you look at packages-
http://docs.python.org/tut/node8.html#SECTION008400000000000000000

but the thing is it will only treat whole directories as modules per se if they 
have
a __init__.pyc file in them, and the _LiveAPICore doesn't have this file. i 
know i
can just create it, but i wonder if this was what was intended.

so i went ahead and tried it anyway, and added the _LiveAPICore directory to the
python22/lib folder as this is a system path.

the good news is the crashing disapeared. but i still get this error log 
generated,
which is a new set of problems (see attached)-

i wonder if i did what you are supposed to with the _LiveAPICore directory

Original comment by queg...@gmail.com on 4 Feb 2008 at 11:25

Attachments:

• stderrT.txt

[GoogleCodeExporter]

where ever i found

from _LiveAPICore import *

i replaced it with this

from _LiveAPICore import RemixNet
from _LiveAPICore import OSC
from _LiveAPICore import LiveUtils

i also replaced the ip adress in the liveosc.py file with my own ip.

if there is a better way to do this let me know.  im sure i have overlooked 
something.

i can now send osc messages to ableton and can succesfuly rename clips, fire 
them off
and do whatever.
i can also retrieve some osc messages in max/msp, however it only seems to work 
when
integers or floats are sent.

Original comment by queg...@gmail.com on 4 Feb 2008 at 12:39

[GoogleCodeExporter]

Hey queglay, congrats!

Good that someone finally managed to fix this.
In the meantime, I've chosen not to go for the liveApi route, because of the 
(known 
and documented) timing restrictions. If the Ableton guys ever make it possible 
to 
control Live on a per-audio-sample level, it would be a great app (with liveApi 
or 
with their own Api). Sample accuracy is what I need for predictable 
looping/timing 
of live sounds...

Good luck!

Original comment by freakf...@gmail.com on 4 Feb 2008 at 1:22

[GoogleCodeExporter]

could you possibly get the path to the bounced file from ableton and direct 
max/msp
to it?  then you could do whatever you wanted in that department.

in terms of clip firing, the limitations are only with osc.  you could still 
get the
api to handle midi mapping and use midi for triggering couldn't you?

Original comment by queg...@gmail.com on 4 Feb 2008 at 10:30

[GoogleCodeExporter]

ok, you need to add this file to the _liveapicore directory.

then any import and * references will work.

Original comment by queg...@gmail.com on 4 Feb 2008 at 10:34

Attachments:

• init.py

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

the __init_.py worked great for me in Live 6.0.10

Amazing!

Original comment by rin...@gmail.com on 6 May 2008 at 9:32

[GoogleCodeExporter]

Yeah it seems like that this __init_.py has just solved the issues here. Now it 
works
fine under Ableton 7 also!

Thanks.

Original comment by dam...@gmail.com on 15 May 2008 at 2:09

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I saved __init__.py and imported into the directory, but when I attempt to open 
Ableton 7.0.3, I still get the 
runtime error.

Original comment by rithwik....@gmail.com on 19 May 2008 at 12:45