"Disk is too slow or System Overload. (-10010)" errors with Snow Leopard

Since upgrading to Snow Leopard, I have been getting these error messages while using Logic Express and GarageBand. At first it seemed like a problem with the latest update to Logic Express 9, but then it started happening with GarageBand. I have been on the Logic discussion forums, but this really seems like a Snow Leopard problem. Anyone else out there having similar problems and know of any fixes?
Thanks.

It's a new IMac purchased in July with a 345 gig drive, with 278 gig available. I'm recording to the internal drive.
It has a 2.8 GHz Intel Core 2 Duo processor and I had extra memory installed when I bought the machine, so it has 4GB. I don't know how many partitions on the hard drive.
(Sorry, I'm a relatively new PC-to-Mac convert)

Similar Messages

Logic Express says "Disk is too slow or system overload (-10010)"

I have a brand spankin new white MacBook. It has Intel Core Duo 2.1 processors, with 2gigs of RAM, and Leopard 10.5.6 OS. I am using Logic Express 8 and every now and then I will get an error message "Disk is too slow or system overload (-10010)
I checked the requirements for Logic Express 8 and I exceed them. Could I still need more than 2 gigs of RAM?

I got the same problem when I was recording 10 tracks while using SW monitoring. For a short while it went OK but then twice in a row I got this message about the disk being too slow. The result was that I got a real loud noise on the headphone. But after that the recording just proceeded. I had to stop because otherwise I think the musicians would have gone deaf. However I had to continue with recording for some more hours so I tried to solve it. The following worked for me. I turned off 24 bit recording because I had the impression there was too much data being written. I also made the buffer as low as possible (32). After that I did not have a problem anymore and recorded for about 7 to 8 hours in a row.
So I suspect that the HD is indeed too slow or has not enough cache. As far as I can see my HD has 8 MB RAM and runs at 5400 rpm. I wll ask Aple support if this could be an issue when recording large amounts of data. Note that I have 4 GB RAM and still got the problem so that is not the cause of this issue here.

Logic 9.1: Disk is too slow or system overload (-10010)

After updating I kept getting this error: Disk is too slow or system overload (-10010)
Can't go five minutes without encountering this. I'm in 32 bit mode using record via rewire. It's maddening and I am now kicking myself for updating. The song that's doing this is a song I was using working on the day before I updated. I had no problems then.
Anyone else encountering this?

I have encountered this issue as well. I never solved the issue but did find a work-around. Unfortunately, this temporary solution may not work for more 'heavy' users then I. Although, many have commented that this issue happens even on small projects (as it did with me also), many usually create much bigger projects and are using the smaller projects just as a litmus test. I qualify this because the work-around I discovered is using USB 2.0 to connect my external HDD rather than either of the firewire ports on the drive. So, for those wanting to create larger projects, this solution may not be an option. I won't delve into the details here, but I will include a link to my thread so you can see all the troubleshooting I did and the suggestions that were offered.
http://discussions.apple.com/thread.jspa?threadID=2102925&tstart=0
Or, you can search the forums for error 10010.
The only other items of note I can think to add at this point is I am still on 10.5.8 not SL. Logic 9.1.1, and I recently increased the amount of RAM to 4G. The work-around has been working for me, and I haven't had time to check that any of these updates fixed the problem. But I will soon and will report any changes.
I hope this provides some insight.
Chris

Disk is too slow or system overload (-10010)

Yes I have searched but I couldn't find an actual solution to get logic to stop doing this every other minute (literally). I used to think the 'smart' snap feature was the most annoying thing in logic, but this waaaaaay surpasses it.
Anybody found a solution yet?
Logic 9.1.0 32 bit.

The thing to remember is that the infamous 'disk too slow' or 'CPU too slow' error messages aren't just some random bug that needs fixing. They are actually warnings that are there for a reason. You'll get them in any DAW - or any kind of audio or even video application - that needs to do a lot of disk read/writes and CPU work in realtime. There is plenty of advice out there on how to optimize your system to get it to perform as best as it can (even in the Logic documentation), but there is obviously a physical limit to how many tracks and plug ins you can use. When you hit this limit, then all the warning is telling you is that your drive or CPU are actually too slow for the task at hand. At that point, there are other workarounds (like freezing tracks, adjusting buffer and other settings, or bouncing subgroups etc) to keep you working. In some cases it might mean that your work is beyond the capabilities of the machine you're using, in which case considering getting a faster Mac and/or faster hard drive(s) is the next solution.
Another thing to keep in mind is that Logic uses a kind of resource optimization process, built in to the audio engine. This means that sometimes you'll get a 'disk too slow' error in some part of your song, but when you play through that part a second time, you don't get the error again. This behaviour is markedly different to how other DAWs work, notably ProTools, where the disk and CPU resources are pre-allocated to guarantee performance up to a pre-defined maximum limit of tracks.. The upside of Logic's dynamic engine is that it allows Logic to squeeze out every last drop of power it can get it hands on, by not doing any processing on tracks that aren't playing audio at a given time. But the downside is that you can get CPU or disk too slow errors at seemingly random places. It can be confusing to see a disk too slow message when playing a certain passage, and then not seeing it again in exactly the same passage later.. leading to people wondering if it truly is random, and a bug. But it isn't a random bug, it's just the way Logic handles audio in an effort to get the highest track count possible at any given time.
Btw, @ fuzznormal: While I agree with pretty much everything you said, you make it sound like a MacBook Pro's internal drive is slower than it really is. Honestly, even if you have put in dedicated SATA II cards or some kind of decent SCSI in your G4, the system buss alone on those old machines is at least an order of magnitude slower than the system buss on any current Mac.. It creates a pretty formidable bottleneck which wipes out a significant amount of any speed advantage the G4 with dedicated drives might have over a MacBook Pro using its humble internal. I (like everyone) used to have a snazzy G4 with a fast SCSI card (I think it was SCSI anyway), and there's no way I could get anywhere near as many tracks running as I can now on my MacBook Pro using the internal drive. Of course I don't usually use the internal drive for audio, but on the occasions that I've had to, it happily chugged out more tracks than my old G4 could, with very rare disk overloads.

Disk is too slow or System Overloaded ERROR

I have logic studio and a macbook pro and keep getting the following error message: Logic Pro: Disk is too slow or System Overloaded (-10010) Not sure how to fix it. Any suggestions?

It's a bug in logic. It's been there since multicore CPUs came out.
Try putting your fx on a bus/aux rather than on the same track as the instrument.
That way it will trick logic into using a different core for the different tracks.
I've seen this problem on dual quad core CPU mac pros, so it has nothing to do with your CPU performance.
Also if your recording to the internal harddrive whilst playing back audio from it you might run into problems when using bfd2 or addictive drums or any other large sample library type plugin.
In my MacBook pro I took the DVD drive out and put in an SSD for the OS in its place.
I then use the internal mechanical drive for recording and samples etc.
This solved all my issues and made everything so much snappier.
It's dead easy to do too. Infact it works so well I'm thinking about getting a standard MacBook pro (so I can do the same thing again) instead of the retina one.
I'd refuse to buy a retina one until I have seen logic play back 1 instance of bfd2 a few audio files whilst at the same time recording a guitar through amplitube 3. I'm not paying £2000 if it can't do that. (you'll be surprised)
Like I said my old one couldn't do it due to the overloads you mention until I did the DVD drive swap trick.
The retina looks good but, 1/4" thinner is one thing, but having to carry leads and adapters for everything it kind of defeats the purpose!
I would need a thunderbolt to FireWire adapter (which aren't out yet) a FireWire 800 lead and a FireWire 800 to 400 adapter jut to plug my apogee duet soundcard in! ***?
I'd buy a thunderbolt audio interface but their are no mobile ones. The only ones that are out are large ones for the studio (And mac pros don't even have thunderbolt)
It makes no sense, no sense at all!
You couldn't make it up. At least they have dropped the dongle from logic so I can plug my mouse in.
Emagic should release a pc version again. These quarterly decade updates are getting boring!
Where's logic X?

