What am I receiving a message, "disk is too slow (record) (-10005)."

Any answers?

Do you also get messages like:
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.
Then you may simple have too many real instruments tracks and effects, and I'd silence some tracks while editing and quit any other application you do not need, to free more RAM.
But if that is not the case, test, if you have the same problem with other GarageBand projects, or when working from a different user account. If it is a system wide problem, I'd reinstall GarageBand.
Regards
Léonie

Similar Messages

Disk is too slow (Record)(-10004) error..so sick of this.

Hello all,
I can no longer record more than three tracks in logic without getting the error message "Disk is too slow (Record)(-10004)". When this happens, recording is stopped.
At first I suspected my drive was faulty, maybe slowing down. So being in the middle of a session that took me 2 hours to set up, I called for a break and rushed off and bought an external Seagate 7200rpm firewire 800 drive. I installed it and set it as the recording path for the project. There was no change, the same error occured.
I then switched the target drive to another internal one I use for Time Machine - same problem occured.
It seems to me that this problem has nothing to do with my drives. I am at a loss to explain it. I have looked for hours online for a solution but while many have experienced this there seem to be few answers out there.
Unless I find a solution this will be my last project with Logic. I tried and tried for the last 5 years to use this program but things like this keep happening. It's glitchy with UAD cards, Duende, RME interfaces, Midi controllers, Hard Drives, RAM and external clocks. I've had problems with them all over the years. I will most likely switch to Cubase which I feel is inferior for editing and loops, but at least it seems to be stable.
If anyone has any insight I'll try and fix it, but I just can't keep shelling out money for a program that just doesn't work.

I am experiencing a similar problem & have been receiving the same messages, even while recording as little as one track and playback has become an issue as well. However, THIS WAS NOT ALWAYS THE CASE. I have heard of people with this same problem, where they receive this message out of nowhere after logic has been working perfectly for them.
I also would like to note that I am running all settings in logic for optimized recording and playback (audio & buffer settings etc etc etc)
THIS IS NOT A HARDWARE ISSUE, at least in my situation as I am running a fast internal HD & have ample memory. Please reach out if you feel like you have a pragmatic solution to this issue.
This may be a possible lead on the fix... I remember reading this post from a user "soundsgood" in 2008 who was having a similar issue..I don't understand completely his solution, but if someone could enlighten me, I feel that this might be the solution to our issue
+"Okay - forgive me 'cause I'm a newbie on this forum and if somebody else has already figgered this out, I'm sorry.... I've been having the same problem all of the sudden after many years of crash-free and error-free recording. I've read everything. I've pulled my hair out. I've done dozens of clean installs. I've repaired permissions so many times I can do it blindfolded. And sitting here tonight, it dawned on me.... there are TWO places Logic is sucking data from: wherever you've got your SONG files stashed, of course.... but it ALSO NEEDS TO ACCESS THE STARTUP DRIVE (or wherever else you might have your Apple Loops installed). I was watching my drives being accessed during a playback of a fairly complicated tune (most tracks were frozen of course), and both of the afore-mentioned drives were going berserck with accesses. We're all focusing on our dedicated audio drives, but forgetting about our boot drives (where Logic usually resides along with most or all of our loops). I carbon copy cloned my boot / operating system (including Logic) to a different (in my case, an external firewire) drive and the problem disappeared. Could've been because the cloning process de-fragged all the loops & stuff, or maybe my OS just likes snatching its sample/loop info from an external drive. Worked for me... so far....... let me know if it works for others....."+

Why am I getting this error message, "Disk is too slow. (Prepare) (-10001)"

