"Disk too slow or System Overload" ... hardly

Hi all!
I hung onto my 2007 MacPro until just before summer when I upgraded to be on the safe side. I do orchestral work and have been accustomed to running heavy VSL projects on one single machine pretty effortlessly. On my new 12 MacPro, things are working even smootherEXCEPT for this "Disk too slow or System Overload" happening from time to time on fades. The projects in hich I experience this behaviour are audio only, orchestral mixes of between 60 and 70 audio tracks and I get the message when executing fades on all tracks simultaneously. I can't remember getting this on my old MacPro which had a fraction of the cpu-power and not nearly as much ram.
My specs are 2x2.66 6-Core w/32GB ram, and all audio files, fade files and othe project files, are written to two 2 TB 7200 disks in the internal disk slots, configured as striped RAID. This gives more than enough speed and I still have 1,64 TB of free space on the RAID set.
This issue comes and goes and I can't seem to figure out what triggers Logic's problem to read fades fast enough. Just now I had some corrupted fade ailes, rebuildt them and now Logic can't get past the fades at all unless I start playing in the middle of them.
I can't understand why this problem should be introduced on a configuration much, much faster than my previous MacPro where this problem hardly ever occured. I even doubled the I/O buffer from 512 that I was using on my old mac, to 1024 with no difference at all. Increasing Process buffer size to "Large" doesn't have any affet either.
Any clues anyone?
Best regards,
Ginge

Good point, nice link!
But the thing is I'm not using any software instruments and apart from one EQ on a track here and there, two Tube tech plugs and two sends to Altiverb (of which one is inactive). This kind of load was not a problem on the old heap and shouldn't be a challenge for a 12-core... Also, without changing anything apart from the move above, it is now playing with only one pixel-high movement on the meter, like you would expect it to do.
BTW the quirk is now back on the project that was fixed. I did new fades at another position and CPU 1 is now maxing out again. A new set of fades means equal fades on regions on 63 tracks playing simultaneously.
As I'm writing I'm becoming aware of one interesting aspect: the project files contains imported aaf data and to save space I'm leaving the media-files at the original location where it was put by Pyramix who exported the aaf. I figure there shouldn't be a difference if the audio files reside in a folder called "Media files" or "Audio files". These folders are sitting on the same disk albeit not in the same subfolder. If anything, I'd assume it would minimize potential for error caused by having several copies of files with identically names on different locations on the disks. But now it seems the issue is less likely to appear if I save the project including assets, copying external audio files (on any disk), or at least that is how it looks like right now. New fades are working fine after I've done this.
Doesn't make sense to me but it seems to make a difference...
Ginge

Similar Messages

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

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

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

Logic Express "disk too slow or system overload"

Hello,
I'm brand new to all this and have just started going through the tutorials that come on the DVD with the Mark Sitter book for Logic Pro and Express. i have a brand new MacBook Pro and can't seem to get beyond the first ten seconds of the demo song without it bogging down with an error message that reads "Core Audio: Disc is too slow or system overloaded. (-010010)". The funny thing is that the CPU meter is barely registering any activity. Any words on this for a rookie?
Thanks.
Darthpolski

I found some Hard Drives that seem to be super small and FW800 with a rotational speed of 7200. They're made by a company called GTech. i think it's called the Mini. Has anyone had any experience with these for my application? I have a Lacie but was hoping to keep the system a bit more concise.
Thanks,
Darthpolski

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)

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.

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.

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.

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

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

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 too slow or System Overload" ... hardly

Similar Messages

Maybe you are looking for