Disc too slow (-10004)on new G5 with Fireface

Hello
Has anyone experienced or has a solution for the problem I' m having with my brand new G5 dualcore 2,3 with a Fireface 800. All the drivers and software are the latest. The G5 : 2 ata hard discs totally 500gb , 2,5 Ram with Logic 7.1.1
Sample rates 192khz amd 172 khaz are giving with only 2 microphones and nothing else a disc error reading('disc too slow ') . The energysaver is off and processor highest value-put disc sleeping if possible - is off
Anyone a solution?
Thanks
Michiel Megens
G5 dualcore 2.3 Mac OS X (10.4.3) 500 gb with 2,5 gb ram

you probably have your buffer settings too low. in audio hardware and drivers, you should set your buffer to something like 256 or 512 and see if that improves matters.
the next thing you should do is not record at 192kHz. there are very very few conditions under which working at such obscurely high sample rates are worthwhile and will make a valid positive impact on your work. anything short of working in a top level studio with top notch everything, it's just not worth the trouble.

Similar Messages

HT2510 having issues with Garage Band stating disc too slow...i have stopped ALL other apps, restarted and still having same issue....Please help!

i have not been able to replay older Garage Band productions I have done. I got one to play and then when I edited and saved said did i want to save to newer version. I said ok...But getting repeated error that disc too slow and then starts playing in timeline but no audio then says Garage Band not responding.
Please advise...

Just some thoughts: You have an older Mac, so that could be part of the problem. You may have processes running in the background, or perhaps your disk is too full. Look in the Apple Knowlege Base for things like Startup Items, Launch Daemons, etc and see if you have any that you can get rid of. Also check your HD available space. If it's too full, your files are probably fragmented and spread all over the disk, which might make it respond too slowly.

Logic 9 "disc too slow" 2 TB drive for recording audio on Mac pro tower, lots of system HD space 6 gigs ram?????

I purchased a Mac pro tower in 2008 it has a 320 GB system drive with lots of room left I have 2 500 GB drives and just purchased a new 2 TB 7200 RPM drive just to record from Logic onto it. I have 6 GB of Ram. I have been having this problem for years and I'm getting quite sick of it!.. I just set up a new 24 track project and I'm recording into logic via firewire with my Presonus firestudio and 2 digimax FS units at 44.1k and cant even record a few songs without it stopping in the middle of recording. This is sooo frustrating. Imagine when the band comes up with something cool and asks me to play it back and walk up to my $4,000 mac with my $500 worth of Logic to see it say Disc too slow!. I have seen this problem on many forums. Mac needs to fix this!. It makes me want to make a youtube vid of me burning my Mac with lighter fluid in the yard!. I purchased the "best of the best" at the time and Logic wont even work on a brand new Mac pro properly!?.. Cmon Apple help me out here???

Now that I've had time to stew over your comments. I do appreciate what you are saying however there should be another way to remedy this problem without having to purchase anything (ie in the software or an update, new version from apple). I ran a recording studio for Several years. I also did put a lot of thought and research into purchasing my Setup and had many compliments on the sound quality. What I'm saying is that Logic 9 should have no problem functioning on my computer. I think mac has made a poor product. I bet if I purchased the Pro Tools equivalent to Logic 9 that i could record 24 channels till the cows come home and get no errors. What I need to know is if there is something that I havent tried in my settings or software that can fix this. I think 6 gigs of Ram should be more than enough to work with. Here is what Apple has to say:
Minimum System Requirements
2GB of RAM (4GB recommended).
Display with 1280-by-768 resolution or higher.
OS X v10.6.8 or later.
Minimum 3.4GB of disk space. (19GB of optional content available via in-app download).
So why should I have to purchase any Ram when it's supposed to work on only 3.4 gigs?... That's why your answer frustrated me. I meant no personal insult. I just think there has to be a better answer out there. I do appreciate your input though .

RECORDING ERROR MESSAGE-'DISC TOO SLOW'

Every once and a while after I have recorded around 12+ tracks, I get a "Disc too slow" message with a black block at the end of the recording. The black block when played back is just a loud noise. What is this and what setting might I have wrong. I have the new IMac 27" with quad cores. The cores meter is barely moving and I don't hardly have any processors on. HELP.

