Core Audio Disk IS Too Slow (Write) (-10002)

This only happens when recording, not playing back
I have added no new equipment or outboard gear
Recording guitar/cab mic'd through a tascam USB 144>computer
The first 2 tracks went well, then it all went downhill after that
To NO Avail:
http://discussions.apple.com/search.jspa?threadID=&q=%22DiskIS+TooSlow%22&objID=f1195&dateRange=all&userID=&numResults=15
1.Checked both the System preferences under "Sound", and GarageBand's preferences under the "Audio MIDI" tab.Neither an iSight camera, nor a USB Speaker system is selected for input or output.
However , My Tascam USB 144 has to be hooked up as an input in order to record ?
2. Repaired/verified Disk permissions
3.Followed these steps in Ch.10 of the garage band missing manual (unless there are some new ones)
A.
Closed out all programs,
B. Hit the track arrow to hide the mixer
C.Hid the window completely while recording
D. Locked the tracks
4. Tried logging out, then back in, rebooting
THis only provided temporary remedy and allowed me to record further than usual, but would wind up stopping with the error message
5.Cleaned the cache out
6.Set the buffer size to max
Message was edited by: Geoff J

Perhaps, my implication was that an older OS version might be more stable with your hardware, as per my particular experience.
You don't say what audio hardware you're using. I'd suggest going to the manufacturer of whatever you have and asking them if all is kosher.
Also, disengaging the hardware and using Logic with built in audio while playing back will help you trouble shoot. If it works okay without any hardware hooked up, you have a lede as to the potential problem.

Similar Messages

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.

Core Audio Disk too slow or System Overload message

Hi, I hope somebody can help me. I've seen the topics about this already posted, but my situation is a little different. I'm only playing back three tracks of recorded audio and two EXS24 sampler instruments. I have the Logic compressor on my bass track and thats it! My Disk IO meter shows no load at all as well as the audio meter. However, I'm still getting the core audio disk to slow or system overload message. I figure with a dual 2.7 G5 and 2.5 Gigs of ram I should be unstoppable. What's happening?
By the way I'm using Logic Pro 7.1, and my sound card is a Delta 1010 from M-Audio.
Thank You, anybody for your help!
Dual 2.7GHZ PowerMac G5 Mac OS X (10.4) 2.5 Gigs of ram

Same or similar problem to you check out my recent thread
http://discussions.apple.com/thread.jspa?threadID=245528&tstart=30
Powerbook, 512, 1GHz, 60 gig Mac OS X (10.3.6)

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

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

No Audio Playback due to Error Message "Disk is too slow. (Prepare) (-10001)"

Out of the blue, no audio playback. Was working just fine earlier today.
I repeatedly get the error message:
Disk is too slow. (Prepare)
(-10001)
NOTE: I have more than enough disc space. That is NOT the issue.
I also just got a second error message:
Part of the Project was not played
This project has too many real instrument tracks to be played in real-time. To optimize performance, see the 'Optimizing GarageBand performance' page in GarageBand Help.
NOTE: Odd as I have only 2 tracks in the GarageBand file.
Any others experience this? Suggestions?

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)

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...

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 error with Logic 9.1.4

I have am running Logic 9.1.4 on a MacPro 2 X 2.8 Ghz (Intel) with 8GB of RAM running OS X 10.6.7.
I recently updated to Logic 9.1.4 and was trying to record one track of vocals on a session on which I had previously worked on a few weeks earlier with no issues.
But today I got this error over and over again:
Disk is too slow or System Overload.
Occasionally I would get the message below with the error, but not always:
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 don't have a lap top and tried a few fixes found here (buffer size increase ,rebooting etc.). Again, I recorded several tracks of vocals on other days with absolutely no problems. But today couldn't record more than a few seconds at a time without getting this error. The only difference I can think of is that I updated to the latest version of Logic 9 (9.1.4) rather than whatever the previous Logic 9 version was.
Any help at all would be greatly appreciated.

ISSUE RESOLVED!
So after messing around with this for over 4 hours today, I think I have resolved the issue.
The issue seems to have been primarily with my main vocal track, which was frozen while I was recording a harmony vocal. The main vocal track was actually made up of about 20-30 take folders which I had swiped to make one good take. I was hoping to take a good hard listen at my swipes during mixing once all recording was done, so I had never merged into one audio track. Besides, like I said, this track was frozen so I figured it was already playing back as though it was one audio file.
So I just merged all the takes in this track into one file. Counterintuitively, unfreezing about 10 tracks also seemed to improve performance in the meters. Which makes me wonder whether I should use freezing at all? Both these things together seem to have made all the difference.
In the process, I also learned how to run Logic 9 in 64-bit mode, although this (at least by itself) didn't seem to make any difference other than making AmpliTube inoperable.
So the lesson here: don't have too many take folders going at once. And freezing tracks with take folders doesn't seem to come close to being the same thing as playing back one single merged audio file.

Hi i use a macpro i7 wt 7200rpm internal drive i get this message Disk is too slow-(prepare) (-10001) when i am using logic 9

Hi i use a macbook pro 17" 2.66ghz intel core i7 with 8gb ram & a 500gb@7200rpm internal drive i get this message "Disk is too slow. (Prepare) (-10001) when i am using logic 9 wiyh just a 5 vsts loaded 2 of them being esx24's . i used to not get this warning earlier in the same or even heavily loaded projects.
When i press play the beachball appears for a minute or so then the message.
Even when i open up a new project a beachball appears for about 30-40 secs and then the project opens up
i have even tried opening up the projects w/o any vst's loaded (i have disabled them from audio units manager)
Initially i thought it was a hard drive problem so apple had it replaced for me but i am still encountering the same problem.
have even tried disabling the sudden motion sensor from terminal no luck there too
tried reloading osx 10.6.7 no luck there too
what do i do
aggi

