 Kind Of Stumped |
 Tue 19 Dec 2006, 08:06
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
|
Wed 20 Dec 2006, 07:09
Post
#2
|
|
 Rookie Group: Members Posts: 48 Joined: 13-Nov 05 From: League City - US Member No.: 72,457 |
The internal audio card should not within itself tax the CPU excessively. There are several factors that you may want to peak at. Start by looking at your free ram space, sample rates, clock speed, and of course, your buffer settings (lower buffer settings, the more CPU consumption). May not be able to run low buffer setting on the internal card (dependent on track count). Unless I am wrong, remember most laptop processers HD's only spin at 5400 rpm's. I know I am probably preaching to the chior, and probably not telling you anything you do not already know and/or have tried. Make sure there are no other CPU hog consuming applications buried and running in the background. I know these are simple, and, no doubt, areas you've already investigated, but these simple things have caused me much grief during live performances.
I am not for sure what all you are pushing through your laptop, but if you are midiing or running plug-ins (i.e, vst's, UA,) and using the keyboard as midi controller, these can casue major over-loads. Especially if you are running heavy hog-sucking applications (i.e., volume pedals, sustain pedals, or polyphony chordal structures). These components many times will crash my Mac laptop, but will minimally hit my Mac desktop CPU. Keep in mind, essentially, when when you use the FW interface, it is mainly responsible and dedicated only for converting the audio/digital signal. That's it. The Mother Board, PCI, PCIe, and RAM handles the rest of the processes. I hope you find the solution to your problem. Our band routinely uses sequencing with live performances, so I know exactly how frustrating it can be when you have these glitches in performance. Good Luck! Merry Christmas!!! Allen |
|
|
|
Posts in this topic
mortalengines Kind Of Stumped Tue 19 Dec 2006, 08:06
fishboisfo Try a couple of things -- update to 10.4.8 -- Live... Wed 20 Dec 2006, 17:02 mortalengines Thanks guys I will try all of the above...BTW as f... Thu 21 Dec 2006, 08:11
lancet QUOTE (mortalengines @ Thu 21 Dec 2006, 03... Thu 21 Dec 2006, 11:38 mortalengines So that means that the transition from 10.3 to 10.... Fri 22 Dec 2006, 06:33 lancet QUOTE (mortalengines @ Fri 22 Dec 2006, 01... Wed 3 Jan 2007, 12:32 mortalengines Here's an interesting footnote to all of this.... Thu 4 Jan 2007, 06:04 lancet QUOTE (mortalengines @ Thu 4 Jan 2007, 01... Thu 4 Jan 2007, 13:15 oatylove im not a rocket scientist, I wouldnt up grade caus... Wed 3 Jan 2007, 06:21 aportman I am personally sick and tired of forced up-grades... Thu 4 Jan 2007, 07:05 |
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:
