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

Freeze files are continuous 32 bit audio files from the start to the last sample with a value other than digital zero, freezing all your tracks is not really a goo d idea. Open your performance meters and you'll probably notice DISK I/O is hitting the ceiling (causing your -10010) and your processor is in the basement. Try to bring them closer together. There is a pref to turn the message off. Unfreeze your tracks with the lowest CPU usage and just let them play.

Yes, but some effects have little noticeable CPU demand.

In your case 1 instance of an ES M or a high pass filter is not worth freezing, espescially when it is the disk which is bottlenecking and not the CPU. If you remember these rules you can yield more from your system. Most of the plugs from Logic 4 or older have little CPU demands.

You can sacrifice CPU-in the system performance meter was the Disk and CPU burden equally weighted or was it all on the disk side or...Also, if you have tracks which are CPU intesive but only playback during an intro those ones are really good to freeze because their files won't get in the way at all.

Do you have larger disk buffer engaged? This will double Logic's memory requirements, but at 2GB you'd have to be using some pretty big sample libs to say that is a bad idea.

If it is your Disk IO going over many of us use external Hard Drives....I'd guess you are using internal from the track count...Session sampling rate-a huge factor for obvious reasons-use higher sampling rates only if it is REALLY necessary, alot of people use them and don't really know the difference, they just bought into marketing-huge CPU and disk killer.

Keep your system and audio drives lean. OS X and Disk formats won't allow you to do too much damage as long as you keep your disks 1/4-1/3 free and reformat regularly. I do about 3 times per year but twice if you use your system alot and once per year if it is a hobbyist.

1. Logic has multiple solo modes. If you open the Track Mixer and solo there you get no reduction in Disk or CPU. If you solo in the arrange (next to freeze buttons you can reduce the load on your system, view the performance meters for examples and just go through 1 track at a time for a better understanding. The drive will then only have to access the files which are soloed. You will basically have to isolate the problem if it is a CPU issue (find out which plugin-if it is a logic plugin then Audio Instruments with high polyphony are the only plugins which can single handedly bring a PBook to it's knees). Keep in mind plugins you may have further down the line such as busses or on master outputs. Some plugs are more CPU intensive then others, you will just have to experiment, Guitar Amp Pro, Sculpture, and Ultrabeat (for Logic plugins) are killers for my powerbook-Bitcrusher, ParEq, Gate have basically no effect, for examples.

External hard drives help because in a Powerbook setting you would typically be running your system, Virtual Memory, samples etc from the system/Internal ensuring there is enough room and speed to do it's things while running your session and audio files from the external-sharing resources. They help most because the system can access the drive it needs to when it needs to without the audio files to be playing getting in the way and vice versa. Running at a smpling rate above 48k will have a huge impact as well, so stay in the 40s unless you have a really good reason not to. There are plenty of drives- I would go with FW if you have a 15 or 17 inch. If you have a 12 inch you may want to consider USB2 if you use a firewire interface. I would recommend not getting a giant drive, 80 to 200 GB will do. I just use Western Digital and have many hard drives, that way I have backups of everything and basically shrug if one goes. Seagates are other ones which you will find for under $100. I avoid Maxtor and LaCie because I have had bad luck with them. External FW drive enclosures are also useful. This board is full of people recommending drives, just search for more opinions. They are out there.

This error can be caused by other things like conflicting drivers.

Cheers

Hi David. Just 2cents from a relative newbie... I had the same trouble with my G4 1Ghz 1Gb until I did the following 3 things:

1. Get a high speed HD 7200+ (Western Digital "Caviar")

2. Be sure to save your tune as project.

3. DOWNLOAD PRO APPLICATION SUPPORT v3!!! (from apple site)

Pro app support was the biggest help for me. Goodluck.

I think I isolated the problem. I'm using a software instrument (EXS24) in the song, and when I mute it, the computer does not stall anymore.

do a search on the forum, you will find this a common problem. it is a case of a corrupt plug-in channel.

if you have the perofrmance meter up and you notice one CPU spiking and the other hardly being used, then one of your plug-ins is "cycling" or feeding back. i think it is something to do with the programme not realizing that a plug-in is still engaged (the plug-ins are active even when the sequencer is not running) and not allocating tasks to the other cpu as it should.

you will also notice that even when idle the cpu meter (usually the left one) is hovering at around a third. the solution is to open audio config and option-click (bypass) each plug-in one by one until you notice the cpu drop significantly. that will be your offending plug-in.

reinstantiate the plug-in in another slot or on another track or audio instrument and it should be fine.

all advice you have received from justin is important stuff to know, but you should have been able to run 16 frozen tracks unless your buffer settings are really low. on a powerbook though, that's about as much as i would have thought you'd manage. he's dead right about an external hard drive if you're doing audio stuff on a laptop. don't forget the system needs your hard drive to do things as well.

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.

I get this error too on my Powerbook, which I use live on stage, where a sudden stop is a disaster. It's very odd though. Often a song will suddenly stop, giving the overload error message, but if i start again from the beginning, it plays though fine again and again. I'm using external FW drive, and all but the instruments I'm playing live from my keyboard have been bounced down to save processing cycles. I'm always looking out for danger zones in the song, where CPU spikes could occur, but overall my songs are 50-75% CPU. I don't see why a song should stall, but only the first time I play it. Does Logic do something different the second play though?

I don't see why a song should stall, but only the first time I play it. Does Logic do something different the second play though?

this is a normal behavior when you are on the limit of your computer, Logic is loading the files in VM !
Same for EXS !
Do you use EXS ?
what audio interface do you use ?
puting it on a PCMCIA FW card may solve your problem
you can also reorganize your FW disk

Best

Cyril

It takes a lot of familiarity with your system if you want it solid for live performance, I insult my system with what I expect from it when going live, be prepared for any error which happens kind of often. Bypass things when you can bounce down as much as you can, 75% CPU by Logic is something I stay away from live to avoid issues. The sessions should be small and portable. I've been live and we had found out at soundcheck that everytime the bass kicked in it made the disk resonate so much that it was unreadable for live performance, it has also happened the other way around where the internal drive is unreadable i certain rooms in live settings-at least then you have some time to span the files used by the songs over 2 disks as well.

Pro app support was the biggest help for me

mate most people can't even run logic without pro app support. you've been doing well if you even managed to boot logic up!