Disk too slow messages

I keep on getting this message Disk too slow not able to process all data on time every 5 to 10 seconds

Hello rsmani
Check out the articles below for some troubleshooting steps for the error message that you are seeing.
Logic 9.1.4 or later: Core Audio System Overload messages
http://support.apple.com/kb/TS3834
Logic: About I/O buffer size and monitoring latency
http://support.apple.com/kb/HT1314
Thanks for using Apple Support Communities.
Regards,
-Norm G.

Similar Messages

Disk too slow

Hi there,
I am running logic express 7.2 and tried to run some audio files yesterday. Unfortunatly i cannot run them as i am getting a disk too slow message popping up. I was trying to run 18 x 24bit x 96000hz files. This doesnt strike me as excessive for this day and age. My system:
MacBook Pro, 17-inch, 2.33GHz Intel
2.33GHz Intel Core 2 Duo
3GB 667 DDR2 - 2x1GB SO-DIMMs
100GB Serial ATA drive (7200rpm)
Pls can somebody explain what the settings in core audio do? I have tried the biggest buffer and and larger disk buffer setting but no luck. I see the audio slider is rising quite high but again i would expect a machine like this to be able to handle it..
May logic 8 be able to handle this?
Also pls can you let me know how to defrag the drive on a mac?
thanks
richard

You have to consider that your internal disk is accessed by the system and the applications so it will NEVER play those 18 tracks.
If they were 16 or 24 bits at 44.1Khz you could have some chances to play them rightly.
The only solution is to have an external Firewire 400 or 800 (better) or, if you want more, an external array in stripe set 0 or 5.
About the buffer: more buffer = less CPU but more disk activity and more latency
less buffer = more CPU but less disk activity and less latency
And... Logic 8 won't help you with disk performances.
cheers
rob
rob

Newbie with "disk too slow" issues

Hi folks,
TOTAL newbie (Mac newbie, audio newbie) here, up front disclaimer. I've just been trying to play the "Numbers Game" demo project in Logic Pro on my new MacBook Pro and I'm getting the "disk too slow" message (error 10010)...This is a 2.66 GHz MacBook with 4GB of RAM. I'm just using the internal drive (500 GB, 5400 RPM)...The system is new, so it's clean.
All my software is up to date...Logic Pro is 9.1.2. The same thing happens in 32 or 64 bit mode, at the same spot in the playback (about 41 seconds in).
I've read various threads here regarding this message and have tried some of the suggestions (like disabling the Airport). I've tried both extremes (32 and 1024) on the disk buffer size, etc...
Like I said, total newbie so I'm probably doing something stupid. Has anyone else had this particular issue? I notice this demo project is rather complex...so maybe it really is overloading the system?
Thanks in advance for any suggestions.
Will

Nope, not trying to play from the optical... I'm not quite that much of a newbie.
Never hurts to ask
BTW, if you hit that spot and get the overload message, and then start playback over again from the beginning, will it play back the project without incident? If so, you've run across one of the longtime and well documented issues of Logic. Once you play through that first time around, you're good to go.
If it's doing it every time you playback the project even if you haven't closed Logic, then it is indeed bogging down your system. Fuzzy is right, you'll have better performance if you put the project and its contents on an external drive. Also, if you have a Unibody MBP, the HD's are super easy to swap out. Mine came with a 500GB 5400RPM drive, and I put in a 500GB 7200 speed drive, and it makes a HUGE difference. The original drive is in an external enclosure that I use for a back-up. It's a very nice set-up.
Good Luck!

Built in click or clicktrack? Stability? "DIsk Too Slow"

I've had a lot of issues with "disk too slow" messages while tracking through Amplitube or Waves SSL. And when I got these messages I've used the built in click/metronome (klopfgeist).
But then I started using an audio clicktrack by bouncing out klopfgeist to a seperate audio track and then using that in the project. Thus NOT using the built in click. And since then I haven't got any "disk too slow" messages.
I'm wondering if anyone else have experienced this, and if others could try this. I have now been running for half a day with several Amplitube tracks and NO "disk to slow" messages what so ever (know on wood).

Try making a clicktrack using a different instrument (any EXS24 drumset using a sidestick or rimshot-like sound, for instance), see what happens. Klopfgeist is a Software Instrument, and if it drives your system into overload, it tells me that your setup is already close to overloading anyway. However, if it is the case that the Klopfgeist Instrument is drawing more CPU than the EXS24, something isn't right with Klopfgeist.
I hardly ever use it, I just choose an appropriate (drum- or percussion-) loop to play along to.
So what do the CPU meters indicate when you run your overloading projects with Klopfgeist bypassed? Big difference?
I cannot "create" the issue because I do not have Amplitube. But if it is comparable to other Amp sims, they can be CPU hogs, depending on how heavily you use them and which parameters are active.

