Logic pro Audio engine error (-10011)

[ElmerT]

I have a new set up G5 quad 2.3 Rme fireface 800

But opening a song in logic (for exp. demo ultrabeat) keeps getting the mesage :

Core Audio
System Overload
the audio engine was not able to process all required data in time
(-10011)

This drives me nuts!!
'cause it stops playback

I've seach some forums and there are alot with this problem but no one has a solution..
So please help me out!!!!!

[Lagerfeldt]

Did you trash your preferences?

Did you remove your autoload?

Did you repair disk permissions?

What else have you tried? Re-installing sound card and MIDI drivers? Using Onyx to clean up stuff too?

[ElmerT]

I have tried everything Reboot the hole Hardisk Upate first Macosx bevore installing Logic, I updated also to the newest RME fireface 800 drivers. But nothing seems to work!

This is happening at an sample rate at 44.1 but if I put it up the probleme get so worse it mash up evreything and finely crach logic.

Buffer size seems no matter and when I load system performance the first cpu gets all the load the 2e much less. I've triede all setings in the fireface nothing works!

Am I the onley one with this probleme???

The onley thing I can still think of is; update the 512 MB of ram and put the fireface on FW 800; but I heard from other forums that it also acured on machines with more then 3 gb of ram..

[peter893]

are your hard drives set to sleep ?

If your drives are asleep and have to be awoken you can receive that message.
so be sure that is unchecked in energy saver prefs.

Pete

[Ricey]

how many tracks do you have open, how many edits? are you freezing tracks?
and unfortunately, you need 2 GB of RAM before you can even tell if anything's not working...

[ElmerT]

I disabled all sleeping modes on my Computer. so my hard drive doesn't sleep and processor speed on highest. As test I use the demo song for g5 onley, if you open Ultrabeat demo full (29 tracks with ultrabeat) with no tracks in freeze mode. It's on 44.1 sample rate anything more crach the whole thing.

I'll try the 2 gb of ram soon, but how can this solve the probleme 'Cause I thought that it was some thing with cpu speed! It's seems logic can't process all audio data fast enough.

[Ricey]

Originally Posted by ElmerT

I'll try the 2 gb of ram soon, but how can this solve the probleme 'Cause I thought that it was some thing with cpu speed! It's seems logic can't process all audio data fast enough.

true, not enough or bad ram would cause other problems like kernal panics and lockups.
29 instances of Ultrabeat? well, that would kill my PB setup of course, but still - it seems like a lot. which version of Logic? OS version?

also, in case you haven't been there yet:

http://community.sonikmatter.com/forums/index.php

do some searches on your issue before jumping in, it has probably been covered thumbsup

[boody]

I had simmular problems: my new G5 had two flaws
-the memory modules were not put in place tight enough
-the OS factory install wasn't ok

Resolved all problems by;
-checking all hardware connections & pressing the ram modules (found one ram-module going 'click')
-fresh OSX install > repair disc permissions
-pro application support install > repair disc permissions
-install Logic Pro > repair disc permissions

if you first want to find out if your system is flawed; run the hardware test in 'loop' mode overnight (run hardware test > press ctrl-L or alt-L , I forgot, just look at the state)

Goodluck
Budy

[ElmerT]

thanks for all the tips!!

I've reboot the whole syteme and the update to all newest fersion Macosx 10.4.5 all pro aplication suport update and update to logic pro 7.1.1. the onley thing I didn't try is if all components are fit really well. But I allready done the hardware tests and it say's it's all okey..But I'll keep on searching!! and let you know if any thing is shanging

[bmsander]

I'm still on version 5.5 on a PC, but have you checked your audio preferences to make sure that you're using the correct protocol?

For instance, I can choose between PC AV (the basic Windows drivers) and ASIO (the faster drivers).

Sorry if this is no help.

Good luck!!

[ElmerT]

I will update my ram very soon thinking to put 2gig extra in.. I think 2,5 gig must be enough. Than reinstall my whole computer...and if that doesn't work I simple don't know it no more.....

(I've checked for lose components but all fitted wel)

[Mr.HOLMES]

AHHHHHHH
I have it even again noe in the middle of a session.
It was running like wonderful for about 4 h and after this you can not even press play after 3 seconds logic drops out.

I have had this with other sessions too sometimes new saving helped or saving on a different drive.
but now nothing helps.

have tried every tag I know.

[chk027]

I'm getting that Mothereffer too. It only happens once in a while, and just recently since the 8.02 update, it never happen before that.

It doesn't do it all the time and it there is normally a spike in the HD when it happens if you look at the resource gage at the bottom.


F (-10010)

[Mr.HOLMES]

Jepp I have found the problem in my system.
I have two UAD PCI e Cards in my Mac Pro and the spike on the CPU is taht UAD is not knowing why they have that problem with the new Intel Macs.

They wrote me that they work on it and will find a solution in the near future...hopefully

They are downgrading the probs a bit in their customers mail because I can not work with the UADs ....they are slowing down my computer and provide every 20 Seconds (-10010) System Overload.

Man waht for I bought a 2x2.66 GHZ Mac Pro.....
6 Tracks Audio and system overload rediculess UAD!!!

If I take out the PCI e cards my CPU is having its full power with the cards in no way.

[LoSchifo]

I just figured out how to fix the system overload problem.
I run Logic Pro 9.1.1 on a MacPro 8 core w/ 10gb ram running on SL .3
Everything is updated to the latest version.
I noticed Logic, at least on my Mac Pro 8 core, addressed all the plugs to a single processor.
I selected all the tracks, removed the plugs from the first three slots on all audio tracks simultaneously, then made 3 steps of undo.. et voilà! the plugs are assigned to different processors. I tried this solution cause it happened years ago on ProTools Mix3 on OS9...
hope it helps.
LoS.

[Umlaaat]

Originally Posted by LoSchifo

I just figured out how to fix the system overload problem.
I run Logic Pro 9.1.1 on a MacPro 8 core w/ 10gb ram running on SL .3
Everything is updated to the latest version.
I noticed Logic, at least on my Mac Pro 8 core, addressed all the plugs to a single processor.
I selected all the tracks, removed the plugs from the first three slots on all audio tracks simultaneously, then made 3 steps of undo.. et voilà! the plugs are assigned to different processors. I tried this solution cause it happened years ago on ProTools Mix3 on OS9...
hope it helps.
LoS.

bringing back an oldthread... sorry, WHAT did u do??

[realtrance]

Actually I think LoSchifo's fix is still relevant. Rummaging around in the Logic forum at discussions.apple.com, there are a number of issues with Logic not using multiple processors very well. There are solutions, but they seem to require some trickery such as the one described above.

[Baliad]

I have been dealing with this problem for years and I have even researched this problem for years... here is one SIMPLE solution that has solved everything for me:

it all depends on the track you have selected when you play everything... if you have a complex track (like a drum sampler or softsynth) selected during playback then it will slow down the system... but if you select something simple like a vocal with hardly any plugins on it, everything should go smoothly... i tried this and am amazed that such a simple solution fixed my problem...

that said, i know many have said they even encounter the issue with only 1 track... all i can say is that that issue is probably different than the one i was experiencing...

[valis]

Baliad what you refer to is Logic's "Live Mode" for the selected track, and is the reason (which you may know) as it put anything on that audio chain on its own lower latency buffer and separate cpu core. Create a midi track and assign it to nothing and use that to select when you need to keep the issues at bay.

[explorer]

This is relevant. Required reading for Logic users.

Logic Pro/Express: Tips for balancing multi-core performance