Disc is too slow. (record) (-10004) help!!

i got this message the other day for the first time...
CoreAudio:
Disk is too slow. (Record)
(-10004)
i was recording my band with two room mics just for fun the other day and this happened about three times. I was recording straight to the hard drive of my macbook pro because i did not bring my external drive. i was using a firepod connected via firewire 400. i was recording only two channels of audio for the two room mics and no plug-ins except for maybe one EQ on a track. does anyone know about this kind of error message and what it entails?? if i knew how to post a picture i would put up a picture of my audio driver settings. maybe i am doing something wrong there. i was recording our drummers drums the other day with 4 mics equaling 4 tracks and this did not happen, but i was not recording nearly as long. does anyone possibly have any advice??? if i was too vague in description i will answer any questions...

Couple things -
Recording to the internal drive is never a great choice but you shouldn't have problems recording 2 tracks, or even 4. Is you disk getting full? I would try to make sure I have at least 10% of the drive open (4GB free on a 40GB drive, for example).
Check your maximum record time by pressing the "A" key and set it to the lowest usable value. 15 mins. is a good start, esp. if you have limited drive space, like when recording to the internal HD.
Enable the Larger Disk Buffer in the Audio Prefs. This always seems to work for me.
Is all your software up-to-date? Are your fire pod drivers current?
Check your RAM. Apple Menu-> About This Mac -> More info. Bad RAM is a common problem, often overlooked.
That's all I got...
-John

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

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

Error mesaage: disc is too slow

My system keeps stoping and Im geting error message (-10010) disc is too slow or overloaded
whats the fix?

The "disk to slow" error occurs, when GarageBand needs more memory for real time processing.
It usually helps to restart the Mac before recording - this will free all available RAM at once.
And do not run any other applications concurrently, that like to hog memory, like Safair, iPhoto, iMovie.
Is your project on an external drive? Connect the drive to the fastest port you are having. Don't daisy-chain the connection.

?"Disc is too slow" error?

During recording of a song (4 simultaneous real instrument tracks via usb interface) GB cut out on me and left me with the error message "Disc is too slow". Assuming this means the hard drive, does anyone know why this happened or steps to prevent it. We were 4 mins plus into the song, and what we got sounds fine, just got cut off.
I was thinking maybe I need a buffer setting adjustment. I thought I remembered seeing a way to change buffer size in exchange for delay in monitors. I could not find that function when looked today. Any thoughts on this aspect?
Thanks for any help you have

The "disk to slow" error occurs, when GarageBand needs more memory for real time processing.
It usually helps to restart the Mac before recording - this will free all available RAM at once.
And do not run any other applications concurrently, that like to hog memory, like Safair, iPhoto, iMovie.
Is your project on an external drive? Connect the drive to the fastest port you are having. Don't daisy-chain the connection.

Disc is too slow or system overload

"Disc is too slow or system overload"
right in the middle of a project. stupid question. what can i do? won't even play. can't even bounce it.

Was dealing with that, among other system/disk response issues last weekend. This weekend I researched it extensively and found 2 things that, knock on wood, so far have seemed to resolve my issues. One Mac white paper suggested that when using an external drive, you must format it as MAC Extended, and NOT include journaling. This paper was dated in 2006, but the theory made sense to me, so I tried it. BTW, it also emphasizes that you NOT get rid of journaling on the main HDD of the computer. The other thing I stumbled across was a little download calls "ProKitUpdate 4.5". It is supposed to make your 'professional' apps run smoother. I also downloaded and installed that. I then set up a test with 8 inputs, recording at 48K x 24 bit (what I was doing weekend before last), and recorded for about 2 hours. During that test, I had no beachballs, no dropouts, no 'disk is too slow' errors, and as a matter of fact, no errors at all. At this point, I'm feeling more comfortable with the setup, but am still planning on some more testing before I assume the problem won't happen again.
Charley

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.

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?

Code hints interface and compilation is too slow,who can help me?

I used Flashcc to generate the SWC library, after quote the library in my project, the pop-up of code hints interface is very slow (about 30 seconds), and the project compilation speed is very slow.It is unbearable！is there any method can improve the situation?thank you!!

Sounds like you might have a configuration issue on the o/s side.
Check that kernel parameters are set as recommended in the installation guide
The first thing that came to mind after reading the problem description was that you might have too low SHMMAX for that 10GB SGA, which would cause multiple shm segments to be created and thus explain the performance degration you're experiencing.
A quick way to check if that's the case would be doing "ipcs -m" to see if there are multiple shm segments when SGA is set to 10GB.

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

