![]() |
![]()
Post
#1
|
|
![]() Advanced Member ![]() ![]() ![]() ![]() ![]() Group: Members Posts: 479 Joined: 08-May 05 From: Portland - US Member No.: 65,373 ![]() |
I have a powerbook G4 with 1.5ghz processor, 1.25 gig of Ram & OSX 10.3.9 with Ableton Live 5.2.2 & I was playing live the other day & not using my Firwire Interface as an output (instead opting for the "built in audio" option with a 1/8" adapter to RCA outs into a mixer) & on one song I started getting serious CPU overload at 62% & by that I mean audio cutout/stutter/slowdown....very ugly. This hadn't happened earlier in my home studio with the FW interface hooked up & it didn't happen when I got back home either (with the FW hooked up once again). Does using the built in audio really tax the CPU that much? Anyone else ever experience this? What was the solution?
|
|
|
![]() |
Replies
![]()
Post
#2
|
|
![]() Member ![]() ![]() Group: Members Posts: 56 Joined: 10-Jul 05 From: San Francisco - US Member No.: 67,641 ![]() |
Try a couple of things -- update to 10.4.8 -- Live 5.2, i believe, to have been optimized for panther. An even easier solution is keep track count low, and check your plug ins-- especially reverbs -- as they eat CPU. Lots of things can happen in a live performance -- hope this helps. Streamlining the locations of your samples, etc, or even the need to get a peripheral firewire interface for travel maybe one of many solutions. Contact Apple rather than Ableton, as this would seem more of a hardware than software issue. Good Luck !!
|
|
|
Posts in this topic


























![]() ![]() |
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