Error message!!!!!Disk is too slow or System Overload this keeps coming up?

Logic Pro:
Disk is too slow or System Overload
(-10010)
Mac book pro
10.5.8 OX
4gigs RAM
recording to ext 800 firewire drive
any ideas???

I am just reposting my response to a similar question because I never found a solution to this problem just a work-around. I would love to know the actual solution.
I have encountered this issue as well. I never solved the issue but did find a work-around. Unfortunately, this temporary solution may not work for more 'heavy' users then I. Although, many have commented that this issue happens even on small projects (as it did with me also), many usually create much bigger projects and are using the smaller projects just as a litmus test. I qualify this because the work-around I discovered is using USB 2.0 to connect my external HDD rather than either of the firewire ports on the drive. So, for those wanting to create larger projects, this solution may not be an option. I won't delve into the details here, but I will include a link to my thread so you can see all the troubleshooting I did and the suggestions that were offered.
http://discussions.apple.com/thread.jspa?threadID=2102925&tstart=0
Or, you can search the forums for error 10010.
The only other items of note I can think to add at this point is I am still on 10.5.8 not SL. Logic 9.1.1, and I recently increased the amount of RAM to 4G. The work-around has been working for me, and I haven't had time to check that any of these updates fixed the problem. But I will soon and will report any changes.
I hope this provides some insight.
Chris