How full is your 500 GB hard disk?
Do you have 10% to 15% free space available?

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?

Two HDD - "Disk is Too slow or system overload"

I have a White MB C2D 2GHz, 2 GB DDR2 and Logic 7.2.3.
I wanted to open the session with 44 audio files, but there was an error "Disk is Too slow or system overload. " I found information that I need to replace my standard 5400rpm drive to 7200rpm.
But first plugged in my portable USB drive that is 5400rpm and copied this Logic project. It works! All OK, but work over USB is very slow.
I wonder if you really drive on the 7200 exchange will help me.
Please help.

el.j-music wrote:
I have a White MB C2D 2GHz, 2 GB DDR2 and Logic 7.2.3.
I wanted to open the session with 44 audio files, but there was an error "Disk is Too slow or system overload. " I found information that I need to replace my standard 5400rpm drive to 7200rpm.
But first plugged in my portable USB drive that is 5400rpm and copied this Logic project. It works! All OK, but work over USB is very slow.
A 7200 drive may help but then again... the internal drive is what the operating system uses to write swap files and other OSX related tasks. OSX keeps files under 20meg defragmented but larger files are left as is so your audio files were probably copied to various places on the internal drive, not the most optimal for playback.
I would think a 7200RPM external Firewire drive is your first choice (unless you're using a Firewire audio interface). In that case either a 7200 USB drive or 7200 internal drive would be the way to go.
See what a few other posters think before deciding.
pancenter-

How do I fix the problem 'disk is too slow' and what does it mean anyway?

I'm transferring casete tapes to the Mac via the input line. I've transferrred nearly 100 with no prouble, but sudddenly today two things have gone wrong (see separate question for the other one). This one is that suddenly the error message 'Disk is too slow' comes up. also the track (the top one, not the bottom edit section one) is bright red instead ofthe usual dark purple.
What's gone wrong and how do I fixit?

Sorry about the lack of terms: lazy of me I admit. Having read up Garageband Help, I think I've got the answers. Yes, by the top part I mean the track in the timeline. The bottom part is the same track showing up in what is headed the 'Audio Region' The bright red is the colour the track is in the timeline during recording, and it stays like that until after stopping recording I click somewhere in the timeline section (not necessarily on the track itself) at which time it just goes the normal kind of dull greyish colour an unselected region does.
Thanks for telling me how to see the HD info. Its 250GB, of which I've used about 23GB. The first computer I worked on as a programmer back in 1962 had a 400KB drum (the first disks didn't arrive until 1963) as its random access backing store - and yes, that is a K. The machine also came with 12KB of RAM and 4 tape decks, was the size of a hotel kitchen, and cost about $200,000. You young people don't know how lucky you are

CoreAudio: Disk is too slow

Have just switched over to MAC Pro Intel, a few years old. When press play in Garageband 3 get message "CoreAudio: Disk is too slow. (Prepare) (-10001)" This applies all previous Garageband 3 files and any newly created ones. I cannot play any of them. Can you tell me what this means and how I can fix? Thanks.

I looked at the Activity Monitor and didn't see anything using up resources. I saw disk writes peak out, but nothing to suggest why. I recorded track after track in the same project and finally after the 4th track, it started recording as long as I wanted without a problem. I'm going to chalk it up to disk fragmentation in that particular area.

Repeated Error: Disk is too slow. (Record) (-10005)

Hello brilliant forum users,
I'm using a brand new mac mini with all of the software updated. It's got 2GB of RAM.
I am recording spoken word through a mixer, onto one track (male basic).
There are no other tracks.
I have no other applications open, and the computer has had a fresh boot.
I am getting this error repeatedly, intermittently, with no apparent cause:
Disk is too slow. (Record)
(-10005)
After googling and reading up, I have done the following:
Made sure FileVault is off (it was).
Turned off time machine (I had it on).
In the energy saver preference, deselected 'put hard disk(s) to sleep when possible'.
Still, the error occurred.
Then, I decided to record to my 500GB external (backup) drive, which is connected via usb (I do not have a firewire external drive). I thought, surely this will fix the problem. I made sure time machine was disabled.
Still, the error occurred.
It is totally random, happens at 2 minutes, 20 minutes, or not at all.
I have recording audio resolution set at 'good'.
I am recording via an audio-in (3.5mm I think?) aux cable from an OUT on the mixer.
It seems that I should call apple, but I am at a meditation center in Thailand, and the time difference makes it difficult, not to mention that the computer is in the meditation hall, which makes phone calls difficult.
So, I turn to the trusted experience of YOU!
Thank you very much!
Most appreciatively,
Lizzy

I have also been getting this one intermittently while playing back - sometimes while playing back only one track. Don't know if it's related.
Part of the project was not played
This project has too many real instrument tracks to be played in real-time.
To optimize performance, see the 'Optimizing GarageBand performance' page in GB Help.
hmmm.. that doesn't sound right - and may suggest a software issue.
Have you tried creating a new user account (go to System Preferences, Accounts, and add another account with the "+" sign) and using Garageband from a new account?
Or if that's not working, do a complete uninstall of Garageband...
• trash GB receipts (at the hard drive level)
• trash your Caches folder (at the user level)
• trash all GB preferences (at the user level)
• trash the GB application
... then reinstall Garageband from scratch?
Hope this is helpful!

Core Audio Disk IS Too Slow (Write) (-10002)

Similar Messages

Maybe you are looking for