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

Similar Messages

  • 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 too slow or System Overload" ... hardly

    Hi all!
    I  hung onto my 2007 MacPro until just before summer when I upgraded to be on the safe side. I do orchestral work and have been accustomed to running heavy VSL projects on one single machine pretty effortlessly. On my new 12 MacPro, things are working even smootherEXCEPT for this "Disk too slow or System Overload" happening from time to time on fades. The projects in hich I experience this behaviour are audio only, orchestral mixes of between 60 and 70 audio tracks and I get the message when executing fades on all tracks simultaneously. I can't remember getting this on my old MacPro which had a fraction of the cpu-power and not nearly as much ram.
    My specs are 2x2.66 6-Core w/32GB ram, and all audio files, fade files and othe project files, are written to two 2 TB 7200 disks in the internal disk slots, configured as striped RAID. This gives more than enough speed and I still have 1,64 TB of free space on the RAID set.
    This issue comes and goes and I can't seem to figure out what triggers Logic's problem to read fades fast enough. Just now I had some corrupted fade ailes, rebuildt them and now Logic can't get past the fades at all unless I start playing in the middle of them.
    I can't understand why this problem should be introduced on a configuration much, much faster than my previous MacPro where this problem hardly ever occured. I even doubled the I/O buffer from 512 that I was using on my old mac, to 1024 with no difference at all. Increasing Process buffer size to "Large" doesn't have any affet either.
    Any clues anyone?
    Best regards,
    Ginge

    Good point, nice link!
    But the thing is I'm not using any software instruments and apart from one EQ on a track here and there, two Tube tech plugs and two sends to Altiverb (of which one is inactive). This kind of load was not a problem on the old heap and shouldn't be a challenge for a 12-core... Also, without changing anything apart from the move above, it is now playing with only one pixel-high movement on the meter, like you would expect it to do.
    BTW the quirk is now back on the project that was fixed. I did new fades at another position and CPU 1 is now maxing out again. A new set of fades means equal fades on regions on 63 tracks playing simultaneously.
    As I'm writing I'm becoming aware of one interesting aspect: the project files contains imported aaf data and to save space I'm leaving the media-files at the original location where it was put by Pyramix who exported the aaf. I figure there shouldn't be a difference if the audio files reside in a folder called "Media files" or "Audio files". These folders are sitting on the same disk albeit not in the same subfolder. If anything, I'd assume it would minimize potential for error caused by having several copies of files with identically names on different locations on the disks. But now it seems the issue is less likely to appear if I save the project including assets, copying external audio files (on any disk), or at least that is how it looks like right now. New fades are working fine after I've done this.
    Doesn't make sense to me but it seems to make a difference...
    Ginge

  • Disk is too slow or System Overload Errors(-10010)

    Hi, It may have been a mistake, but for the 1st time in a long time, I updated my system and software two days ago, after which i tried to runm Logic 9. During playback, I am not getting a random error message that "Disk is too slow or System orverload. This is a system that has operated error free for the past eighteen months, no problems, until now! What really puzzles me about this is the part about "motion Sensor" ! My system is a Mac Pro Desktop unit and not a laptop, and definitely not equipped with and motion sensor(s) at least not that I am aware of.
    Can nyone shed some light on this for me?
    Thanks in advance

    Hi
    rockfort wrote:
    Did you repair permissions after the OS update?
    ** I don't know how**
    To repair Permissions, in the Finder, use the Go:Utilities function, and run Disk Utility.
    In Disk Utility, select the boot drive partition on the left and click on "Repair Disk Permissions".
    rockfort wrote:
    Free space on the OS and/or Project drive(s)?
    ** 1.78TB space free on the drive**
    So, are you recording /playing back your projects from your System drive?
    This is not generally recommended. Instead one should really use an second (Project) drive either Internal (no good for an iMac) or external Firewire/Thunderbolt drive (depends which iMac you have).
    Further, the error message you have been getting is a general "Disk too slow" and/or "CPU overloaded" message.
    It would be worth keeping an eye on the System Performance meter in Logic whilst playing the project (Double click on the CPU meter in the Transport or use :Options:Audio:System Performance) to see if it is CPU or Disk related
    CCT

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

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

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

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

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

  • "Disk too slow or System Overload"

    So while I'm doing rather simple things like recording vox or even playback, the audio stops and I get the 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."
    I'm running on Intel Dual Core i5 2.3's, 4 gigs of RAM with about 230 gigs of free space. I have turned the SMS already to it can't be that. Does anyone know what the problem could be?

    CosmicChild wrote:
    Thanks for the reply. Mind if I ...probe... you for some more info?
    Too many CPU intensive VI- what is VI?
    HDDs- what is that?
    thanks you!
    VI = Virtual Instruments.  Logic software instruments or third party software instruments.
    HDD =  Hard Disk Drive
    pancenter-

  • 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

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

  • Disk is too slow or System Overload- error

    After going through the community I found around 91 posts regarding the same problem. Since I was having the problem,hence,instead of fiddling around myself,I took my Macbook Pro and got it serviced at an Apple Authorised Service Station. Got the Hard Disk formatted. Reinstalled Software  OS X 10.8.5 and Logic Pro X. Came home and just dragged an audio file to test, and guess what ??? Nothing has changed.I did not connect any audio interface, did not open any plug ins. Since my HDD is formatted, I don't even have many Apps installed. Just tried to keep everything simple !! This is really frustrating. I lost a project and incurred financial loss because of this.

    Arnab,
    If it were a serious bug in LPX then wouldn't most of us be suffering the same thing? As that's not the case... then it's more likely to be something specific to your system/hardware/configuration
    Now, having said that...  i will say that some people reported issues such as the 'graphical lag' problem.... when they were still using Mountain Lion with LPX but after upgrading to Mavericks/LPX .. the issues seem to basically vanish.... or at least we see very few reports of that problem these days.
    So maybe, you should try using Mavericks and see what happens....
    Note: Mavericks actually places larger demands on the hardware it seems... due to its new graphical routines for example... but it also seems to fix quite a few long standing issues too so it's a bit of a gamble but worth a try I feel... especially as you basically have a clean Mac anyhow.... with little else installed at this stage.
    You can always go back to Mountain Lion if it doesn't work out for you....
    Finally: Apple aren't actually here.. This is a User Community made up of and supported by users just like yourself...  so if you wish to discuss this with Apple themselves, contact them directly....
    http://www.apple.com/contact/

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

  • 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

  • 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

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

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

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

Maybe you are looking for

  • ITunes purchsed book cannot open. Error message: "cannot open format"

    I purchased book on iTunes and now cannot open it. Error message: Format not comparable, Cannot open.

  • Reports server: cannot start stand-alone servers

    I have 9iAS 9.0.2.0.1 on RedHat Linux AS. When I try to create/start a new reports server (using rwserver.sh), I get "REP-50001: Server is initializing", but it never starts. My in-process server works, but I can't create any additional servers. I've

  • Error ora-604 ora-904 invalid column name

    Someone knows how to fix this problem? Error ora-604 ora-904 invalid column name.

  • Uploading the Legacy AUC in Infrastructure

    Hi All, I have to upload the AUC assets from Legacy system to SAP this is Infrastructure project and we are using PI. Please tell me  the steps with T.Codes and i have checked in this forum but i didn't get the proper resolution. Thanks and Regards,

  • Restore lost Address Book contacts

    I lost all Address Book Contacts the first time I tried to sync my iPad2 with my iMac. I have recent Time Machine backups, so I restored this file: username/Library/AddressBook/AddressBook.data from a backup, making sure that Address Book was not run