Error Message: Disk too slow or System Overload

hey guys
during playback i keep receiving an error message reading: Disk too slow or System Overload. I was wondering if anyone knew the cause of this?
Thanks for any info

I am sorry to hear that you are having those problems. I found this thread in the discussion board about a user having the same issues with the "Disk too slow or System Overload" error message.
Read the thread and this may actually help you to understand what is going on:
http://discussions.apple.com/thread.jspa?threadID=1456048
Also, make sure you download this update that may removed several issues with your computer and any Final Cut Studio software.
http://support.apple.com/downloads/ProKit45
Hope this information helps,
Vicente Tulliano

"Core Audio Error Disk Too Slow" On Stage?

i use logic pro on my macbook pro(2gb ram 2,16ghz) and i'm completely satisfied with this combination.
Only when i'm playing live(electro music - loud environment - lots of sub/bass etc.) i sometimes get the message disk too slow/system overload, although i'm only playing some aiff files and some softsynths to it...
is it possible that my external disk(lacie d2 FW400) is skipping due to vibrations or is my Sudden Motion Sensor stepping in? i disabled it already... anyone the same problems or even an answer
thx in advance...
Macbook Pro Mac OS X (10.4.9) 2 gb Ram

If you can afford it buy one of these http://www.sonnettech.com/product/temposataexpress34.html
and an external sata drive - sonett also make them http://www.sonnettech.com/product/fusion.html
Or any external sata drive will work if you only need the one drive. The sonett is good as it does port multiplying meaning you can have up to 10 drives running on your laptop
Although a quicker and cheaper fix could be to try putting the lacie on some neoprene. - this will cut out "most of the" bass thats transferring from say the stage to the drive, but it wont help if the bass is really loud as it is more than likely the airborne bass that is causing the errors.
If money is no object the sonnet solution is very good and in theory would be rock solid running in raid and mounted on neoprene.
Just a thought....
G5 DUAL 2.7GHZ 4 GIG RAM and G5 DUAL 2.5GHZ running as node, macbook pro 2.33 3 gig ram Mac OS X (10.4.9) Yamaha DM2000

Disk Too Slow??? Why now?

Hello all,
I have been using Logic Pro for the last five years on my system with no problems and all of a sudden, now I can't record a single audio track without a "Disk Too Slow" problem. Literally, the project can have only one track and it will still give me an error.
My System:
PowerMac Dual G5 2.5GHz w/ 3GB RAM
Mac OSX 10.4.11
160 GB Hard Drive (provided by Apple) - 58.9 GB left - Logic installed here
250 GB Hard Drive - 130 GB left - recording done on here
M-Audio Project Mix I/O
For years I have been recording with Logic and I've never had this problem. I haven't done anything new, haven't installed anything new, or anything like that and just now I've been having these problems. I'm a DJ and audio recording constantly for upwards of 90 minutes straight is vital.
Here's what I've done:
* Tried changing buffer settings (set from 128 --> 512)
* Tried making sure no other applications are running
* Tried emptying trash
* Tried turning off Airport
Nothing seems to work. Any ideas?

Hi there,
Sorry to read you are having troubles with this.
I have had the same troubles since Tuesday. All of a sudden I started getting Beach Balls and "Disc too slow". A few occasions I had a message saying that my "midi port was not found" on my MOTU.
Here what I spent the last couple of days doing.... I am sure you have tried them all but maybe something here may help
With some kind help from a forum regular, I reset my MOTU interface to factory settings. I repaired my permissions on my system drive.
I ran a "check disc" for my external audio drive, it past every time, but I repaired it any way.
I took my drive out of the firewire case to check the connections because it seemed it could be a power issue, tried it in another case. (I put the drive together so I felt comfortable doing this)
I also removed a plug in that I had added IK CSR reverb, I had installed it the day my system started giving me "disc too slow" messages.
I also removed all of my TRacks plugins from sessions, they are resource hogs and may have not been helping.
I also trashed my logic preferences.
Things at the moment are looking better.
If my problem still exists it may be in my case the drive being on its way out. It is only a year and a half old, and dose pass disc utility tests every time.
So I am thinking that I may have been mixing out my machine with plugs then having to do hard re-boots not helping things.
Sorry to hijack things, just hoping that we can maybe find a common cause, and solution,
Good luck,
Jay

"Disk Too Slow..." problem solved...for me

