you might check to make sure Live is not running via Rosetta (get info on the live application in the finder and make sure the checkbox is not selected but a crashlog would probably be the most telling. in your user home folder > Library > Logs > CrashReporter > Live_(DATE)_(COMPUTER-NAME).crash.cdeustaquio wrote:I seem to be having the same problem.
(...)
Any suggestions??
Mac book pro crashing with Live 6
-
jean_pierre
- Posts: 38
- Joined: Thu Oct 25, 2007 5:20 am
-
jean_pierre
- Posts: 38
- Joined: Thu Oct 25, 2007 5:20 am
thanks for the tip.
activitiy monitor says: cpu: 120, threads 8 , real memory 134 mb, virtual memory 1,08 mb for the process live when i am triggering 5 voices of the minimonsta plugin as vst plugin in live twice (10 voices together).
in logic i can get at least 40 voices of the same plugin with the same sound.
activitiy monitor says: cpu: 120, threads 8 , real memory 134 mb, virtual memory 1,08 mb for the process live when i am triggering 5 voices of the minimonsta plugin as vst plugin in live twice (10 voices together).
in logic i can get at least 40 voices of the same plugin with the same sound.
-
jean_pierre
- Posts: 38
- Joined: Thu Oct 25, 2007 5:20 am
that is odd, it seems as though something isn't quite right here.spielor wrote:activitiy monitor says: cpu: 120, threads 8 , real memory 134 mb, virtual memory 1,08 mb for the process live when i am triggering 5 voices of the minimonsta plugin as vst plugin in live twice (10 voices together).(...)
in activity monitor do you see that other applications are taking a lot of CPU or memory? you should be able to sort the processes by CPU or Real Memory and get a good feel for the processes on your machine and what they are doing.
how much RAM does your machine have in total? is your machine actually crashing or is it just acting sluggish? how much CPU does Live report using (in live and in the activity monitor) when triggering the 5 voices twice? and you've checked to make sure rosetta isn't enabled right... hmm
-
grimmwerks
- Posts: 9
- Joined: Wed Oct 13, 2004 11:26 pm
-
jean_pierre
- Posts: 38
- Joined: Thu Oct 25, 2007 5:20 am
yeah, in your particular case it sounds like an issue with the melodyne bridge on leopard, the celemony forum has the details on how to resolve: MelodyneBridge and ReWiregrimmwerks wrote:Mine is crashing but it's leopard - it was working great last week and now it's just dying completely.
apart from ableton are the applications fine and the second highest is the activity monitor itself (and it is very low).
the laptop has 2 gig ram. Live doesnt crash but starts acting a bit slow and the adio is distorted with dropouts.
rosetta is not enabled. the activity monitor says something about 110 percent cpu and live between 70 and 100 (cpu meter jumps).
i already heard from other people with this macbook that there are some problems when it comes to audioperformance with other programs than logic.
i am very disappointed because my aim was to switch to live completely not just for liveperformance. fortunately i didnt buy it until now.
maybe there will be a solution for this problem in version 7.
the laptop has 2 gig ram. Live doesnt crash but starts acting a bit slow and the adio is distorted with dropouts.
rosetta is not enabled. the activity monitor says something about 110 percent cpu and live between 70 and 100 (cpu meter jumps).
i already heard from other people with this macbook that there are some problems when it comes to audioperformance with other programs than logic.
i am very disappointed because my aim was to switch to live completely not just for liveperformance. fortunately i didnt buy it until now.
maybe there will be a solution for this problem in version 7.
-
jean_pierre
- Posts: 38
- Joined: Thu Oct 25, 2007 5:20 am
you definitely have a good amount of RAM and your 70%-110% CPU use sounds pretty high. odd though that you can 4x as many triggers in logic without running into the same problem - it might be worth contacting ableton support and see what they say, additionally you could try and get into the 7 beta pool and see if it is any better.
using the newest / most stable version of the plugin?
using the newest / most stable version of the plugin?
-
postmixformula
- Posts: 14
- Joined: Fri Jun 15, 2007 3:10 am
- Contact:
I've not long installed Leopard and am running it on a 2.16GHz MacBook Pro w 1.5GB RAM. I played a DJ gig on Sat night and it crashed mid set. Under Tiger running the same set it would perform better. There was midi lag and minor sound distortions on the main-out. Problems that I had w my old iBook. I fixed it (momentarily) by increasing the Buffer size in the preferences pane. Ultimately not good enough.
Re Rosetta: Live 6.0 is Universal Binary, by default the app should not be ticked in the information panel for Live. You may have issues if running plug-ins that are not Universal Binary in which case Rosetta would run and you would probably suffer from slow-downs and drop-outs.
Re Leopard: I think Apple have shifted the goal posts in Leopard and that there's a bit of tweakin required from Ableton to get the performance back on track.
Re Rosetta: Live 6.0 is Universal Binary, by default the app should not be ticked in the information panel for Live. You may have issues if running plug-ins that are not Universal Binary in which case Rosetta would run and you would probably suffer from slow-downs and drop-outs.
Re Leopard: I think Apple have shifted the goal posts in Leopard and that there's a bit of tweakin required from Ableton to get the performance back on track.
MacBook Pro 2.4GHz 16GB RAM | Live 9 suite | Novation Twitch | Novation ReMote SL25 | Korg padKontrol