sand box wrote:
Erik.......do you feel it is better to record direct to my external HD or the Imac HD?
External. IF it is Firewire. USB is less suitable, but it'll do too. The startup disk is also busy handling RAM for virtual memory, so it is doubly stressed when recording to it, and will 'refuse' to record, or drop out, or say "disk too slow" sooner.
What are the best settings for buffer and the other recording parameters?
Depends on your machine; rule of thumb: keep it as low as possible when recording for minimum latency (32, 64 or 128 or 256), and set it higher when playing back, (256-1024) to avoid "system overload".
The best recording format imo is 24 bit/44.1 KHz (or 48 KHz). If you record 10+ tracks that are all subtle acoustic recordings, it may ever so slighly improve sound/mix quality to go with 24/96KHz, but that will also double the overhead for the CPU. And imo the difference even then is hardly perceptible, save for the most highly trained professional ears.
I record basic rock with 16 tracks or less and not overly complicated effects. Also I still don't understand what "flattening" of a track means. Thanx.
Okay, so 24/44.1 is enough for that. Flattening a track means that you make a new audio file (solo the track, and bounce) that includes the plugin effects you applied to it. It is an (old fashioned) way of freeing up CPU (because you can switch off the plugins afterwards and use the 'flattened' audio file).
Freezing provides a better alternative for freeing up CPU though. Look it up in the manual, it is a simple and effective feature.
regards, Erik.

Disc Too Slow Error

hey everyone, im very new to Logic and overall computer based recording. i have a Tascam FW-1804 interface that im using as well as Logic Express 7. im sure this message 'disc too slow error' is fairly common, but what should i do to get rid of this problem? should i get an external hard drive? what settings should i modify to make the program run more smoothly? thanks a lot for any help or advice, i greatly appreciate it.

You definitely need an external hard drive if you aren't already using one. The internal hard drive is already too busy running system processes, and running those plus a logic project is too much work. So you should run logic projects from an external drive that only has that one inparticular job of running the logic project. Also make sure the external drive is AT LEAST 7200rpm if not higher. Also give yourself some headroom and buy like a 500gb external. In my experience, a hard drive performs best when it is less than 50% full, so that's why you should always go a little bit bigger than what you need.
Lastly, you should check out some external firewire RAID striped 0 solutions. This means that there are 2 physical drives that are hooked together in a way that the computer treats it as 1 logical drive. The advantage of this is that the data is split evenly between the two drives and there will be less strain on the drives. Kind of a similar concept as dual core processing in a sense.
The only disadvantage of this is that if 1 out of the 2 drives fail, it's pretty **** hard, if not impossible to get your data back.
What I do is record everything with my RAID because it is a lot faster, and then every once in a while will backup everything to another standard external hard drive.
http://eshop.macsales.com/shop/firewire/1394/USB/EliteAL/
Check out the selection there. I've got the 500GB RAID and a 200gb standard. I have never had issues with them and I highly recommend them.

"Disc Too Slow?" What does that mean?

Recording live horns (blue tracks). Five tracks. Via PreSonus Firebox preamp.
Got a pop-up window: "Disc Too Slow." In the track editor of one track, a solid block of black, taking up about half a measure.
Never seen anything like this before. What does this mean?

I'm recording on my iMac computer. So I presume that's an internal disc.
The tune has five tracks: all real tracks (blue). Recording one track at a time. Coming in via Shure mic into Presonus Firebox preamp. Firewire cable.
Don't know what the speed is. That's one thing I've never even thought of before. Seems that G/Bs settings were everything I needed.
This is a new one to me.

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.

Disc too slow...for two track recording?!

So weird issue popped up at band rehearsal last night...
Hooked up two mics to my Apogee Duet, created a stereo Aux (with compression) routed to a stereo track just record rehearsal for album preproduction
Everytime we'de get 2 minutes into a song Logic would lock up and say "Disk too slow" or "Disc too slow ro system overload"
I have run HUGE sessions in my little project studio with no issue...why can't this handle basic recording tasks? GAH!