"disc is too slow or system overload" -- L8 and Leopard

Hi all, I'm mixing something on Logic -- a two track piece, one an a Addictive Drums drum track, and a bass with some effects from Guitar Rig 3, and L8 keeps freezing during playback with the message above ("disc to slow or system overload.") This never happened to me before. Can anyone suggest a culprit and solution?

yeah ...i've always had a dedicated firewire audio hard drive so i don't think its that....i think its the software instruments and 3rd party plugins....they're probably draining more power than usual<</div>
Right, the external hard drive only makes a difference with audio tracks.
although Addictive drums might be streaming samples from the hard drive.
You say the instruments and plugins might be draining more power than usual? Perhaps it's Logic 8 and Leopard using more CPU power than Logic 7 and Tiger. Have you had the CPU/Drive performance meters visible when the overload message appears? Is it the CPU meter that's spiking or the drive meter?
pancenter-

"Disc is too slow. Prepare 100001" message??

Using GarageBand has caused me a few crashes lately and I am getting the above error message frequently. Is my Mac about to break? Thanks in advance.

We see a similar message all the time over in the Logic audio forum. Garageband is a subset of Logic Pro using the same basic underlying technology.
This usually means that the program cannot pull all of the data (audio samples or recorded audio) off the disk in time. However, it can also mean that the CPU was tied up with DSP processing (reverb, chorus...etc) and couldn't devote enough cycles to handle Input/Output without a data error.
It can also mean your hard drive is running low on free space
As Douggo mentions.... it would be helpful to know more about the Garageband song that's causing this to happen.
One thing you can do is set the audio buffer to a larger size... with in Garageband is called, Optimize for more tracks... or something like that.
pancenter-

Large File Encryption is Too Slow!! Help

I am trying to write some methods to handle encryption of zip files, most are very large (over 200 mb). At first it was attempted to load the file into memory, create a Base64encoded string and encrypt that back out to a file. But not nearly enough memory to do that, and generally as files get larger, it would not be possible to support that. So instead I am opting for something like CipherOutputStreams, read in, write out without buffer. on Small files, this is great (smaller than 1 mb) as it happens instantly. But when it get up to the 200MB minimum size of our zips, it takes hours. Is there any way I can speed this up? (See code below)
import java.util.*;
import java.io.*;
import java.util.zip.*;
import javax.crypto.*;
import javax.crypto.spec.*;
public class EncryptedZipUtil
private static final String ALGO = "DESede";
private static final String CIPHER_ALGO = "DESede/CBC/PKCS5Padding";
private static final byte[] IV_PARAMS = new byte[] {
          127, 111, 13, 120, 12, 34, 56, 78
private static final String ENCODING = "UTF-8";
private static final byte[] ENCRIPTION_KEY = "Encryption key must be at least 30 characters long".getBytes();
private static Cipher getCipher(int mode) throws Throwable
      DESedeKeySpec spec = new DESedeKeySpec(ENCRIPTION_KEY);
      SecretKeyFactory keyFactory = SecretKeyFactory.getInstance(ALGO);
      SecretKey theKey = keyFactory.generateSecret(spec);
      Cipher dcipher = Cipher.getInstance(CIPHER_ALGO);
      IvParameterSpec IvParameters = new IvParameterSpec(IV_PARAMS);
      dcipher.init(mode, theKey, IvParameters);
      return dcipher;
public static ZipInputStream getDecryptedZipStream(File f) throws SecurityException, IOException
    FileInputStream fin = new FileInputStream(f);
    return new ZipInputStream(new CipherInputStream(fin,getCipher(Cipher.DECRYPT_MODE)));
public static void streamEncryptZipFile(File zipFile, File outzip) throws Throwable
    FileInputStream fin = new FileInputStream(zipFile);
    CipherOutputStream cos = new CipherOutputStream(new FileOutputStream(outzip),getCipher(Cipher.ENCRYPT_MODE));
    while(fin.available() != 0)
      cos.write(fin.read());
    fin.close();
    cos.close();
public static void streamDecryptZipFile(File e_zipFile, File outzip) throws Throwable
    CipherInputStream cin = new CipherInputStream(new FileInputStream(e_zipFile),getCipher(Cipher.DECRYPT_MODE));
    FileOutputStream fos = new FileOutputStream(outzip);
    int the_byte = -1;
    while((the_byte = cin.read()) != -1)
      fos.write(the_byte);
    cin.close();
    fos.close();
public static void main(String[] args) throws Throwable
    EncryptedZipUtil.streamEncryptZipFile("D:\\ziptest\\original.zip","D:\\ziptest\\encrypted.zip");
    EncryptedZipUtil.streamDecryptZipFile("D:\\ziptest\\encrypted.zip","D:\\ziptest\\decrypted.zip");
}Like I said, the code here works great with small files. Quick, correct and simple. My Machine is 2.8ghz P4, with 1024mb Ram, and when I run this on my larger files, it uses 99% CPU and no memory in addition to the standard JVM Heap.
Any advice would be greatly appreciated

