Lemur users using LiveOSC "ClipLauncher"

Discuss music production with Ableton Live.
Post Reply
andreasfr
Posts: 6
Joined: Thu Jun 22, 2006 11:44 am
Location: CPH, Denmark

Lemur users using LiveOSC "ClipLauncher"

Post by andreasfr » Thu Oct 01, 2009 3:13 pm

Hi there.

While I'm eagerly awaiting Max for Live, there are some alternatives to getting some of the same awesomeness without buying the standard MAX/MSP just two weeks before Ableton goes public beta with M4L (hint, hint :wink: Come on Abes, you can do it!)
One of these alternatives is something the JazzMutant community put together using the LiveOSC python-script (forgive me if I'm wrong on the details).
I've installed the "ClipLauncher" and it seems to work great! Now I get clip names and their color on a scrollable and scaleable matrix up on the Lemur. Oh goodie..
HOWEVER after a successful installation and happy jamming away for hours, I close my live-set and computer.
Now when I restart my computer and open Live (8.0.5) it crashes and displaying "Memory corruption detected. Error (0x5e)".
I can only get things working again by deleting Live and reinstall it. It doesn't help to simply remove the LiveOSC python-script from within the app.
Can anybody tell me what's going on or how to help the problem?

I'm using:
MacBook with OSX 10.5.8, 3GB RAM, Live 8.0.5, MOTU Ultralite, Elektron TM-1.

(also no word from Ableton tech-support yet)

Hope you can help..

Regards,
Andreas

drewbixcube
Posts: 298
Joined: Sat Sep 02, 2006 2:37 am

Re: Lemur users using LiveOSC "ClipLauncher"

Post by drewbixcube » Thu Oct 08, 2009 11:23 pm

Has support gotten back to you yet? I've recently come across this error message as well, using TouchOSC... It's a pain to have to reinstall... ah well. Such is the consequence for using outside scripts, I guess.

Cheers

andreasfr
Posts: 6
Joined: Thu Jun 22, 2006 11:44 am
Location: CPH, Denmark

Re: Lemur users using LiveOSC "ClipLauncher"

Post by andreasfr » Fri Oct 09, 2009 12:42 am

Yeah support got back and was quite cool and tried to help, but basically they couldn't say what caused the error and hence couldn't tell me how to fix it.
BUT I recently wiped my harddrive to make a clean snow leopard install and that seemed to take care of the "memory corruption" error. I don't know why. But I've installed the script now and everything is running smoothly.
Making a clean install of your whole OS might be too big a hassle for a problem of this size, but having a Lemur and firing clips cooler than the APC is reeeaally nice. 8)

Cheers

Post Reply