Why is my Disk I/O spiking so bad?
?????????
Logic Pro, Mac OS X (10.6.8)
?????????
Logic Pro, Mac OS X (10.6.8)
That's simply the way it works.... it's not like the CPU meter, it just shows that your disk is being accessed.
It will even peg and stay there as it's pulling data for several tracks.
pancenter-
It spikes bad though...im talking going from no reading to 100% reading...it was bad enough to make logic crash yesterday while i was trying to record an artist...
should i just un install and then reinstall logic or what should i do?
What Mac are you using?
How much RAM do you have on Board?
How much buffer are you using in Logic Pro?
There are several different reasons why Logic may spike the CPU meters. It will require some details to give you an educated answer.
I can say that on my Mac Pro 2.8ghz 8-Core with 16 Gigs of RAM, I've never seen any spikes and I can do a boat load of tracks.
MM, it's spiking his Disk Meter, at least that's what I thought he meant.
Im using a MacBook Pro 17 inch
8GB of RAM @7200 rpm with 500 gb of HD space
Its an i7 model at 2.3GHZ with the turbo reaching 3.2 GHZ and its the newer 2011 model. At the moment i am recording directly to my Macs hd because i cant afford an external hd. My buffer is set to 256.
I understand that logic will utilize the cores...and lately its only been using six instead of all 8... but my main issue is why my HD I/O meter in logic spikes so badly. Bad enough to freeze logic in the middle of a recording. I mentioned in a previous post that ANY TIME audio is introduced into a project it spikes badly when playing/recording. Im also seeing the spikes in Activity Monitor. Again ive never had this problem until the newest update (Logic Pro 9.1.5).
I just took the computer into the apple store and after running all the diagnostics they could they said my computer was fine...I use an Apogee Duet 2 Usb audio interface but that is not causing the spikes because with/without it pluuged in the HD I/O meter still spikes. So they Apple Geniuses said it might be a problem with Logic Itself or i may need to re-instsall the OSX. But none of them really had great Logic experience so im counting on you guys
Your right its spiking my disk meter not my cpu core meters. Its also happened if i was closing safari switching back to logic my disk i/o would spike
And how is this 'spiking' a problem? Does Logic stop on every spike? Or crash? Or crackle 'n pop? Or are they just higher than average peaks in the HD activity meter?
Spiking itself is not a problem, as long as nothing overloads. And when it overloads, read this first:
Well it shut down the other day...after recording for maybe 3 minutes. Its just recently started spiking...going into the red then subsiding...then going back into the red. Ive never had this happen before which is my main concern. Even with one audio file the computer HD I/O meter will spike...
Ignore the disk I/O meter - it is going to "spike" all the time and is not indicative of a problem. That's just the way it is. If Logic is freezing/crashing, you have a more serious problem that is most likely caused by a plugin - Logic in itself is quite good about crashing "gracefully" when overloaded (for example popping a dialog and asking if you want to save your work before it falls over when running out of memory).
If you examine the crash log, you should get an idea of what's causing your problems. If you're not sure how to read the crash log, post it here and someone will take a look.
How do i get to the crash log in Logic? Thanks for all your help guys
And it just started happening recently which is why i was concerned in the first place...and ive been using logic for almost seven months now (switching from ProTools)
When Logic crashes, you should see a dialog on the screen saying "Logic has unexpectedly quit" and it will show you the crash log. If the entire machine freezes and you have to force a restart, you should see a similar dialog appear when it boots up again.
~/Library/Logs/DiagnosticReports/
Look for the latest Logic report.
//Dan
Why is my Disk I/O spiking so bad?