Disk to slow/System overload!?

That is the message i get after trying to play a demo from Logic Express 8. What is wrong please help!

I believe this has been covered before and that you have to copy them to the local disk instead of playing them from the CD/DVD.
P

Similar Messages

  • Disk too slow / System overload HELP?

    I'm really hoping someone can help me out with this!:
    I purchased a G4 PowerBook around six months ago, with Logic Pro pre-installed. Since then, I have mixed and mastered lots of music that was recorded on a previous system and imported. I was running multiple tracks simultaneously with tons of plug-ins and everything ran smoothly on my new Mac. HOWEVER, within the last month, my playback capabilities have been severely reduced. When I try to play back even two tracks simultaneously (with just one compressor or reverb), I get the error message, "Disk too slow / System overload."
    My first reaction to this problem was to check my disk space and see how much room I had left: it turns out I have over one third of my harddrive space still available. I checked my memory capabilities and they seem to be more than adequate. I bought new virus protection, too, and ran scans to see if that might make a difference, but it hasn't. I don't understand why this is happening on a system so new. ANY ADVICE YOU CAN OFFER WOULD BE GREATLY APPRECIATED!
    Many thanks.
    Powerbook G4   Mac OS X (10.4.6)  

    It is generally not a good idea to run logic on the same drive that contains your audio files and samples. Most of the data involved with logic whether it be programs or individual audio files will be saved physically all over the place on your hard drive. At a certain point the actual part of the drive that reads the data will not be able to move around to all the little different audio files it needs to access for the session on top of running the program and whatever other software that is up. It is best to save all your audio files and samples to a fast external drive (7200rpm at least) otherworldcomputing.com has great drives that have high quality cases and the option to put any drive they have in stock into the case. (i would recommend seagate) If you are going to continue running your entire sessions off the internal drive then you need to keep up with your basic mac housekeeping. You should repair your permissions 2 times a month (use disk utility) You should buy a good directory repair program such as disk warrior. The directory is exactly what it sounds like. It keeps track of where everything is on the computer. If your directory is corrupt the computer will have to do an extra manual search to find what its looking for. If your directory is healthy your computer will make a straight shot to the file you are looking for.

  • DISC TOO SLOW/SYSTEM OVERLOAD

    I have read a couple of other posts about this issue and tried their remedies with no success. Has anyone been able to figure this out or have any other remedies? This is getting bad. I play bacy my arrangement and keep getting this Disc too slow/system overload error. It just "came on" out of nowhere. Someone stated about possibly an update in itunes?????? Is there a way to 'uninstall" an update once you have installed it and go back to a previous version?Please help. This is annoying.
    Tim

    What can I say?
    http://support.apple.com/kb/TA24535
    http://support.apple.com/kb/HT3161
    Also: install MenuMeters http://www.pure-mac.com/diag.html#mainmenu to keep an eye on other activities (esp. +memory swapping+ ) of your Mac/OS X (possibly disrupting Logic).
    In Logic, before playback:
    Disable all inputs on audio tracks.
    Freeze/BIP your SI tracks.
    Keep an audio- or aux track selected (or: avoid having a Softw Instrument track selected).
    And:
    Blame the dog.
    regards, Erik.

  • "Disk is too slow/system overload"??? Help!

    Hey
    I'm running Logic Express on a G4 with OS X 10.4.10. My processor is 450 MHz, and my memory is 896 MB SDRAM. When playing back around 6-7 tracks, i get a message saying:
    "CoreAudio - Disk is too slow or System Overload (-10010)"
    or
    "CoreAudio - System Overload. The audio engine was not able to process all required data in time."
    I'm assuming that this has something to do with my processor being too slow, however, according to the logic express requirements, i have much more than required. Or this could be a problem with RAM maybe, considering i only have 896 opposed to the 1000 needed.
    Sorry if this is a noob question, i'm new to macs in general. I'm just looking for answers because this is keeping me from doing what i love. Any answers appreciated!
    Thanks!!
    EDIT: I'm using a presonus firepod for an interface, if that helps.
    Message was edited by: wasco

    I'm not sure where you read the system requirements for LE8, but looking at my box I see that you need a "1.25GHz or faster PowerPC G4 processor (and) 1GB of RAM." Keep in mind that these are minimum requirements.
    Unfortunately, the processor is your main problem . . . LE8 requires a processor almost three times as fast as your 450 MHz. Also, as you pointed out, you don't even have the minimum 1GB of RAM. You do have the proper OS, but I don't know if you have the minimum required 6GB of available disc space.
    Other than upgrading your processor or buying a new computer, the only other suggestion would be to make sure you record to an external drive but I'm not sure how helpful that would be in your particular case.
    I'm sorry I couldn't be more helpful.

  • Disks, demos, and system overloads

    Just upgraded from 7.2 on dual 2.5 G5 with 6 gigs RAM, and moved demos onto the disk. Unlocked them. Try to play and system overload instantaneously (couple seconds). Just trying to play the demo.
    Message indicates my disk is too slow. Just the stock internal disk, but does not seem likely that this is a problem. No other applications are open, and the CPU's are barely used.
    The instructions also indicate that the demo disk is a DVD with a tutorial on it. Cannot locate such tutorial and the disk clearly does not play as a DVD.

    Thanks. System worked fine with LP 7 and the solution here was to erase the preferences folder for Logic. The hard disk meter, playing one of the demos, never exceeds 30% of the length of the meter, and the CPU consumption is evenly split between the CPUs.

  • Logic Pro 8 - same old 'system overload' and 'disk too slow' errors

    I am having serious issues with Logic Pro 8 on my macbook pro. I am running it with a Focusrite Saffire LE firewire interface.
    I am only using it to playback two stereo files, as a backing track and a click for live performance. I can seem to leave it running all day at home without a problem but when I try and use it in rehearsal it trips up either straight away or half way through a track. It gives either 'disk too slow', 'system overload' or 'unable to sync audio and midi' error messages. This is obviously rendering it unusable. I have tried all the usual tweaks associated with this problem but to no avail.
    I am reluctant to believe it is a hardware issue because I have Cubase 5 on the same laptop and that runs like a dream all night without the slightest hiccup. Obviously I have been using that instead.
    Having done many internet searches about this it does appear to be a common problem but with no definitive fix.
    Did anyone else getting these issues ever fix it?

    Jazzmaniac wrote:
    That has nothing to do with logic. If your had disk becomes slow in rehearsals then it's very likely the hard disk acceleration sensor kicking in to protect your drive from damage. Strong vibrations will cause the heads to park, significantly reducing the the seek times and the transfer rates. Jazz
    How does that explain the OP's statement:
    "I am reluctant to believe it is a hardware issue because I have Cubase 5 on the same laptop and that runs like a dream all night without the slightest hiccup. Obviously I have been using that instead."
    I think it has more to do with Logic's disk access and buffering system.
    It's true that vibrations can cause data mis-reads as the drive head has to re-read the data, however part of the problem lies with Logic's buffering. I don't think the sudden motion sensor (sms) is kicking in, just that the drive may be having to re-read data and Logic's buffering system can't handle the slight interrupts.
    I've dealt with the exact same situation locally (for a client), we ended up using an old bass drum case to make a padded rest for the MBP, that eliminated 90% of the problem.
    pancenter-

  • "Core Audio Error Disk Too Slow" On Stage?

    i use logic pro on my macbook pro(2gb ram 2,16ghz) and i'm completely satisfied with this combination.
    Only when i'm playing live(electro music - loud environment - lots of sub/bass etc.) i sometimes get the message disk too slow/system overload, although i'm only playing some aiff files and some softsynths to it...
    is it possible that my external disk(lacie d2 FW400) is skipping due to vibrations or is my Sudden Motion Sensor stepping in? i disabled it already... anyone the same problems or even an answer
    thx in advance...
    Macbook Pro   Mac OS X (10.4.9)   2 gb Ram

    If you can afford it buy one of these http://www.sonnettech.com/product/temposataexpress34.html
    and an external sata drive - sonett also make them http://www.sonnettech.com/product/fusion.html
    Or any external sata drive will work if you only need the one drive. The sonett is good as it does port multiplying meaning you can have up to 10 drives running on your laptop
    Although a quicker and cheaper fix could be to try putting the lacie on some neoprene. - this will cut out "most of the" bass thats transferring from say the stage to the drive, but it wont help if the bass is really loud as it is more than likely the airborne bass that is causing the errors.
    If money is no object the sonnet solution is very good and in theory would be rock solid running in raid and mounted on neoprene.
    Just a thought....
    G5 DUAL 2.7GHZ 4 GIG RAM and G5 DUAL 2.5GHZ running as node, macbook pro 2.33 3 gig ram   Mac OS X (10.4.9)   Yamaha DM2000

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

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

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

  • Logic Pro X - Disk is too slow or System Overload. (-10010)

    Hi there, I'm a professional music user and recently switched from Pro-Tools to Logic due to PT11's lack of third party plug-in support at the moment. I was looking forward to leaving behind the error messages of Pro-Tools for the supposed plain sailing of Logic. However, after installing Logic X and starting a new session with one track of audio and 4 tracks of software instruments, I'm receiving the following error message when attemping to record a part on one of the software instruments. 'Disk is too slow or System Overload. (-10010)'
    I have an 8 core Mac Pro with the latest version of Mountain Lion, 16GB of Ram and a 250GB SSD boot drive (which Logic is installed on). My sessions are ran from a secondary 120GB SSD which has 110GB of free space on it and my sample libraries are streamed from another internal 250GB SSD and a 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5" Internal Hard Drive. My interface is a Focusrite Scarlett 6i6 USB 2.0 and my I/O buffer is set to 512.
    It is completely unacceptable to me that I should be experiencing error messages with this set up and a 64 bit DAW, particularly when the session in question only has one track of audio and one instance of East West's Play engine, spread across 4 software instrument tracks.
    Has anyone else experienced similar problems or have any ideas as to what the solution could be? I'd really appreciate any advice.
    Cheers,
    David

    Just as a quick followup....
    After doing a little research online it seems the Scarlett is one of those USB2 devices that has issues with how Apple changed their implementation of USB when they released Macs with USB3 interfaces and put this updated implementation into Lion and later Mountain Lion... and that this is probably why some people have major issues like the OP is reporting and why other's do not. It depends on the hardware/OS X version combination as to if this issue rears it's ugly head.
    Oddly enough some Win 8 users are also reporting similar issues with the Scarlett for much the same reason.
    The March 2013 Scarlett OS X drivers are intended to 'alleviate' this issue but Focusrite have stated it is only to 'alleviate' in some instances and not completely fix the problem for everyone who has it,.,..
    However, the good news is that Focusrite have released some beta drivers (v1.7b2 and later b3) which seem to work better for some people than the last official release...
    Mac Only.
    General stability/logging improvements:
    - Improved audio stream syncing
    - Fixed bug which results in occasional inaccurate timestamps
    - Improves sample rate switching
    - 18i20 stream formats now switch automatically
    - Fixes Forte streaming at 176.4/192kHz
    You can find them here..
    http://beta.focusrite.com
    Note: These beta drivers again seem to only alleviate the issues for some people and not all but it has got to be worth giving them a try I would think...

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

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

Maybe you are looking for