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.

Similar Messages

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

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

  • 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

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

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

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

  • Two HDD - "Disk is Too slow or system overload"

    I have a White MB C2D 2GHz, 2 GB DDR2 and Logic 7.2.3.
    I wanted to open the session with 44 audio files, but there was an error "Disk is Too slow or system overload. " I found information that I need to replace my standard 5400rpm drive to 7200rpm.
    But first plugged in my portable USB drive that is 5400rpm and copied this Logic project. It works! All OK, but work over USB is very slow.
    I wonder if you really drive on the 7200 exchange will help me.
    Please help.

    el.j-music wrote:
    I have a White MB C2D 2GHz, 2 GB DDR2 and Logic 7.2.3.
    I wanted to open the session with 44 audio files, but there was an error "Disk is Too slow or system overload. " I found information that I need to replace my standard 5400rpm drive to 7200rpm.
    But first plugged in my portable USB drive that is 5400rpm and copied this Logic project. It works! All OK, but work over USB is very slow.
    A 7200 drive may help but then again... the internal drive is what the operating system uses to write swap files and other OSX related tasks. OSX keeps files under 20meg defragmented but larger files are left as is so your audio files were probably copied to various places on the internal drive, not the most optimal for playback.
    I would think a 7200RPM external Firewire drive is your first choice (unless you're using a Firewire audio interface). In that case either a 7200 USB drive or 7200 internal drive would be the way to go.
    See what a few other posters think before deciding.
    pancenter-

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

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

  • 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

  • CoreAudio. Disk is too slow or system overload

    Hi. I am writing you to ask something that might be simple. I am working with Logic 7 pro and with a Powerbook 15 inch, processor 1.25 and ram of 1.25. When I am reproducing some files I got the message:
    Error
    CoreAudio. Disk is too slow or system overload.
    I will appreciate any help
    My mail is
    [email protected]
    Thanx a lot.

    Hmm, I agree with David, get an external firewire drive. I think that the internal disk on your powerbook is 5400 rpm, which can be quite slow. It certainly is not the RAM if you are only running a few tracks. It will probably be the audio data that cannot be read quickly enough by the hard drive. The solution that they might have been about to give you could have been resolution and word length of the audio files you are recording, Are you recording at 44.1khz and 24 Bit? If you are recording higher, try bringing it down if you want CD quality to 24 bits and 44.1khz. Obviously when mastering it it will be dithered, but I, and pretty much everyone else here, would advise recording at 24 bits rather than 16. As for external drives, go for something like 7200 rpm (I think that's what mine are), although you will find faster and much better! I hope this helps, keep asking questions as there are many people here who are very (and much, much more than me hehe) capable of helping you out, and we're all here to learn. Good luck and all the best, Fred

  • 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 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 is too slow or System Overload. (-10010) The #SuddenMotionSensor - CAN I TURN THIS OFF sick of it popping up! any solutions? #logic9

    Disk is too slow or System Overload. (-10010) The #SuddenMotionSensor - CAN I TURN THIS OFF sick of it popping up! any solutions? #logic9
    i have an external firwire harddrive just for the audio projects which is 7200rpm etc and it has 500gb of free space on it!
    i've already tried the pmset -a sms 0 thing, but that is only for laptops, their seems to be no solition for Mac Pro Desktops!
    this is annoying.
    hope someone can help.
    Dan

    and in laptops it is just working for the original builtin HD.
    It shouldn't be there at all.
    you set it off by (copy/paste):
    sudo pmset -a sms 0

  • Garageband system too slow or system overload -10010

    I have a mid-2012 Macbook Pro that's running Yosemite 10.10.2 with 16G RAM and a 498G HD (245G used).
    Since a recent update to Garageband, I have been getting the error "garageband system too slow or system overload (-10010)".
    I don't really use garageband often, but I like to practice vocals every now and then and then play it back to see where to improve.
    Now when I go to play the sound back, I get this error and the program freezes.
    I don't know what to do or what is causing it, some help would be great.
    Also worth mentioning is that the RAM was just upgraded to 16 from 4 (before the update even the 4 would allow play back).
    Thanks in advance.

    I do have file vault enabled, do I need to disable it?
    I am not sure, if it is the problem in this case.  But it has been known to slow audio processing down.
    Can you test this by moving your current project to a folder outside your file vault? For example, to the Users > Shared folder? Or to an external drive, that is connected to a fast port USB3 or Thunderbolt?

Maybe you are looking for

  • Separate CSS files for Differenct Applications in the Same Workspace

    I am working in APEX 4.0, using Theme 4 (Topaz), primarily with the region template "Top Bar." The application I am working on has gotten so large that I decided to break it into two applications. So I copied the original application and then deleted

  • Error in XPRA EXECUTION Phase of Add On installation in SAP sys in SAINT

    Hello All, I have tried to install VERSANH ADD On on my SAP System with SPAM Version 7.00 <0032 kernal level 48. i have run transaction SAINT imported all PAT and ATT files and started the process. now after running around 16 Hrs it is throwing error

  • Bank Reconciliation(EBS)

    Hi, Created 2 vendor invices of 1000 + 2000 issued check for 3000 using bank clearing account -Outchecks. ( Dr vendor Cr Clearing-Outchecks account) On receipt of the bank statemnet Clearing account (Dr Clearing account Cr Bank account) In Subledger

  • Creating a stopwatch in Labview 6

    Good day to all,                          I am trying to create a stopwatch in Labview 6. I'm very new to the program and don't know where to strat. Any help wouold be appreciated. Danien.

  • How to get the Highlighted Item on DataGrid?

    Hello everybody... I've already searched in a bunch of sites and forums, and i can't find anything... I need to get some data on the Highlighted (not selected) Item on my DataGrid (I intend to use MouseOver event)... does anyone have a clue on how to