Hello all! I've been using GarageBand for a while now and I've accumulated quite a few files. Along with all of my movies and iTunes library, my internal hard drive filled up rapidly and I didn't catch it. I received a warning message on my screen one day saying that my hard drive was nearly full and I only had a few MB available. I'm using a 150 GB Solid State Hard Disk on my 2009 MacBook Pro (2.6 GHz Intel Cre 2 Duo, 4 GB of RAM). I remembered reading a while back that it's better to use an external hard drive for pretty much everything when using Garageband, so I bought one. I now have a seagate 500 GB, 5400 rpm external (USB 2.0) and I moved ALL of my movies and music over to it. I freed up around 60 GB of space on my internal hard drive in doing so.
So now that I've given you a little background, let me explain the issue I'm having. Before I noticed that my hard drive was full, I started receiving this error message:
Disk is too slow. (Prepare)
(-10001)
Upon receiving this message, I was unable to do pretty much anything in GarageBand. I couldn't listen to tracks, export to iTunes, or do anything! All I'm using GarageBand for is editing. My band and I do all our recording (and mixing) offsite at a separate studio and i just deliver a 2 track stereo signal (L/R) to my MacBook. From there, I just cut the individual tracks from a block of 30-45 minutes of recording because we just record our entire studio session and mix everything there. I pretty much never have more than two tracks and a few effects going at the same time.
After I realized that my disk was nearly full, I consulted my brother-in-law. He's head of the IT Deartpment at a major hospital here in West L.A. and he told me that I may have created a problem with the cache by filling up my internal hard drive and that I may still have issues with performance even after I free up space. He then told me that I may need to reboot my MacBook a few time to "free up the cache" (or something close to that, sorry guys I'm not that tech-savvy). It seems he may have been right, as I'm still experiencing the same issue. I rebooted around 10 times overall to no avail. I'm still using my internal hard drive to store the files that I'm working on (temporarily) because USB 2.0 is way too slow for my liking, when using GarageBand.
I've read quite a few articles on this offering solutions such as:
1. Do a complete Uninstall and Reinstall of GarageBand
2. Clone my hard drive to my external, format it, and reinstall everything back on it
3. Get a hard drive that supports Firewire 800 (The HDD I bought is USB 2.0, but it has two USB cables to increase speed, but I only have 1 port and I tried a powered USB Hub, but this HDD won't work with it for some reason).
4. Use different editing software.
5. Take it to Apple!
Will any of these things fix my problem? Are some better than others? Before I do anything, I wanted to ask this question on the furum to see if anybody had an easier (or cheaper!) solution. Any suggestions, tips, or advice would be much appreciated, as my band is starting to get on my case about finishing our CD! Thanks...

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

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?

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

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. (record) (-10004)

I get Disk is too slow. (record) (-10004) everytime I want to record (vocals) no more than 30 second into it.
I realised that It happens more often when I need a small I/O Buffer Size and not at all when higher. So I started playing around with all those parameter and the Larger Disk Buffer
Small I/O Buffer Size(for recording without delay) works best with the Larger Disk Buffer On (ticked)
Playing back busy mixes with many pluings work better without the Larger Disk Buffer On and the I/O Buffer Size High (1024)
So, my question is... Is this normal procedure or I am just dogging a fundamental problem in Logic?
Feel free to comment/advice/question/etc...
G5-Dual 2.5 Mac OS X (10.3.9) Logic Pro 7.1.1 Edirol FA-101 Firewire 1.5G RAM
G5-Dual 2.5 Mac OS X (10.3.9) Logic Pro 7.1.1 Edirol FA-101 Firewire 1.5G RAM

did you defrag your disk ?
How full is it ?
I could record 54 tracks on my Motu PCI system on a G4 533 MP

Disk is too slow (Record) error message

Hello there.
I've been using GB for 18 months now and have only few issues.
One issue I've had from time to time is an error message during recording. This in the past has meant that unless I'm paying attention to the screen, we can loose an awful lot of material.
It happened again this weekend and I managed to grab a screen shot.
The error message reads
"Garage Band
Disk is too slow. (Record)
(-10005)"
I'm using a 2.4Ghz Intel Core 2 Duo with 4GB Ram.
I'm recording to my internal Hard Drive which has over 90gig of free space.
I'm currently recording through an F-Control Firewire device, but I would also get this error when I used to use USB headsets.
Has anyone seen this error or have an idea whats causing this I'd love to know. Its always a pain having to be conscious that it could happen at any points, detracts from getting into the full flow of the conversation.
Thanks in advance
Matt

I'm using a 2.4Ghz Intel Core 2 Duo with 4GB Ram.
I'm recording to my internal Hard Drive which has over 90gig of free space.
All these data has nothing to do with your disk speed! This is measured in rpm, and an external disk with at least 7200 rpm might alleviate your problem.
What is your disk's speed? And how many tracks are you handling simultaneously?

Error message: "Disk is too slow or System Overload."

When I try to record from the line-in on my MacBook Pro (2.16GHz, 2GB RAM, 100GB 7200rpm HD), I get after some time (that can range from a few seconds to a few minutes) the error message: "CoreAudio: Disk is too slow or System Overeload. (-10010)".
This is weird because I get that error even when recording into an empty project. I have no such error on my old PowerBook G4 (867MHz, 512MB RAM) with the same version of Logic Express (most recent). Both computers are fully up-to-date.
I also get that error on my MacBook Pro very often when I'm working on a project and it's getting pretty annoying, it sorts of halts the process each time...
I also have Mail, iCal and Adium running at the same time as Logic Express, none of which use much CPU so the problem can't realistically be from them...
Any help to resolve this issue or at least shed some light on the potential cause would be greatly appreciated!

Simply having idle applications in the background is probably fine, but I certainly believe that something like Mail checking for new messages in the middle of recording in Logic could cause problems.
I would also check Activity Monitor to see if you have any background processes running that you aren't aware of. My wife's iBook slowed to a crawl once, and I discovered that a printer driver she installed to use a printer at work was using about 80 percent of the CPU.
-Eric

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

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

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" ???

I've been running Garageband happily eversince I bought my iMac 18 months ago, using it to transfer old cassette tapes to the Mac. Then suddenly 2 days ago I got the error message 'Disk is too slow'. Nothing unusual about the tape, just pop group (M People), not 1000-piece orchestra. The 250GB disk has 224GB free space. Tried closing all other apps (I don't run many anyway) but still problem. I need to finish off this copying urgently and I'm slightly desperate. No-one in the Garageband discussions has come up with anything.
No other apps have any problems, but then all the others presumably can control their input speed.
What is the problem causing the message, and how can I fix it? Is it because the disk has become fragmented, and if so is there an equivalent of the PC defrag utility for Mac? If not, what? Please help!!