"Disk is too Slow or System overload" message...HELP!

Hello,
I am using a MacBook Pro and recorded an Audio track last night with my guitar (plugged directly into my Motu audio interface) using the the "tape delay" effect/plug-in. After recording ONE track, I was playing it back and simply playing my guitar for practice over the track while monioring through my speakers when I get the message "Disk is too slow or system overload (10010)."
What is this? I should be able to record audio tracks with my MBP, right? What am I doing wrong and how could my system possibly be overloaded and unable to continue with ONE audio track? Please help. Thank you.

you can also try typing System overload in the search discussions field on the top right of the discussions page,make it specific when you get the results to Logic 7.
there's millions of posts about it....
also check your buffer,(low setting when recording editing ,increase it at playback)
and in case you recording/play from an external drive make sure it's power supply it's connected.

Logic Pro X - Disk is too slow or System Overload. (-10010)

Hi there, I'm a professional music user and recently switched from Pro-Tools to Logic due to PT11's lack of third party plug-in support at the moment. I was looking forward to leaving behind the error messages of Pro-Tools for the supposed plain sailing of Logic. However, after installing Logic X and starting a new session with one track of audio and 4 tracks of software instruments, I'm receiving the following error message when attemping to record a part on one of the software instruments. 'Disk is too slow or System Overload. (-10010)'
I have an 8 core Mac Pro with the latest version of Mountain Lion, 16GB of Ram and a 250GB SSD boot drive (which Logic is installed on). My sessions are ran from a secondary 120GB SSD which has 110GB of free space on it and my sample libraries are streamed from another internal 250GB SSD and a 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5" Internal Hard Drive. My interface is a Focusrite Scarlett 6i6 USB 2.0 and my I/O buffer is set to 512.
It is completely unacceptable to me that I should be experiencing error messages with this set up and a 64 bit DAW, particularly when the session in question only has one track of audio and one instance of East West's Play engine, spread across 4 software instrument tracks.
Has anyone else experienced similar problems or have any ideas as to what the solution could be? I'd really appreciate any advice.
Cheers,
David

Just as a quick followup....
After doing a little research online it seems the Scarlett is one of those USB2 devices that has issues with how Apple changed their implementation of USB when they released Macs with USB3 interfaces and put this updated implementation into Lion and later Mountain Lion... and that this is probably why some people have major issues like the OP is reporting and why other's do not. It depends on the hardware/OS X version combination as to if this issue rears it's ugly head.
Oddly enough some Win 8 users are also reporting similar issues with the Scarlett for much the same reason.
The March 2013 Scarlett OS X drivers are intended to 'alleviate' this issue but Focusrite have stated it is only to 'alleviate' in some instances and not completely fix the problem for everyone who has it,.,..
However, the good news is that Focusrite have released some beta drivers (v1.7b2 and later b3) which seem to work better for some people than the last official release...
Mac Only.
General stability/logging improvements:
- Improved audio stream syncing
- Fixed bug which results in occasional inaccurate timestamps
- Improves sample rate switching
- 18i20 stream formats now switch automatically
- Fixes Forte streaming at 176.4/192kHz
You can find them here..
http://beta.focusrite.com
Note: These beta drivers again seem to only alleviate the issues for some people and not all but it has got to be worth giving them a try I would think...