fermusic wrote:
IS your Disc the internal System drive with at least 60GB free space? (this is required for Leopard)
Not true. Insane claim. Leopard cannot run from a startup disk smaller than 60 GB? Why do you keep repeating this nonsense, when it has been explained to you by several people, not too long ago? You keep juggling these figures, too.
Here you say it is 100 GB:http://discussions.apple.com/click.jspa?searchID=-1&messageID=7978443
Here you talk of 40%:http://discussions.apple.com/click.jspa?searchID=-1&messageID=8218690
Here it is 1/4:http://discussions.apple.com/click.jspa?searchID=-1&messageID=6840828
Here too (25 %):http://discussions.apple.com/click.jspa?searchID=-1&messageID=8018139
Here's the search I did:
http://discussions.apple.com/search.jspa?threadID=&q=%22free+space%22&objID=&dat eRange=thisyear&userID=fermusic&numResults=30&rankBy=10001
Get your facts together Ferla, or at least do not present them as facts. Because they are not.
This is not a Leopard requirement, it is another 'Ferfetched' fact, or a 'Ferversion' of the truth.
I can Run over than 64 Audio Track project on my old MacBook Black Core DUO 32bit on a USB2 2.5" HD!
Yes, and my daddy is stronger than your daddy too....

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.

How can I get a better driver for my 1394b Hostcontroller in my Macbook pro 2010 to solve the problem, that it is too slow under Windows 7 installed with bootcamp ?

How can I get a better driver for my 1394b Hostcontroller in my Macbook pro 2010 to solve the problem, that it is too slow under Windows 7 installed with bootcamp ?
WIndows can't find a better one than the installed LSI Conformed 1394 Hostcontroller

Read and follow the Bootcamp Installation instructions that you were offered to view when you ran Bootcamp Assistant.
Run Bootcamp Assistant again and select the option to download the Bootcamp Support software. Follow the instructions. Then boot into Windows and install the Windows Support software you downloaded and saved.

Disc Too Slow LE 7I use

