Combo Remapper - use score text and symbols to switch articulations
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Logic 9 Error Message Disk is too slow or System Overload. (-10010)

Discussion in 'Logic 9' started by Damian Clarkson, May 19, 2013.

  1. Damian Clarkson

    Damian Clarkson New Member

    Hi,
    I've been using logic 9 for about 2 years now and every now and then I go through these frequent stages of getting this 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
    The song I am working on at the moment has 14 tracks and only 4 of them have plug ins on them, 3 of which are just the basic EQ one. I use mainly outboard effects so there should be barely any load on the computer except for playing back the track.
    I've frozen the tracks, tried changing the settings in the preferences, buffer size etc. I've scoured the interent for something which could be causing this in my system but can not find an answer. I have even tried turning off this motion sensor function through advice from the apple page but I couldn't do that. Any help would be much appreciated.
    I have a MAC PRO 2.8GHZ Quad-Core Intel Xeon
    with 8 GB 1066 MHZ DDR3 memory
    Thanks, Damian
     
  2.  
  3. gdoubleyou

    gdoubleyou Senior member

    Usually caused a slow, nearly full hard drive or recording to the system drive.

    But since you have a mac pro I don't think that's your issue.

    If your machine supports multi-threading, in the audi preferences try setting processing threads to 8.

    :thmbup:
     
  4. Damian Clarkson

    Damian Clarkson New Member

    Thanks for that. I tried changing processing threads to 8 at that still didn't work. The only thing that has worked so far is copying all the files and starting a new session. Even still this only seems to work for a while.
    Are there any reasons why this would be...?
    Thanks, Damian
     
  5. gdoubleyou

    gdoubleyou Senior member

    How much free space do you have on your system drive? free space on project drive?

    And is your system drive a stock Apple drive?

    :cool:
     
  6. Damian Clarkson

    Damian Clarkson New Member

    Hi,
    I have 1.47 Terabytes on my system drive and 1.39 Terabytes free on my other drive which is only for audio. So everything I record and all related files are saved on that and nothing else.
    It is a stock apple drive, as far as I'm aware. I had it built by the shop I bought it from which was an Apple reseller.
     
  7. Eli

    Eli Senior member

    The general rule of thumb is that you should always leave at least 10% of the system disc free (for background use by the system: i.e.: scratch disc files, swap files, virtual memory, caches, etc)

    But for a project drive, I think you should be okay leaving it fairly close to full; of course ensuring there is sufficient space for the record time multiplied by the number of tracks you need to record simultaneously.
     
  8. peterlemer

    peterlemer Senior member

    I have the same problem. Plenty of RAM plenty of free space on both system and project drives. All instrument samples are drawn off a 3rd drive, which is a velociraptor. Could it be related to buffer size? Mine set to 256

    pete
     
  9. peterlemer

    peterlemer Senior member

    no, changing buffer size didn't help, playback stopped, I got another Sudden Motion Sensor alert. My Mac Pro doesn't HAVE a sudden motion sensor, does it? What's going on???

    client not happy

    pete
     
  10. peterlemer

    peterlemer Senior member

    I need to know more about controlling which cores are used for my project. I see one or two max out, and Logic stops, while other cores are unused. I'm sure there's an art to this.
    any pointers would be appreciated.

    ( ample spare HD space and speed, ample RAM.)

    pete
     
  11. CCTMusic

    CCTMusic New Member

  12. peterlemer

    peterlemer Senior member

    thanks CCT, some useful tips there

    > http://support.apple.com/kb/HT3161
    although I am experiencing overload without any master output plugins, this caught my eye:
    " keep a track that uses an Audio channel strip selected in the Arrange window, unless you're actively playing or recording to a Software Instrument."

    http://support.apple.com/kb/TS3834
    Suggests that I increase/decrease buffer size according to whether I am mixing or recording. TBH I've increased the buffer to max, and still get the problem, and in any case switching buffer size takes time that I can ill afford.
    It also suggests disabling software monitoring, which I will test.
    I'll look at track freezing, something I haven't used before.
    I'll try voice limiting software instruments, although my main hog is Synthogy Ivory, and I don't really know what voice limiting does to its background processes.
    I'll switch process buffer from medium to large.
    Virtual Memory: what it says about EXS24 is interesting, but I use Kontakt instead. Does anyone know if that uses VM?
    I'll also test 'Sample Accurate Automation' to OFF. At this point I've no idea what difference it might make.

    http://support.apple.com/kb/HT4426

    > open the expanded System Performance meter by double-clicking the System
    > Performance meter in Logic's transport.

    doesn't seem to be available in Logic 9.1.8. What's the 'expanded System Performance meter? I get a meter via menu/options/audio/System Performance.

    anyway, many options here, so thanks :)

    pete
     
  13. charlie

    charlie Senior member

    This has been a known error code for as long as I've been on this forum.
    It's one of those strange "software burp" issues that you just hit ok and keep going.
    Annoying? Sure.
    But it's been around for a long time.
     
  14. SorteAllan

    SorteAllan New Member

    SSD to solve problems?

    Hi.

    I've considered buying an SSD harddrive which doesn't work with a Sudden Motion Senser which often seems to be the problem.

    If you replaced your standard harddrive with an SSD, wouldn't that mean you'd get totally rid of the "Sudden Motion Sensor parked your harddrive" alert message?
     
  15. mt100uk

    mt100uk Senior member

    Maybe, but remember that the error code is suggesting this *might* be the problem. Personally I think it's a caching problem with logic. That said, using SSDs will improve your performance and in my case it does ameliorate this error. Personally I think it's like a car with the handbrake on, if you apply enough power it doesn't matter if its on or not!
     
  16. TmHuud

    TmHuud Member

    fwiw since i bought all ssds for the mac this problem that plaqued me since the dead sea scrolls were written has vanished.
     
  17. mt100uk

    mt100uk Senior member

    I find I still get surges and spikes on the HD and CPU meters, not enough to trigger an error or stop the audio engine but enough to make me think there is still an issues, the level will run up to the highest reading on the HD meter playing 2 audio files (at 48/24) on a quad 3.4 iMac with SSD audio drive (via TB), surely that's not right? The weird thing is it responds just the same (and doesn't die) with 60+ audio tracks and loads of plugs. NB this is on logic 9, I'm still not having similar issues on X, although I haven't got any projects *that* complicated yet.
     
  18. Atlas

    Atlas Senior member

    That will definitely help in many situation but is not a fullproof warranty...
     
  19. Atlas

    Atlas Senior member

    Logic always had problem with managing CPU resources. Since I updated to ML the problem seems to have noticeably decreased. I didnot try with LPX yet.
     

Share This Page