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. 

Similar Messages

  • Disk is too slow or System Overloaded ERROR

    I have logic studio and a macbook pro and keep getting the following error message:  Logic Pro:  Disk is too slow or System Overloaded (-10010)  Not sure how to fix it.  Any suggestions?

    It's a bug in logic. It's been there since multicore CPUs came out.
    Try putting your fx on a bus/aux rather than on the same track as the instrument.
    That way it will trick logic into using a different core for the different tracks.
    I've seen this problem on dual quad core CPU mac pros, so it has nothing to do with your CPU performance.
    Also if your recording to the internal harddrive whilst playing back audio from it you might run into problems when using bfd2 or addictive drums or any other large sample library type plugin.
    In my MacBook pro I took the DVD drive out and put in an SSD for the OS in its place.
    I then use the internal mechanical drive for recording and samples etc.
    This solved all my issues and made everything so much snappier.
    It's dead easy to do too. Infact it works so well I'm thinking about getting a standard MacBook pro (so I can do the same thing again) instead of the retina one.
    I'd refuse to buy a retina one until I have seen logic play back  1 instance of bfd2 a few audio files whilst at the same time recording a guitar through amplitube 3. I'm not paying £2000 if it can't do that. (you'll be surprised)
    Like I said my old one couldn't do it due to the overloads you mention until I did the DVD drive swap trick.
    The retina looks good but, 1/4" thinner is one thing, but having to carry leads and adapters for everything it kind of defeats the purpose!
    I would need a thunderbolt to FireWire adapter (which aren't out yet) a FireWire 800 lead and a FireWire 800 to 400 adapter jut to plug my apogee duet soundcard in! ***?
    I'd buy a thunderbolt audio interface but their are no mobile ones. The only ones that are out are large ones for the studio (And mac pros don't even have thunderbolt)
    It makes no sense, no sense at all!
    You couldn't make it up. At least they have dropped the dongle from logic so I can plug my mouse in.
    Emagic should release a pc version again. These quarterly decade updates are getting boring!
    Where's logic X?

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

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

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

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

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

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

  • Disk is too slow or System Overload- error

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

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

  • 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

  • I just installed Lion and the newest version of Logic express 9 (9.1.5) and every time i playback audio I get this error message:  [Disk is too slow or System Overload. (-10010) . Never had any issues before now...

    I just installed OSX Lion (10.7.2) and updated to the newest version of Logic express (9.1.5) on a macbook and every time I playback audio I get this error message:  [Disk is too slow or System Overload. (-10010) The Sudden Motion Sensor may have parked the hard drive head, or the disk performance is not sufficient to read or write all audio tracks, or the system was not able to process all data in time]
    Never had any issues before now... any ideas?

    Have a look into the Preferences folder (YourUserFolder/Libraries/Preferences/) and trash all Logic preferences.
    You'll have to setup the program again.
    cheers
    rob

  • Error message!!!!!Disk is too slow or System Overload this keeps coming up?

    Logic Pro:
    Disk is too slow or System Overload
    (-10010)
    Mac book pro
    10.5.8 OX
    4gigs RAM
    recording to ext 800 firewire drive
    any ideas???

    I am just reposting my response to a similar question because I never found a solution to this problem just a work-around. I would love to know the actual solution.
    I have encountered this issue as well. I never solved the issue but did find a work-around. Unfortunately, this temporary solution may not work for more 'heavy' users then I. Although, many have commented that this issue happens even on small projects (as it did with me also), many usually create much bigger projects and are using the smaller projects just as a litmus test. I qualify this because the work-around I discovered is using USB 2.0 to connect my external HDD rather than either of the firewire ports on the drive. So, for those wanting to create larger projects, this solution may not be an option. I won't delve into the details here, but I will include a link to my thread so you can see all the troubleshooting I did and the suggestions that were offered.
    http://discussions.apple.com/thread.jspa?threadID=2102925&tstart=0
    Or, you can search the forums for error 10010.
    The only other items of note I can think to add at this point is I am still on 10.5.8 not SL. Logic 9.1.1, and I recently increased the amount of RAM to 4G. The work-around has been working for me, and I haven't had time to check that any of these updates fixed the problem. But I will soon and will report any changes.
    I hope this provides some insight.
    Chris

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

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

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

  • Logic 9.1: Disk is too slow or system overload (-10010)

    After updating I kept getting this error: Disk is too slow or system overload (-10010)
    Can't go five minutes without encountering this. I'm in 32 bit mode using record via rewire. It's maddening and I am now kicking myself for updating. The song that's doing this is a song I was using working on the day before I updated. I had no problems then.
    Anyone else encountering this?

    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

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

  • 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

Maybe you are looking for

  • Satellite M30: coloured lines run up and down on display

    Hi there Ive got a problem with the display on my Satelite M30. I can boot into windows fine etc but coloured lines run up and down my display as well as general artifacts. I cant even install nvidia drivers without a blue screen. The strange thing i

  • IDoc to AS2 scenario connection issue

    Hi Experts, IDoc to AS2 scenario. i am geeting below connection  error  while sending data from PI to Third Party Partner.Please help me on this issue i will appriciate you . MP: exception caught with cause javax.resource.ResourceException: Fatal exc

  • Activate Extended Features converting files

    Hi, I'm using Adobe Acrobat 9 Pro Extended to convert to pdf 3D files. We are doing the conversion via Batch Process that executes a sequence and is working fine. The problem is that the generated pdf file has no te extended features activated by def

  • HFM Rules - Variable not working

    Hi, I am trying to setup a rule to calculate using balances from other scenarios. Instead of writing 100's of rows of rules I have created a variable. For some reason the variable is not working as it should. Below is what I have If value="<Entity Cu

  • Finder window at start up

    I've been using Macs since 1993 and got into a work pattern of always having a Finder window open to navigate round the system. So on every re-boot the same Finder window reappered wherever I left it on shut down. With Mountain Lion I find this has c