Even in the PC world, defragmenting is never going to cause a problem like this. Defragmenting gives negligible benefits, at best. In the Windows world, people would be much better off if they forgot words like "defragment" and "registry". They end up either just wasting time or messing around with things they shouldn't be messing around with.
That said, run Apple Hardware Test on your system. The extended tests. That will see if there's anything obviously wrong with your system. If not, take it to an Apple store or AASP in your area, and ask them to run a check of the HDD. I'd tell you exactly what program to have them run, but in my experience you just get blank stares, followed by a second or two of silence, then a quick, "Uh-huh". Meaning they didn't understand a thing you just said. So just tell the person to have the monkeys in the back run tests on the HDD. They should be able to have an answer in a half hour or so.

HT1935 "Disk is too slow or System Overload-" Only 1 soft synth in project

I am getting the message "Disk is too slow or System Overload…" message when trying to playback in Logic Pro 9.1.8. This happens with only one soft synth plug in within any project. I am running Lion 10.7.5 on my Early 2011 13" Macbook Pro, upgraded to 8GB of RAM. This happened before I upgraded the RAM too.
I have checked all of my Logic preferences and they're set to what Apple suggest to keep CPU usage in check.
I have tried turning off my "Motion Sensor" and it still happens, so I don't think it's that.
If someone could advise me on what might be causing this I'd be very grateful.

Hi
Which Soft Synth plugin?
Does the problem happen with all plugs or 1 specific one?
CCT

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.

What am I receiving a message, "disk is too slow (record) (-10005)."

Similar Messages

Maybe you are looking for