I use iMac Intel Core 2 Duo, 2GB, Bus Speed 667 MHz, Processor Speed 2.16 GHz
Today I missed my deadline to 500 radio stations because all day long I saw "Disc Too Slow 10010"
I only used two tracks for a 20 min bulletin. I removed all compression and limiters. I bounced to an Ext HD but no way would this program load.
This question has been asked before but I have yet to find a satisfactory answer (maybe I'm dense).

Hi Ron,
Sorry about your trouble.
You mention bouncing to an external hard drive.
Were you playing the program (the audio in the song) from your Internal system drive?
What external hard drive is it? Are the drivers for it current? Did you replace the cables going to / from the drive to the computer? Did you try a different hard drive?
Sometimes this disk too slow error message happpens when the FireWire buss is overloaded, and not necessarily by the hard drive. Which audio interface are you using, and is it FireWire?
Please, don't tell me you have an M-Audio FW 410 or the like...
Cheers

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.

Keyboard too slow on brand new Satellite C650-179

I got a brand new C650-179 where I have problems with the keyboard.
Basic facts:
Win 7 Home Premium
4 GB RAM
No software additional software installed yet
My problem is mostly related to the n key but also sometimes d key. If I press n slowly with one sec pause there is no problem, but if press n fast it types n and jumps back one step left and sometimes only jumps one step to the left. Similar thing seems to be with my d character, it radomly types z instead of d.
Do anyone know a possible reason for this behaviour except hardware error?
Cheers

I am experiencing the same problem with a brand new C650-15L (allthough other keys). My unit just came back from RMA Toshiba, they replaced the keyboard. The RMA sheet indicates the technician did some test and everything should be OK.
But NOTHING is OK! The same problem still persists. I tried a boot CD and the same problem is there, so it is possibly a controller problem.
This is really disappointing RMA service how did they possibly test the unit without noticing that the problem was still there...
I am now trying the battery-out method described above before contacting support once again.

My macbook is too old to use new iTunes with my iPhone, is there a way around this?

I'm not sure which operating system it is but I bought it in September 2006 if that helps...
Do I really need to buy a new computer in order to sync my iPhone?!

Hi There
To check the version of Mac OS X you're running click on the Apple menu in the top left corner of the screen and select About This Mac. The iPhone 4 requires a computer running Mac OS X 10.5.8 or later with iTunes Version 10.1 or later (http://www.apple.com/iphone/specs.html).
You do not need to purchase a new computer just a new OS if you're running 10.4.x (x is any number). If you're running 10.5.x you just need to run software update to get the latest version of 10.5 and iTunes which the iPhone can be used with.
J.C

Disc too slow flag????

2.8 Ghz I mac:   i7, 8 Gig memory,. I have been having a problem with my Logic program. I have very CPU intensive software programs (drum, sampler, editor software) and record many audio tracks. My logic program constantly stops, freezes or crashes when I am recording audio. I can see on my CPU meter that certain cores are overloading and that the HD bar fills up before the crash and the inevitable "System Overload" - message, indicating that there is a data bottleneck. I have done many things in the program and in my software and in Logic to minimize the problem, following the instructions from Logic support. Please take a look at this link. http://support.apple.com/kb/TS3834. The problem is still there. I know I have a powerful i mac with a fast processor and lots of memory. I think some of the expensive CPU intensive 3rd party software that I recently purchased from Native Instruments (Studio Drummer, Studio Horns, Melodyne) has helped create this problem. I would so much like to eliminate it and I know that thereare studios which run this software successfully in their Logic programs. I record Audio to my internal" WD1001FALS-40U9B0 Media 1 TB HD. The only thing I haven't tried is using a dedicated HD (maybe a firewire SSD?). This solution/suggestion is listed here:
If your projects typically involve many audio tracks, consider a dedicated hard drive for audio. If your computer supports multiple internal drives, then an additional internal 7200 RPM drive would be a good choice. If your computer does not have space for an extra drive, then a FireWire drive may be a good option. Many notebook computers have 5400 or even 4200 RPM internal drives, so using a faster FireWire drive may improve audio track performance considerably. Again, look for a 7200 RPM drive
I don't quite understand the above. Does my i Mac support multiple internal drives? If so, would purchasing an additional 7200 RPM or a SSD HD solve my problem? Could I use it in addition to the drive now installed? If not would it be advantageous to buy a fast external SSD Firewire drive and run my Logic program on that? Willing to spend some bucks to solve the problem. Want a trouble free "running" Logic program that doesn't freeze, crash and/or stop.
Can anyone help me?
thanks,
Jim Roche
[email protected]

Hey Pancenter!
Thanks again for getting back. Yeah. I wish I had stuck with Snow Leopard. Now I've finally got all my 3rd party stuff running on mountainlion....thinking that if it's an "update" than it will be an improvement to my system. Haven't found that to be th case.   So many things with ML run "worse" than before. I fear Logic is also one of them. Maybe they'll do some tweaks and get ML fixed. Would hate to have to reinstall all the stuff I upgraded to ML (printer, Audio Interface, etc. It's frustrating to have tons of great plug ins available for my mix and then not be able to use them due to CPU failure which keep me from doing a bounce without crashing. I'll have to fool around with bussing everything possible and mixing down audio tracks. Yeah the freezing, as you say is a double edged sword. Too much is also CPU intensive. Someone (not a Logic guy however) told me that switching my
Disk Description : WDC WD1001FALS-40U9B0 Media Total Capacity : 1 TB (1,000,204,886,016 Bytes)
Connection Bus : SATA Write Status : Read/Write
Connection Type : Internal S.M.A.R.T. Status : Verified
Partition Map Scheme : GUID Partition Table
internal disk out (description above) and replacing it with a Solid state drive would give me a super fast HD. Not sure however, if this would solve my issues with Logic. Haven't been able to find anyone on the forums who considered or tried this solution. It's not a cheap solution. Those things are expensive. I'd do it if I thought it would work but I'm not sure. Is using a big fast external firewire HD any kind of a solution or is it better to keep the Logic on the internal Mac HD? Oh well! Thanks for your feedback. Happy music making Man!
Jim

Disc too slow (-10004)on new G5 with Fireface

Similar Messages

Maybe you are looking for