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

Similar Messages

  • 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

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

    Yes I have searched but I couldn't find an actual solution to get logic to stop doing this every other minute (literally). I used to think the 'smart' snap feature was the most annoying thing in logic, but this waaaaaay surpasses it.
    Anybody found a solution yet?
    Logic 9.1.0 32 bit.

    The thing to remember is that the infamous 'disk too slow' or 'CPU too slow' error messages aren't just some random bug that needs fixing. They are actually warnings that are there for a reason. You'll get them in any DAW - or any kind of audio or even video application - that needs to do a lot of disk read/writes and CPU work in realtime. There is plenty of advice out there on how to optimize your system to get it to perform as best as it can (even in the Logic documentation), but there is obviously a physical limit to how many tracks and plug ins you can use. When you hit this limit, then all the warning is telling you is that your drive or CPU are actually too slow for the task at hand. At that point, there are other workarounds (like freezing tracks, adjusting buffer and other settings, or bouncing subgroups etc) to keep you working. In some cases it might mean that your work is beyond the capabilities of the machine you're using, in which case considering getting a faster Mac and/or faster hard drive(s) is the next solution.
    Another thing to keep in mind is that Logic uses a kind of resource optimization process, built in to the audio engine. This means that sometimes you'll get a 'disk too slow' error in some part of your song, but when you play through that part a second time, you don't get the error again. This behaviour is markedly different to how other DAWs work, notably ProTools, where the disk and CPU resources are pre-allocated to guarantee performance up to a pre-defined maximum limit of tracks.. The upside of Logic's dynamic engine is that it allows Logic to squeeze out every last drop of power it can get it hands on, by not doing any processing on tracks that aren't playing audio at a given time. But the downside is that you can get CPU or disk too slow errors at seemingly random places. It can be confusing to see a disk too slow message when playing a certain passage, and then not seeing it again in exactly the same passage later.. leading to people wondering if it truly is random, and a bug. But it isn't a random bug, it's just the way Logic handles audio in an effort to get the highest track count possible at any given time.
    Btw, @ fuzznormal: While I agree with pretty much everything you said, you make it sound like a MacBook Pro's internal drive is slower than it really is. Honestly, even if you have put in dedicated SATA II cards or some kind of decent SCSI in your G4, the system buss alone on those old machines is at least an order of magnitude slower than the system buss on any current Mac.. It creates a pretty formidable bottleneck which wipes out a significant amount of any speed advantage the G4 with dedicated drives might have over a MacBook Pro using its humble internal. I (like everyone) used to have a snazzy G4 with a fast SCSI card (I think it was SCSI anyway), and there's no way I could get anywhere near as many tracks running as I can now on my MacBook Pro using the internal drive. Of course I don't usually use the internal drive for audio, but on the occasions that I've had to, it happily chugged out more tracks than my old G4 could, with very rare disk overloads.

  • 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

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

  • 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

  • I'm running Mac OS X version 10.6.8 How come I get this error message "You are running an operating system that Photoshop no longer supports. Refer to the system requirements for a full list of supported platforms." When I Try to download a FREE trail?

    I'm running Mac OS X version 10.6.8 How come I get this error message "You are running an operating system that Photoshop no longer supports. Refer to the system requirements for a full list of supported platforms." When I Try to download a FREE trail?

    Hi Brizill,
    Please refer to the help document below to understand the technical specifications for the same:
    System requirements | Photoshop
    Regards,
    Sheena

  • Hello i have an iphone 4 its stuck in the apple loop. when ever i unplug it from the computer it shuts down and when i plug it in it shows me on itunes its in recovery mood and every time i click restore i get this error the iPhone could not be restored.

    hello i have an iphone 4 its stuck in the apple loop. when ever i unplug it from the computer it shuts down and when i plug it in it shows me on itunes its in recovery mood and every time i click restore i get this error the iPhone could not be restored.an unknown error accurred (2001)

    Error 1 or -1
    This may indicate a hardware issue with your device. Follow Troubleshooting security software issues, and restore your device on a different known-good computer. If the errors persist on another computer, the device may need service.
    http://support.apple.com/kb/TS3694#error1

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

  • CoreAudio: Disk is too slow or System Overload. (-10010)

    I keep getting this error when I'm playing a song that has 16 tracks and effects on each track, but each track is frozen (!): CoreAudio: Disk is too slow or System Overload. (-10010). I'm running a G4 and have 2G RAM. Is this common? What can I do to prevent this? Thanks for any advice you can give!
    -David

    In addition to Rohan's suggestions you have more options depending on how you work and what phases of the project you are in.
    Something overlooked very often is polyphony enabled for the EXS24-some patches are set to 64 drop the polyphony to either the minimum you will need or less (if less you will notice older notes cutting out-but you can set it to the necessary number upon bounce or export). Some mono patches from sound designers are set to 32 or 64-even if you enable unison this is often worthless.
    Up your buffer size-I usually have my PBook at 512-I usually do offline editing, location recording and sound design with the book anyways.
    Export the track.
    Set virtual memory in EXS prefs to 'on' and with the largest RAM allocation-slow disk, lots of activity.
    If you use certain exs patches often but only parts of them trimming the excess off the instrument can improve performance. If you have a piano program with good samples you can initially create a lite version with 2 velocity layers and then when it is time to get things sounding good revert the instrument to the original 5 layer-obviously this makes a huge difference depending on what you are using the piano for, leave it if it is critical.
    Save the Channel strip and export as audio file while keeping the sequence in your session. Like Freezing but you can manually trim the file start position and set the bit depth. Freeze files render from the start until the last audible sample and then truncate the tails, meaning even if you can't hear it it is still pulling "silence" from disk as long as there is sound after it. Exporting as 24 or 16 bit will effectively reduce your file size by 25 (24bit) or 50 (16bit) percent. If you know you don't have to edit a performance for weeks to come exporting it will solve alot of problems for CPU.
    Someone should back me up on this one but at the moment I want to say EXSamples load into memory regardless of freeze settings-reducing your resources.
    Disable the filter (if live or playback-N/A with Freeze)-it is often not critical for some patches. The more synthetic sounds or sounds with fewer/shorter samples rely on them.
    Disable Unison.
    Most sample libraries were not recorded at 88/96k-there is no benefit in running them in sessions in these Sampling rates as far as the EXS sound quality goes.
    That should keep you busy for a while, just some tuning to up your system performance.

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

  • Every time I download anything I get an error message stating ...could not open ....dmg because it is either not a supported file type or the file has been damaged." What do I need to do to fix this problem?

    For the last month or so, every time I download anything I get an error message stating "........could not open ...... .dmg because it is either not a supported file type or because the file has been damaged...." I do not know what to do to fix this issue. Any ideas?

    hmmm.... try this
    basic troubleshooting:
    Repair Disk Permissions http://support.apple.com/kb/PH5821
    Repair Disk http://support.apple.com/kb/ht1782
    reset ACLs http://osxdaily.com/2011/11/15/repair-user-permissions-in-mac-os-x-lion/

  • 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. (-10010)" errors with Snow Leopard

    Since upgrading to Snow Leopard, I have been getting these error messages while using Logic Express and GarageBand. At first it seemed like a problem with the latest update to Logic Express 9, but then it started happening with GarageBand. I have been on the Logic discussion forums, but this really seems like a Snow Leopard problem. Anyone else out there having similar problems and know of any fixes?
    Thanks.

    It's a new IMac purchased in July with a 345 gig drive, with 278 gig available. I'm recording to the internal drive.
    It has a 2.8 GHz Intel Core 2 Duo processor and I had extra memory installed when I bought the machine, so it has 4GB. I don't know how many partitions on the hard drive.
    (Sorry, I'm a relatively new PC-to-Mac convert)

Maybe you are looking for