Nice answer, but for additional duke points I've though of an issue with it: although this defeintly speeds up encrypt/decrypt time, there is no longer any way for me to access this file as a stream directly: if you see the method getDecryptedZipStream(File f), since the file is generally a zip, getting a stream in this manner wont work if we want to thumb through the contents and extract entries on the fly, because now the encryption is done in chunks rather than by bytes which the underlying stream would be should we want to browse the zip. So this solution doesn't solve all aspects of the issue. My alternative was then to imagine that I would enncrypt the individual contents of the zips prior to zipping and leave the zip intact. I could the browse the zip but can not access any of the data without decrypting each file first. I don't know if that is the best solution as of yet.

Logic Express "disk too slow or system overload"

Hello,
I'm brand new to all this and have just started going through the tutorials that come on the DVD with the Mark Sitter book for Logic Pro and Express. i have a brand new MacBook Pro and can't seem to get beyond the first ten seconds of the demo song without it bogging down with an error message that reads "Core Audio: Disc is too slow or system overloaded. (-010010)". The funny thing is that the CPU meter is barely registering any activity. Any words on this for a rookie?
Thanks.
Darthpolski

I found some Hard Drives that seem to be super small and FW800 with a rotational speed of 7200. They're made by a company called GTech. i think it's called the Mini. Has anyone had any experience with these for my application? I have a Lacie but was hoping to keep the system a bit more concise.
Thanks,
Darthpolski

Logic 9 "disc too slow" 2 TB drive for recording audio on Mac pro tower, lots of system HD space 6 gigs ram?????

I purchased a Mac pro tower in 2008 it has a 320 GB system drive with lots of room left I have 2 500 GB drives and just purchased a new 2 TB 7200 RPM drive just to record from Logic onto it. I have 6 GB of Ram. I have been having this problem for years and I'm getting quite sick of it!.. I just set up a new 24 track project and I'm recording into logic via firewire with my Presonus firestudio and 2 digimax FS units at 44.1k and cant even record a few songs without it stopping in the middle of recording. This is sooo frustrating. Imagine when the band comes up with something cool and asks me to play it back and walk up to my $4,000 mac with my $500 worth of Logic to see it say Disc too slow!. I have seen this problem on many forums. Mac needs to fix this!. It makes me want to make a youtube vid of me burning my Mac with lighter fluid in the yard!. I purchased the "best of the best" at the time and Logic wont even work on a brand new Mac pro properly!?.. Cmon Apple help me out here???

Now that I've had time to stew over your comments. I do appreciate what you are saying however there should be another way to remedy this problem without having to purchase anything (ie in the software or an update, new version from apple). I ran a recording studio for Several years. I also did put a lot of thought and research into purchasing my Setup and had many compliments on the sound quality. What I'm saying is that Logic 9 should have no problem functioning on my computer. I think mac has made a poor product. I bet if I purchased the Pro Tools equivalent to Logic 9 that i could record 24 channels till the cows come home and get no errors. What I need to know is if there is something that I havent tried in my settings or software that can fix this. I think 6 gigs of Ram should be more than enough to work with. Here is what Apple has to say:
Minimum System Requirements
2GB of RAM (4GB recommended).
Display with 1280-by-768 resolution or higher.
OS X v10.6.8 or later.
Minimum 3.4GB of disk space. (19GB of optional content available via in-app download).
So why should I have to purchase any Ram when it's supposed to work on only 3.4 gigs?... That's why your answer frustrated me. I meant no personal insult. I just think there has to be a better answer out there. I do appreciate your input though .

Disc is too slow. (record) (-10004) help!!

Similar Messages

Maybe you are looking for