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)  

Similar Messages

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

  • Core Audio : Disk too slow (prepare)

    Can anyone help me. I have created a track that will not bounce
    because it always comes up with this error message: Core Audio: disk
    too slow (prepare). I cannot bounce tracks individually for the same
    reason. I have tried deleting some tracks that i dont need but it still does
    the same. I have 700 and something ram. Is this not enough. I have
    logic pro 7.1 and am using a few ultrabeats in the song. Know Any
    tricks i can get around this problem easily with. Any help would be
    greatly apreciateddd. thanx in advance.

    The drives in the rear positions are on an ATA-100 Bus, those in the front are on an ATA-66 bus. The CD is on an ATA-33 bus, and no Hard drives should be sharing the CD cable. ATA-66 and ATA-100 are plenty fast enough not to be a bottleneck, as long as you are not experiencing low-level correctable Disk Errors.
    A Disk Error will result in retries, both Hardware and Software, which often produces the data, corrected, after a delay.
    My recommendation would be to find a time when you can back up all data from the troublesome drive, and take the \[several hours] to Initialize with the "Zero all Data" option. This writes Zeroes to every data block, then does a read-after-write to check the data.
    If the Drive's error correction was required to recover the just-written zeroed data, that block is declared bad, and the drive will make a near-permanent substitution of a nearby spare block for the one found defective. This process has the effect of laundering out marginal blocks and returning the drive to "factory fresh" condition of all good blocks.

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

    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-

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

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

    I've read most of the reports from previous versions -relating to ibook disk speed and how an external fire wire drive is the way to go, so I got one, how do i set up Garage band to record to it, i can see it on the dt, but I'm still getting the same error while recording one live basic instrument track, no effects, off a 16 track mixer (tape out signal) (live band performance)

    how do i set up Garage band to record to [the external hard drive]
    You create your project on it, or copy your project to it and open that copy.

  • 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

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

  • 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

  • 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

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

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

Maybe you are looking for