Lately my Macbook and Logic have been driving me nuts with the "Disk Too Slow" error message. But I notice it was happening on one particular song. I'll cut right to the chase....delete unused tracks. After doing this the song played thru without a peep. And has been doing so ever sense. The cpu meter shows little or no activity. I am happy and all is right in the universe. Just thought I'd pass it along. Your milage may vary.

Yep.....it all makes sense now. The song was created on my i5 iMac. Empty tracks not a problem there. I got wise when freezing the tracks didn't help. So I temporary deleted all my audio regions except those on ONE track. Still got the error message. So I froze that track and STILL got the message. ***? So I reloaded the song and deleted all unused tracks and, well, the rest is history. For what it's worth, 4 of those tracks were audio instrument and 8 were rewire tracks. I suspect the rewire tracks were the actual hogs, but I don't care at this point. Just happy to get some work done on the laptop. Your tip makes perfect sense as well.

Disk too slow- logic & macbook pro

Hi
I have recently bought logic studio 8 and i own a macbook pro. Whenever i try to record audio in logic, i get about a minute in to recording then a message appears saying 'disk too slow error 00001' although the music carries on, recording stop. It is always the same length of time before the message appears. i only have 1 or 2 plug ins going, and no audio tracks running for this to happen.
It is an intel 1.8 with 2gb ram and 80gb hd with edirol firewire interface for audio in. Is the machine not able to handle recording audio or is it something i am doing wrong?? I'd be very grateful for your advice, thanks in advance. Staf

I have an external lacie firewire HD which i save logic songs to which has over 80gb free space. I only have about 12gb left on the laptop hd (mainly because logic studio requires sooo much space).
Thanks, stafford

Disk too slow / System overload HELP?

I'm really hoping someone can help me out with this!:
I purchased a G4 PowerBook around six months ago, with Logic Pro pre-installed. Since then, I have mixed and mastered lots of music that was recorded on a previous system and imported. I was running multiple tracks simultaneously with tons of plug-ins and everything ran smoothly on my new Mac. HOWEVER, within the last month, my playback capabilities have been severely reduced. When I try to play back even two tracks simultaneously (with just one compressor or reverb), I get the error message, "Disk too slow / System overload."
My first reaction to this problem was to check my disk space and see how much room I had left: it turns out I have over one third of my harddrive space still available. I checked my memory capabilities and they seem to be more than adequate. I bought new virus protection, too, and ran scans to see if that might make a difference, but it hasn't. I don't understand why this is happening on a system so new. ANY ADVICE YOU CAN OFFER WOULD BE GREATLY APPRECIATED!
Many thanks.
Powerbook G4 Mac OS X (10.4.6)

It is generally not a good idea to run logic on the same drive that contains your audio files and samples. Most of the data involved with logic whether it be programs or individual audio files will be saved physically all over the place on your hard drive. At a certain point the actual part of the drive that reads the data will not be able to move around to all the little different audio files it needs to access for the session on top of running the program and whatever other software that is up. It is best to save all your audio files and samples to a fast external drive (7200rpm at least) otherworldcomputing.com has great drives that have high quality cases and the option to put any drive they have in stock into the case. (i would recommend seagate) If you are going to continue running your entire sessions off the internal drive then you need to keep up with your basic mac housekeeping. You should repair your permissions 2 times a month (use disk utility) You should buy a good directory repair program such as disk warrior. The directory is exactly what it sounds like. It keeps track of where everything is on the computer. If your directory is corrupt the computer will have to do an extra manual search to find what its looking for. If your directory is healthy your computer will make a straight shot to the file you are looking for.

No Reason For Disk Too Slow Error, any ideas?

Ok,
So I've used Garageband for years from iLife 06 and up and I've never had an issue with any Garageband until now. Here's the deal, I still get the disk too slow error, and there is no explanation. Below is my computer config:
COMP I'M USING:
Macbook Pro 13 inch
OS X Mavericks
Intel Core 2 Duo (1st unibody)
4 GB of RAM MAX
BRAND NEW Hybrid 7200 RPM Drive Installed 500GB total, 300 GB FREE
NO Other programs are open.
I use Garageband for recording songs but mostly now for recording podcasts. So the track I am using is normally 1 hour in duration. I can't seem to skip around, from minute 1 to minute 54 and edit at my whim without beach ball and timeing out getting the disk to slow error I never had this issue before, I either get the disk to slow error when trying to navigate large gaps of time in the podcast as I said earlier or even during RECORDING a podcast it'll simply say disk to slow, stop recording and occassionally say there are too many tracks in use, when I only record using 1 track of audio.
How can this be possible? Even my old G4 allowed me to jump all over the timeline with no issues. It seems there is some kind of flaw in the software. And yes, I just restored OSX Mavericks to my brand new Hybrid Hard drive, so there's no explanation as there are no disk errors or permissions errors of any kind.
I'd rather not hookup an external drive to record too as that seems silly when I've never had too before. If this "modern" computer can't do something that my old G4 ibook can do, don't you think we're going in the wrong direction with this program?
I've heard of so many people having this issue, and I thought upgrading my OS and getting a new HD would help but it hasn't. I'm at wits end with this issue.
Any advice would be helpful, thank you.

