Ableton Forum

Live 3.03 crashes DP4.12 when you hit start/stop from Live with Live as rewire slave. If you open Live 3.03 in DP as slave, and do all of the starting and stopping from DP, there's no problem. But as soon as you click over into Live and hit start, it will not stop, and there's no sound, and the only thing you can do to stop it is to quit Live, and then DP says it has to quit also, and it sure does just exactly that.

I'm in OS 10.2.6 on a 1gig G4 tower, mirror door, 1.5g RAM

actually, the correct error message i'm getting from DP is: The application Digital Performer has unexpectedly quit.

just so you know...

When running Live 3.03 in Rewire mode with Digital Performer 4.12 (OS 10.3) or Digital Permormer 3.11 (OS9.2.2) there is a system freeze when switching to the Live transport controls from the Digital Performer Transport controls. Also, system freezes after recording tracks into Digital Performer. I am runnning tests on an Mac G4 MDD Dual 1.25 750 megs of Ram. Interestingly I have a client who runs the same set up on a single Processor AGP Mac and DP 3.12 with Live 3.03 and there are no problems with the transport switching (still has the record problem)

I am an audio specialist and am setting up a system for a film composer client who wants to use this program, but we cannot move forward with the purchase until these issues are resolved. Would it be advisable to run Ableton Live 3.03 on a spearate PC with Windows XP slaving to Midi-beats from DP instead of Rewire? Does Live perform better on the Windows OS platform?

Any assistacne would be much appreciated

I think it was this forum where I read that Live DOES run better on Windows currently, unfortunately for Mac users. Apparently it's an issue with the Velocity engine in Mac OS X not being fully utilized, but don't quote me on that. You should keep doing a little more research, and hopefully someone will reply to this thread who knows for sure.

/sherman

This problem is still occuring, seems to be an issue with Live, not Digital Performer.

OUt of nowhere, this problem seems to have corrected itself, not sure how, but I'm not having this issue any more, (at this time). I wish I knew how it was fixed...