MacMusic.org  |  PcMusic.org  |  440Software  |  440Forums.com  |  440Tv  |  Zicos.com  |  AudioLexic.org
Loading... visiteurs connectés
Bienvenue invité
> Kind Of Stumped
mortalengines
posté mar. 19 déc. 2006, 08:06
Message #1


Advanced Member
*****

Groupe : Members
Messages : 479
Inscrit : 08 mai 05
Lieu : Portland - US
Membre 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?
Go to the top of the page
 
+Quote Post
 
Start new topic
Réponse(s)
fishboisfo
posté mer. 20 déc. 2006, 17:02
Message #2


Member
**

Groupe : Members
Messages : 56
Inscrit : 10 juil. 05
Lieu : San Francisco - US
Membre 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 !!
Go to the top of the page
 
+Quote Post



Reply to this topicStart new topic
2 utilisateur(s) sur ce sujet (2 invité(s) et 0 utilisateur(s) anonyme(s))
0 membre(s) :

 

Version bas débit - dimanche 1 déc. 2024, 02:28
- © MacMusic 1997-2008