There are a few other reports of problems with 10.6.7
Some audio device(s) inputs have ceased working, a few disk to slow messages...etc. I don't see the wisdom of upgrading a working DAW system if that's it main function. OSX has to support a lot of different hardware now, many, many Intel motherboard and/or processor revisions... it's not going to be as smooth sailing as it used to be.
pancenter-
Here's a search over the past 90 days.
http://discussions.apple.com/search.jspa?threadID=&q=Disktoslow&objID=c231&dateRange=last90days&userID=&numResults=15&rankBy=10001

Disk too slow error when using M-Audio Oxygen 49 keyboard

I bought the M-Audio Oxygen 49 keyboard. And when I plug it into my MacBook Pro to do some playing, the project will record for maybe a minute but then I get a 'disk too slow' error and the recording stops. This happens every single time, no matter if there's 30 tracks or 1 track on the recording. I know that it is the keyboard causing the error because I am currently working on a 59 track piece that has effects on almost every track and my setup doesn't even blink. (well it'll pinwheel for a second when I hit record sometimes, but the CPU and disk meters don't ever get near red-line levels).
What on earth is causing this stupid keyboard to cause this problem, and how do I fix it? It's clearly the keyboard. When I unplug it and record a live track on a project that just gave me the 'disk too slow' error, everything works just fine!
Grr...
Any help is appreciated, thanks!
Edit: I have the MBP plugged via firewire into an Echo Audiofire and then into a WD hard dtive (at 7200 RPM). The keyboard is USB into the MBP.
Message was edited by: Zombie Flanders
Message was edited by: Zombie Flanders

hi
i spoke with Apple pro application support staff who confirmed that the Tascam 1884 patch for 10.4.10 is the cause of the problem. The apple boot drive can reliably record 1 channel of audio under normal circumstances. Apple staff described the situation as "unfortunate" and recommended to wait for Tascam to release 10.4.10 compatible drivers.
For anyone interested in the technical background, the Tascam 10.4.10 patch DOWNGRADES the audioFW component (messing with kernel headers etc.). This compromises the OS's ability to correctly communicate with FW devices.
I had tried recording to a firewire 800 drive, but all FW IO is affected by the 10.4.10 Tascam patch: Logic simply didn't record anything to disk when I tried this, and the machine became unresponseive. I do not recommend anyone attempt recording to a FW drive with the Tascam drivers installed.
I have recorded circa 400 hours of single channel 96K 24bit audio to my internal Macbook Pro boot drive using the same software/configuration under 10.4.9 without a single glitch. I do recognise that when requiring heavy disk IO it is not advisable to record to the boot drive. However, 1 channel of audio can be reliably recorded if the system is well maintained.
Thanks to all for your comments and suggestions.

Core Audio : Disk too slow (prepare)

Can anyone help me. I have created a track that will not bounce
because it always comes up with this error message: Core Audio: disk
too slow (prepare). I cannot bounce tracks individually for the same
reason. I have tried deleting some tracks that i dont need but it still does
the same. I have 700 and something ram. Is this not enough. I have
logic pro 7.1 and am using a few ultrabeats in the song. Know Any
tricks i can get around this problem easily with. Any help would be
greatly apreciateddd. thanx in advance.

The drives in the rear positions are on an ATA-100 Bus, those in the front are on an ATA-66 bus. The CD is on an ATA-33 bus, and no Hard drives should be sharing the CD cable. ATA-66 and ATA-100 are plenty fast enough not to be a bottleneck, as long as you are not experiencing low-level correctable Disk Errors.
A Disk Error will result in retries, both Hardware and Software, which often produces the data, corrected, after a delay.
My recommendation would be to find a time when you can back up all data from the troublesome drive, and take the \[several hours] to Initialize with the "Zero all Data" option. This writes Zeroes to every data block, then does a read-after-write to check the data.
If the Drive's error correction was required to recover the just-written zeroed data, that block is declared bad, and the drive will make a near-permanent substitution of a nearby spare block for the one found defective. This process has the effect of laundering out marginal blocks and returning the drive to "factory fresh" condition of all good blocks.

