Error code (-10010) disc too slow or system overload

just used logic pro x yesterday, drummer track works seamlessly, I absolutely love this feature. I have 3 guitar tracks and a bass track with apple plugins (amp). Around the end of the song, it stops and shows the error code mentioned above. The project is on an external hard drive btw. Any resolution  to this error?

What type is your ext drive?
USB2? USB3? FW800? FW400?
5400rpm? 7200rpm?
Green or power saving drive.... or not?
Not just any ext HD will work efficiently....
The recommended types are..
FW800 or USB3 7200 rpm non green or non power saving hard drives that are not partitioned.
Anything else is likely to have performance problems when used with audio work...

Similar Messages

  • 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

  • Disc too slow or system overload - please help!

    I'm doing a very minimal project with 2 voices, and 5 fx tracks - no plug-ins and after I've recorded a few takes I keep getting Disc too slow or system overload (-10010) messages either in record or playback. These messages have gotten more common for me lately, but this project is so small I'm really surprised. I've repaired permissions, rebuilt directory with Discwarrior and have 100 gigs free space on my media drive. Logic 7.2.1.
    Usually I work at 44.1 but this project is 48 (fx tracks taken off CD are 44.1) I don't think it's much of a factor because I'm getting the same message on my regular projects. The audio portion of my CPU meter barely registers, but the disk I/O goes from barely visible to spikes into the red.
    Any help would be greatly appreciated.

    That's cool, Logic has been doing this since at least version 4, and
    it still does it.
    PC, Mac, g3, g4, g5, pentuim, 2, 3, 4. inboard/outboard audio disks, SCSI, firewire, 1gigRAM, 2gigRAM, 8gigRAM.
    "Disk too slow or system overload" <-- funny, I just produced a 30-minute television presentation doing all the video editing on this mac, all the while MAYA was running.
    Yet, Logic gives you the overload message even if there's ONE SINGLE AUDIO FILE in the arrangement!
    It has nothing to do with your buffer settings.
    Even the best outboard audio disks stop spinning after a few minutes.
    Unlike Nuendo and ProTools, Logic doesn't care what your disk is doing when you press play.
    Nuendo and ProTools spin up the disks before attempting to play the file, avoiding the RIDICULOUS error message. Logic just throws its transport into play mode, causing the error message, and causing you to believe your system is inadequate.
    After I write this, I'm going back into Logic to press play. I know as a Fact, I will recieve the ''system overload message''. Been this way since version 4,
    SOLUTION#1: Press 'OK' at the error window, wait a few seconds, then try playing the song again.
    SOLUTION#2: Wait...another ten years?
    SOLUTION#3: Invest in ProTools.
    The 'system overload' excuse is ABSOLUTELY one of those "10 years and still going" screwups in the logic software.
    I still use Logic, and the folks at Logic apparently will always think you're lying when you report an error. buffer settings! <- too funny.

  • 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

  • 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 error-hard drive too slow or system overload (new macbook!)

    have made a few short tracks with logic with no probs. when i have tried to play the demo songs which have many tracks, i get an error msg saying hd too slow or system overload. i have a new macbook, 2.4, 2mb ram, 250 gb hd (with loads space left). airport turned off when using logic. what gives???

    Samples that I am using are located on a 7200 external HD.
    Is your external formatted for Mac? If you didn't buy it from a store that sells mac drives specifically, it's probably formatted for windows. You must reformat for Mac or you'll have a lot of performance issues.
    I've a Macbook 2,2 Ghz Core 2 DUO with 2Go of RAM.
    You should get more Ram, it's really cheap these days.
    Airport is disconnected. My AUdio Buffer is 1024 in the Logic preferences.
    Make sure the I/O Safety Buffer is OFF, and then set the buffer size at 256 or 512.

  • Error Message: Disk too slow or System Overload

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

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

  • 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. (-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 too slow and system overload error

    I like many other users am having problems with the "disk too slow or system overload error (-10010)." It only seems to occur during playback attempts, seeing as I recorded with no problems yesterday, and only began happening today (granted, I have not tried recording anything since this started happening). I have tried changing the buffer size (still occurs at all levels), and, as per noted in a similar post, ensuring that my computer does not at any time put drives to sleep. All my sessions are stored on an external Toshiba Canvio Connect 2.0 TB drive connected directly to my computer via USB.
    My setup (I know that this is going to draw a lot of criticism) is a macbook air with 2 gb 1067 MHz DDR3 ram and a 1.4 GHz intel core 2 duo processor, running OS X 10.9.3. While I am fully aware (I promise) that these are well below the recommended numbers, I have been using this configuration since June without any problems whatsoever.

    Clancy,
    No problem!
    I also added it to the Useful links and resources for Logic Pro X  page in the tips sections....
    Cheers..
    Nigel

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

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

  • 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

  • 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

Maybe you are looking for