I just installed Lion and the newest version of Logic express 9 (9.1.5) and every time i playback audio I get this error message: [Disk is too slow or System Overload. (-10010) . Never had any issues before now...

I just installed OSX Lion (10.7.2) and updated to the newest version of Logic express (9.1.5) on a macbook and every time I playback audio I get this error message: [Disk is too slow or System Overload. (-10010) The Sudden Motion Sensor may have parked the hard drive head, or the disk performance is not sufficient to read or write all audio tracks, or the system was not able to process all data in time]
Never had any issues before now... any ideas?

Have a look into the Preferences folder (YourUserFolder/Libraries/Preferences/) and trash all Logic preferences.
You'll have to setup the program again.
cheers
rob

"LOGIC PRO X: Disk is too slow or System Overload. (-10010)" This is the message that I was having since two weeks ago with my Logic 9. I updated two days ago to Logic X and I am still having the same problem.

"LOGIC PRO X: Disk is too slow or System Overload. (-10010)" This is the message that I was having since two weeks ago with my Logic 9. I updated two days ago to Logic X and I am still having the same problem.
I recently formatted my computer. In other words, I'm not using too much memory of my HD. My Memory Ram is 8GB.

dandotcraig wrote:
A week before logic X comes out it starts bugging out... i deleted a bunch of stuff on my HD and cleaned up everything... didnt fix anything... then logic x came out and I though oh i better update that will fix everything... and im still having the same problems... its rediculous.
Umm,, no offence... but what is ridiculous... is you didn't troubleshoot the original problem but instead you assumed it was a LP9 problem so you updated to LPX which is still in its early days and is likely to be less stable than LP9... rather than more so!
So.. Here's the thing....
LP9 was working fine and then stopped working normally according to you. Therefore what changed at the time LP9 stopped working normally?
Here are just a few ideas to think about.. for around the time this started..
Did you update Logic Pro 9... OS X... Drivers for Midi/Audio or other connected devices?
If you did, did you then restore from a backup you made prior to these problems occuring and what happened when you did so? (assuming you do make backups of your system?)
Did you install any new Apps on your Mac?
Did you add a new Hard Drive? How is it formatted?
Did you start recording or creating music in a different way to how you used to before the problem started?
Have you started using a different SI or FX plugin or plugins.. More or different FX for example.. Did you install a new version of a plugin?
Is all your software legal? (Have to ask because some people install all kinds of illegal plugins and whatever else.. and have no idea how the 'cracks' work or what they might affect/mess up/conflict with in the process)
Have you looked at the System logs to see if anything is happening out of the ordinary when you get these messages?
Have you looked at OS X's Activity monitor to see if any app or routine is kicking in hard when you get this issue?
Basically, you need to think about and look for what changed... because something apparently changed to suddenly cause these issues...given you said you didn't have them until a certain timeframe and some of the questions above, I hope, will get you thinking..
....and maybe a few of the others here will come up with other ideas and suggestions to help you...
Good luck and let us know how you got on...

CoreAudio: Disk is too slow or System Overload. (-10010)

I keep getting this error when I'm playing a song that has 16 tracks and effects on each track, but each track is frozen (!): CoreAudio: Disk is too slow or System Overload. (-10010). I'm running a G4 and have 2G RAM. Is this common? What can I do to prevent this? Thanks for any advice you can give!
-David

In addition to Rohan's suggestions you have more options depending on how you work and what phases of the project you are in.
Something overlooked very often is polyphony enabled for the EXS24-some patches are set to 64 drop the polyphony to either the minimum you will need or less (if less you will notice older notes cutting out-but you can set it to the necessary number upon bounce or export). Some mono patches from sound designers are set to 32 or 64-even if you enable unison this is often worthless.
Up your buffer size-I usually have my PBook at 512-I usually do offline editing, location recording and sound design with the book anyways.
Export the track.
Set virtual memory in EXS prefs to 'on' and with the largest RAM allocation-slow disk, lots of activity.
If you use certain exs patches often but only parts of them trimming the excess off the instrument can improve performance. If you have a piano program with good samples you can initially create a lite version with 2 velocity layers and then when it is time to get things sounding good revert the instrument to the original 5 layer-obviously this makes a huge difference depending on what you are using the piano for, leave it if it is critical.
Save the Channel strip and export as audio file while keeping the sequence in your session. Like Freezing but you can manually trim the file start position and set the bit depth. Freeze files render from the start until the last audible sample and then truncate the tails, meaning even if you can't hear it it is still pulling "silence" from disk as long as there is sound after it. Exporting as 24 or 16 bit will effectively reduce your file size by 25 (24bit) or 50 (16bit) percent. If you know you don't have to edit a performance for weeks to come exporting it will solve alot of problems for CPU.
Someone should back me up on this one but at the moment I want to say EXSamples load into memory regardless of freeze settings-reducing your resources.
Disable the filter (if live or playback-N/A with Freeze)-it is often not critical for some patches. The more synthetic sounds or sounds with fewer/shorter samples rely on them.
Disable Unison.
Most sample libraries were not recorded at 88/96k-there is no benefit in running them in sessions in these Sampling rates as far as the EXS sound quality goes.
That should keep you busy for a while, just some tuning to up your system performance.

Disk is too slow or System Overload. (-10010) The #SuddenMotionSensor - CAN I TURN THIS OFF sick of it popping up! any solutions? #logic9

Disk is too slow or System Overload. (-10010) The #SuddenMotionSensor - CAN I TURN THIS OFF sick of it popping up! any solutions? #logic9
i have an external firwire harddrive just for the audio projects which is 7200rpm etc and it has 500gb of free space on it!
i've already tried the pmset -a sms 0 thing, but that is only for laptops, their seems to be no solition for Mac Pro Desktops!
this is annoying.
hope someone can help.
Dan

and in laptops it is just working for the original builtin HD.
It shouldn't be there at all.
you set it off by (copy/paste):
sudo pmset -a sms 0

Disk is too slow or System Overload. (-10010) on Mac i7

Hello dear Logic users,
My problem is: I use Logic pro X on iMac i7 X 3.4 Ghz with 16 GB of RAM running OS X 10.9.2. Mavericks.RME 400 firewire.Speed of hard drive jumps to 100 - 130 Mb/s. Hard drive Rotational Rate:7200
Logic cannot play more than 60 WAV audio tracks. When I add more than 60 tracks I get error letter " Disk is too slow or System Overload " So that is wonderful that system can't run more than 60 tracks. So i did not try yet software Instruments tracks.
Maybe someone is confronted with such the problem?Or is my hard drive bad, or maybe here should be performed specific settings on Logic?
Any help will be so much appreciated!

Hi
LOGIC wrote:
My problem is: I use Logic pro X on iMac i7 X 3.4 Ghz with 16 GB of RAM running OS X 10.9.2. Mavericks.RME 400 firewire.Speed of hard drive jumps to 100 - 130 Mb/s. Hard drive Rotational Rate:7200
Logic cannot play more than 60 WAV audio tracks. When I add more than 60 tracks I get error letter " Disk is too slow or System Overload "
It is generally accepted that it is not a good idea to be running audio projects from the OS drive.
You do not mention what Bit depth, Sample rate etc. Higher sample rates mean larger files, means more work for the drive.
CCT

Disk is too slow or System Overload Error on new Core i7 iMac

Well I just unboxed the new supercomputer, 27 inch iMac with Core i7 and 8gigs of ram. Spent several hours installing Logic Studio 9 and for an opening act I loaded up the demo song by Lily Allen. Too my utter dismay within seconds of playing the demo in Logic Pro I was greeted with the error "Disk is too slow or System Overload.(-10010)".
Can anyone make sense of this? Shouldn't this computer be able to handle this multitrack Logic song with relative ease? What is the problem here, I, of course, am very confused and very worried that something is very wrong.
Thanks

I am running on less of a machine than you are, so I have experienced similar problems, even when playing back 4 audio tracks while recording 2 all at once (usually with significant plug-ins on the 4 playback tracks).
The easiest solution I've found, without modifying how your plug-ins run, buying hardware, etc., is to "Freeze" the tracks that aren't being worked on at present. It "renders" all of what the plug-ins are doing so that the CPU and hard drive are not taxes nearly as much while playing back. It just takes a few seconds to render them once, and then your playback/recording drops the amount of resources it requires tremendously.
The easiest way to activate a freeze on a track is to right-click on the track name in the Arrange pane, select "Freeze" so the button that looks like a snowflake appears next to each track. You can click and drag down the contiguous tracks that can be frozen to turn the option on (or individually click to turn them on). You will then need to play the project to "render" the tracks and freeze them. Next time you play the project, it will run with many less resources and should save you from seeing that message.
As an aside, you may also want to make sure that you are not running any other applications. I found that another app in the background (Connect360) was running on my Mac and sharing my iTunes to my XBox 360, which was also making a good use of the hard drive at the same time. Any other applications running while Logic is running should be closed to ensure the best performance possible in your audio editing environment.
Hope this helps!
Frank

Disk is too slow or System Overload. (-10009)

Hello all,
I'm running a G4 PowerBook, with 1.67 GHz, and 1.5 GB DDR SDRAM. My Logic set-up is Logic Pro 7 and a Motu 828mkII.
My present Logic project contains 7 tracks, with EXS24 through 6 tracks and Sculpture through the last. The instruments were triggered through a midi keyboard.
While trying to score a short film, I keep running into the following error:
CoreAudio: Disk is too slow or System Overload. (-10009). The error happens while recording and during playback only. There are times when I do not recieve the error message, but playback is terribly jerky and I'm unable to clearly see exactly where I am on the timeline.
I have searched for similar errors on this site and cannot seem to find an answer. I imagine the solution is changing the way I have my I/O setting in the CPU usage. Am I on base?
I'd appreciate any help,
Kris

Hey Cyril and 25G's,
Well I went out and bought a OWC Mercury Elite Pro Firewire 800 with Oxford 912. I transferred the EXS Factory Sample files to the OWC drive. Then I deleted the EXS Factory Sample files on the OS hard disk. Then I created the alias for the Samples and placed the alias back in the Logic file under Application Support on the OS hard disk.
The alias' seem to be working because the Logic project works. The only problem is that it is still terribly jerky.
The CPU is maxing out while the I/O meter is not responding at all. Could this be the clue to my problem?
(Also, Cyril, call me stupid, but I cannot find the Virtual Memory portion in the EXS Preferences.)
Thank you for all your help. (I am a bit slow myself when it comes to Logic and the proper steps to de-bugging a problem. So, very detailed explanations are appreciated)

Disk is too slow or System Overload.

I was working on a project that had a little over hundred tracks, and got this error. I thought that it was understandable, as I had many tracks(even though I was only recording one), so I started a new project to record it, with only one track. But I still got this error when I was recording one track, with no other tracks in the project! How can I fix this?
Here's the complete message:
Disk is too slow or System Overload.
(-10008)
The sudden motion sensor may have parked the hard drive head, or the disk performance is not sufficient to read or write all audio tracks, or the system was not able to process all data in time.
I run this on a 27" iMac with 8GB ram and 7200rpm, which should be enough to play and record many tracks.

ArnsteinK wrote:
so I started a new project to record it, with only one track. But I still got this error when I was recording one track, with no other tracks in the project!
But you didn't shut down Logic or (sometimes best) restart your machine in between ? Often, data gets left in memory and it hasn't had any particular command to clear it otherwise - a lot of allocated memory can be still considered as 'used'.
Well, maybe, but that aside,
ArnsteinK wrote:
I run this on a 27" iMac with 8GB ram and 7200rpm, which should be enough to play and record many tracks.
- hopefully you're not doing that just using your internal computer's drive - if you have, you've been lucky so far.
If you're into Logic it is a well established fact that this message can appear for so many different reasons and its not possible for me to know what goes on with your machine - there are plenty of articles on this forum and LogicProHelp as well as the very concise and accurate (but not always as explanatory as I'd like it to be) stuff on this Apple website.
That's all I can offer at the moment until we have some more technical information, in which case there are others here that may have particular insights as well, so you're gonna have to take it from there because there is no one answer.

"Disk is too slow or System Overload. (-10010)" errors with Snow Leopard

Similar Messages

Maybe you are looking for