Disk is too slow (Record)(-10004) error..so sick of this.

maybe you already know this, but: I can avoid this messages by setting all not in use tracks to "no input". For some reason it reduces processor use.

Just curious, are you using any cpu heavy plugins (Space Designer) when this happens? How about anything running in the background causing disk access.

What sample rate are you recording at?

Sometimes the "disk too slow" error is not caused by the disk but by the system bus being tied up and data is not able to be transferred fast enough. High sample rates, buffer settings too low, poor drivers or hardware interfering with the system bus can all cause disk too slow error. How many UAD cards are you running?

BTW, Cubase has far superior audio editing and handles loops well, the main thing is it's not an "Apple" program, in the sense it's not integrated with AU and Apple loops nor does it have the Logic Instruments. However, v5 is stable and handles multiprocessing well on Mac now.

pancenter-

sorry not to be clear, I mean Mac OS should run in 32-bit. Snow Leopard boots in 64-bit mode by default but you can boot in 32-bit. UAD does not support 64bit processing so far. Hold down the keys 3 and 2 and power-on your Mac.

Hmm. I used to have a Dual Xeon 2.66 before it died, and it ran 10.6.4 in 64 bit with a UAD 2 solo card working really well. I occasionally had the same trouble you have had (and also ran down to the local to grab an extra drive, and then also recorded the band onto my samples drive).

Anyway, the one thing I did to clear most of that up, as well as occasional spitting noises, was to update the firmware and driver for the Fireface 800. I hadn't done it probably since I was running 10.4.11!

Anyway, with your setup, I have recorded 14 - 16 simultaneous tracks of bands with the buffer at 32 without any dramas.

BTW, if you can be bothered to set it up, the fireface mixer is fantastic for doing no latency independant mixes for each of the band members, regardless of the buffer setting. You can even assign a midi key to operate a talkback mic. (just don't let anyone touch any other midi keys if you haven't saved the setup... ask me how I know this!)

Anyway, good luck.

I am experiencing a similar problem & have been receiving the same messages, even while recording as little as one track and playback has become an issue as well. However, THIS WAS NOT ALWAYS THE CASE. I have heard of people with this same problem, where they receive this message out of nowhere after logic has been working perfectly for them.

I also would like to note that I am running all settings in logic for optimized recording and playback (audio & buffer settings etc etc etc)

THIS IS NOT A HARDWARE ISSUE, at least in my situation as I am running a fast internal HD & have ample memory. Please reach out if you feel like you have a pragmatic solution to this issue.

This may be a possible lead on the fix... I remember reading this post from a user "soundsgood" in 2008 who was having a similar issue..I don't understand completely his solution, but if someone could enlighten me, I feel that this might be the solution to our issue

+"Okay - forgive me 'cause I'm a newbie on this forum and if somebody else has already figgered this out, I'm sorry.... I've been having the same problem all of the sudden after many years of crash-free and error-free recording. I've read everything. I've pulled my hair out. I've done dozens of clean installs. I've repaired permissions so many times I can do it blindfolded. And sitting here tonight, it dawned on me.... there are TWO places Logic is sucking data from: wherever you've got your SONG files stashed, of course.... but it ALSO NEEDS TO ACCESS THE STARTUP DRIVE (or wherever else you might have your Apple Loops installed). I was watching my drives being accessed during a playback of a fairly complicated tune (most tracks were frozen of course), and both of the afore-mentioned drives were going berserck with accesses. We're all focusing on our dedicated audio drives, but forgetting about our boot drives (where Logic usually resides along with most or all of our loops). I carbon copy cloned my boot / operating system (including Logic) to a different (in my case, an external firewire) drive and the problem disappeared. Could've been because the cloning process de-fragged all the loops & stuff, or maybe my OS just likes snatching its sample/loop info from an external drive. Worked for me... so far....... let me know if it works for others....."+

I also had this annoying problem for quite a while when recording my band in our rehearsal room. I tried several setups with internal and external hds, tried different audio cards just to come to the most simple conclusion/solution that the root of all evil was vibrations. The harddrive is put back in a safety position so that the write-head does not crash the surface. I simply dampened the table where my laptop sits on and now recording works like a charm.
Maybe you could try a recording session on the internal HD while holding your notebook in your hands or try another place for your desktop.

I also read that some guys on this forum disable the motion sensor for their hd's but I really would not recommend that as this can result in serious damage to your harddrive.

Hope this is helpful for you.

2 of UADs-1 and Duende PCIe work very well here, MIDI and Ext.clock as well.

about UADs: please remember to verify if you're running in 32-bit mode.