Page 3 of 3
Posted: Mon Dec 24, 2007 3:20 pm
by Tarekith
I could care less what the Live meter says, it's when the audio drops out at the same time as the spike that I get worried. I always have MenuMeters running in OSX anyway, easier to take a quick glance and see a more accurate view of my CPU and memory useage.
Posted: Mon Dec 24, 2007 4:07 pm
by nebulae
^ Agreed completely - I've always been VERY careful about my CPU usage and been downright stingy, keeping sets at under 50% because fo the danger of dropouts. But with these spikes, even at 30% CPU usage, if I nudge the tempo by 1 bpm and then bump it again about 10 seconds later, the CPU spikes well into 80%, and then we're in the well-known danger zone. Can't have that happen in front of an audience.
Posted: Mon Dec 24, 2007 4:51 pm
by udp
Hey Neb,
I assume your working at 44.1 k samples right? If not, I'm finding I'm having troubles working at anything above 48K. So the problem may be in how Live 7 is handing higher sample rates. Can you confirm or dispose of my theory?
Posted: Mon Dec 24, 2007 5:44 pm
by nebulae
udp wrote:Hey Neb,
I assume your working at 44.1 k samples right? If not, I'm finding I'm having troubles working at anything above 48K. So the problem may be in how Live 7 is handing higher sample rates. Can you confirm or dispose of my theory?
I don't think the sample rate has too much to do with it other than the fact that the higher the sample rate, the more the CPU usage, so quite possibly, even more the CPU spike.
For my sets, I dither everything down to 16bit, 44.1khz. Watch out for frozen files because they are 32-bit and that level of fidelity is just not all that necessary in a club.
Posted: Tue Dec 25, 2007 3:33 am
by udp
There goes that theory. I just seem to be running ok at 44.1 and 48k. Well, maybe the Abes will get a fix for the CPU issue soon.
Posted: Sat Apr 19, 2008 11:39 am
by Patch
Anybody got a solution for the CPU spikes when changing tempo?