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

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

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

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

  • 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

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

  • 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

  • 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

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

  • If statement in DI

    Hi all I'm wondering what the format of IF-ELSE block is in DI. I wan to check validation rules in my query in DI but my IF statement comes with an error. I searched a lot on the Internet but couldn't find the correct syntax. What I wrote is : If dat

  • Problem with nokia store in asha 501

    hi everyone i've had this phone for several months now and as hard as i've tried, i have not been able to access the nokia store and i've tried EVERYTHING. i don't know what the problem is. i can't install any apps on my phone because they can't be d

  • Why does the latest version of Apple TV suck?

    I still have my first Apple TV (1st gen) which is amazing.  I just bought the latest one at xmas.  It was working fine and then asked to be updated.  So, we updated it.  It won't work now.  It asks to be plugged in to iTunes.  And you need a new cabl

  • Metadata over video

    Metadata is a key of FCP X's feature! On metada holding info from camera (name, timecode and other EXIF info), additional data like scene, take, camera angle, also keywords and roles! But how i can publsih some metadata on video? For example timecode

  • X-FI Fatal1ty front pa

    If choose not to install the front panel and only the sound card do i lose any funtionality other that the inputs and outputs on the front panel?will the 3D sound and all of the other high end sound functions still work?Is ribbon cable between the fr