'System Overload. The audio engine was not able to process all required data in time. (-10011)' - Any geniuses out there that can help?

What audio and/or midi interface are you using and did you make sure that there were Mountain Lion compatible Drivers avaiilable/installed for these interfaces?

Given you are using the Digi002 I'm not surprised. Their drivers are not exactly what one would call.. "Top quality" when used with anything other than PT unfortunately... and even with PT, they are known to have their issues....

The only advice i can offer, given that.. is to make sure you have the very latest version of the driver installed... and hope...

The latest one (v11.0.0) can be found here...

http://avid.force.com/pkb/articles/en_US/Download/Digi-002-003-Drivers

I get this too but im Pro 9. Never used to but since installing a UAD card I get this a lot. It's all to do with CPU resources from what I can see. You will see a spike in the CPU meter before the error message.

So I make sure any CPU intensive AU's are bounced - in my case things like my Virus Ti, Studio Drummer even LASS. Bounce any effect heavy tracks and then disable all the plug ins. Also when you start make sure you track selection is only a low usage track like a midi track, helps with CPU overheads - well in Logic Pro 9 it does.

ALso up your IO Buffer size, 512 or even 1024 - oufcoruse no good fro recording/track laying only when mixing.

Let us know how you get on

Cheers

Same old problems. Thought I'd get with the program and see if 64 bit Logic had at least a little improvement in performance.

-One instance of Reaktor Razor (Komplete 8) and same "System Overload" errors (No audio tracks BTW). Crashed first time using...downloading the new new content so I don't want to quit.

-And still no instrument inputs on the audio tracks???

-I'll post my results when all is installed.

2.2 Ghz Intel Core i7/ 8GB RAM

Since having to updating to 10.8.5, I have to update ProTools as well. My partners brand new MBP + MBOX Pro with PT 11 also choked first time. I feel very disapointed Apple, wasted my money (again) for a broken system. 10.7.5 & Logic 9...same crap. Kernel_task using 600% of the processor, shutting down whatever your working on.

I'm a professional composer and thankfully my main system is a leagcy PT TDM MIx+++ system running on a 2004 G4 and its rock solid.

As I said in my earlier post... Avid Interfaces are known to have poor quality drivers that do not play well with anything other than PT....

As an example, on a basic "testbed" 2011 2.0ghz 8GB MMS using a Motu Ultralite I can easily run 8 -12 tracks of Razor... (which is a high CPU usage plugin) without any overloads under LPX....

Plugging in a client's Digi002 instead (and using the latest v11 drivers) into the same Mac and LPX setup.. reduced the number of instances of Razor to just two before I started getting system overloads... so if you are having issues running just one instance of Razor... you should take a look at your hardware/drivers rather than your DAW...

No worries, its never just one thing sadly. A combination of audio driver, AU's, instrument plug ins etc etc. One thing else I do is bounce offline, that way the computer can slow right down to handle the max CPU and still output. If I try to output in real time mine gives the same error as yours. Like I say mine was fine till I put in the UAD card!!

Cheers

No external hardware being used...Core audio out the Mac Audio (Gave up on my USB AVID 11..useless even with ProTools). I've been using and configuring professional systems since 1995, and have used PT (or Logic front-ended) TDM systems exclusivley. My past 1 1/2 years of trying to work the latests & greatest native stuff into my workflow has been exactly oppositte of the word 'workflow'. Sorry to vent.

You have some good points, and I agree with some of what you're saying. Since operating system have become a do-it-all system, getting everything to work correctly takes more time and more expertise... one look at this board proves that, even long time users are having some problems with the recent hardware/OS/application updates.

I have a rock solid MacPro single quad core processor running Snow Leopard, Logic 9 and RME hardware, I've decided to jump off the Apple upgrade band wagon, I see only more problems ahead. Recent versions of OSX are resource intensive, way more than Windows machines at this time, at least with Windows you have options to adjust cache and virtual memory size and with a little tweaking can end up with a very efficient system. 10.6.8 still feels light on it feet and I'm having no problems so why bother. I use to have over a dozen clients whose machines I helped upgrade and maintain... all except two have gone the upgrade route and all are having some sort of problems that they didn't have before.. I gave them Apple's phone # and wished them luck.

I only do an upgrade so I can stay compatable with other studios or users. I work on PT 6.4.1 in 10.3.9. (For a laugh, I run a 7100 running 7.5.1 for my Lexicon Nuverb Card!...flawless!)

When purchased new (Dec 2011, amd for a year or so eveything worked as stated. It was one update (as always that endes this). My last call to Apple was very discouraging. Mac Mail erased 6 years of Sent Emails from a business account. Apple created a case # and nothing to offer as far as a resolution. Didn't even bother to call back. Tech's were dumb as a wall.

On the new install with a default Logic Project, kernal_task (activity monitor) shows 600% CPU usage when ideling (no audio or midi playing.

I guess I should look on the bright side, I have a great email, iTunes and MySpace computer...not much else. And I don't use an iPhone!

On the new install with a default Logic Project, kernal_task (activity monitor) shows 600% CPU usage when ideling (no audio or midi playing.

Logic using 600% or total CPU at 600%?

If it's total CPU usage and not Logic itself.. check for a runaway mdworker routine... caused by a spotlight bug thats been longstanding and never totally fixed... Resolve by stopping the MDworker routine and then exclude all drives from spotlight.. and add back in just the system drive. Wait a couple of hours for spotlight to properly reindex the system drive and then test with Logic to see if CPU usage drops down to normal levels...

If it's Logic that is using 600% then something very weird is going on that is specific to your system or install as that simply isn't normal behaviour even with using just the internal hardware and CoreAudio.

Thanks all for replying..I really appreciate your input.

Its the CPU at 600%. I searched this up and a paticular thread recommended you remove the power management .kpg (?) that is buried in the library. I did this on 10.7.5 and it fixed the problem. However, with heavy usage,the computer takes a quick 'nap' all on its own...probably a thermal-sensor fail-safe.

I stopped the MD worker routine as you recommeneded. I'm only using the system drive, no audio files playing back and not using any hardware (haven't installed any '3rd party' drivers either clean install last night from Apple 10.8.5, Logic 10.0.3). With both Autrai Spark and the newer NI Prisim, Spark within Reaktor, this occurs as it did previously. I really thought 64-bit was gonna fix these issues.

Many Thanks again!

-R