"Disk too slow or System Overload" ... hardly

Hi all!
I hung onto my 2007 MacPro until just before summer when I upgraded to be on the safe side. I do orchestral work and have been accustomed to running heavy VSL projects on one single machine pretty effortlessly. On my new 12 MacPro, things are working even smootherEXCEPT for this "Disk too slow or System Overload" happening from time to time on fades. The projects in hich I experience this behaviour are audio only, orchestral mixes of between 60 and 70 audio tracks and I get the message when executing fades on all tracks simultaneously. I can't remember getting this on my old MacPro which had a fraction of the cpu-power and not nearly as much ram.
My specs are 2x2.66 6-Core w/32GB ram, and all audio files, fade files and othe project files, are written to two 2 TB 7200 disks in the internal disk slots, configured as striped RAID. This gives more than enough speed and I still have 1,64 TB of free space on the RAID set.
This issue comes and goes and I can't seem to figure out what triggers Logic's problem to read fades fast enough. Just now I had some corrupted fade ailes, rebuildt them and now Logic can't get past the fades at all unless I start playing in the middle of them.
I can't understand why this problem should be introduced on a configuration much, much faster than my previous MacPro where this problem hardly ever occured. I even doubled the I/O buffer from 512 that I was using on my old mac, to 1024 with no difference at all. Increasing Process buffer size to "Large" doesn't have any affet either.
Any clues anyone?
Best regards,
Ginge

Good point, nice link!
But the thing is I'm not using any software instruments and apart from one EQ on a track here and there, two Tube tech plugs and two sends to Altiverb (of which one is inactive). This kind of load was not a problem on the old heap and shouldn't be a challenge for a 12-core... Also, without changing anything apart from the move above, it is now playing with only one pixel-high movement on the meter, like you would expect it to do.
BTW the quirk is now back on the project that was fixed. I did new fades at another position and CPU 1 is now maxing out again. A new set of fades means equal fades on regions on 63 tracks playing simultaneously.
As I'm writing I'm becoming aware of one interesting aspect: the project files contains imported aaf data and to save space I'm leaving the media-files at the original location where it was put by Pyramix who exported the aaf. I figure there shouldn't be a difference if the audio files reside in a folder called "Media files" or "Audio files". These folders are sitting on the same disk albeit not in the same subfolder. If anything, I'd assume it would minimize potential for error caused by having several copies of files with identically names on different locations on the disks. But now it seems the issue is less likely to appear if I save the project including assets, copying external audio files (on any disk), or at least that is how it looks like right now. New fades are working fine after I've done this.
Doesn't make sense to me but it seems to make a difference...
Ginge

Logic Pro 8 - same old 'system overload' and 'disk too slow' errors

I am having serious issues with Logic Pro 8 on my macbook pro. I am running it with a Focusrite Saffire LE firewire interface.
I am only using it to playback two stereo files, as a backing track and a click for live performance. I can seem to leave it running all day at home without a problem but when I try and use it in rehearsal it trips up either straight away or half way through a track. It gives either 'disk too slow', 'system overload' or 'unable to sync audio and midi' error messages. This is obviously rendering it unusable. I have tried all the usual tweaks associated with this problem but to no avail.
I am reluctant to believe it is a hardware issue because I have Cubase 5 on the same laptop and that runs like a dream all night without the slightest hiccup. Obviously I have been using that instead.
Having done many internet searches about this it does appear to be a common problem but with no definitive fix.
Did anyone else getting these issues ever fix it?

Jazzmaniac wrote:
That has nothing to do with logic. If your had disk becomes slow in rehearsals then it's very likely the hard disk acceleration sensor kicking in to protect your drive from damage. Strong vibrations will cause the heads to park, significantly reducing the the seek times and the transfer rates. Jazz
How does that explain the OP's statement:
"I am reluctant to believe it is a hardware issue because I have Cubase 5 on the same laptop and that runs like a dream all night without the slightest hiccup. Obviously I have been using that instead."
I think it has more to do with Logic's disk access and buffering system.
It's true that vibrations can cause data mis-reads as the drive head has to re-read the data, however part of the problem lies with Logic's buffering. I don't think the sudden motion sensor (sms) is kicking in, just that the drive may be having to re-read data and Logic's buffering system can't handle the slight interrupts.
I've dealt with the exact same situation locally (for a client), we ended up using an old bass drum case to make a padded rest for the MBP, that eliminated 90% of the problem.
pancenter-

Disk too slow messages

Similar Messages

Maybe you are looking for