I am waiting to see if it helped Inoc with the problem. See if my last suggestion in the attached post helps. The audio engine was not able to process all required data in time (-10011)' I think I found a solution. But since it can't do now what it had done flawlessly before, I'm thinking there is something else going on. I've been reading lots of posts about the irritating audio overload problem: ' Logic Pro: System overload. Once connected to the network, the light on the top of your Sonos device should light up a solid white color. Allow up to two minutes for it to boot up and connect to the network. Plug the power cable back into your Sonos device. How can I fix this Click on Settings and then Audio. Unplug the power cable from your Sonos device and wait 30 seconds. I hadn't had problems with my current config and actually was able to do quite a bit. Camelot shows me that the CPU is overloaded and it crackles and crashes. Updated: SoundGrid server firmware v11.2.65. Now before you ask, I am still on a G4 dual so my RAM capacity will be limited, but until I get a G5, I'm trying to make do. Fixed: Possible audio drops between the WSG-Y16 I/O card and the SoundGrid Driver, when no SoundGrid server is assigned or in use.
I also have more RAM coming today, but because I didn't have the problem before, I'm wondering if it could be some kind of cache issue or anything else like that?
I removed a couple of free plugins, and that has improved some. I used to have no core audio problems while playing with high track count. Lately I've had alot of beach balls then crashes, core audio that can't keep up (choppy audio then halt) even playing a 1 track test autoload with an EXS instrument.
#AUDIO OVERLOAD CRASHING PRO#
Logic Pro 7.2.3 used to be running great for me, no crashes, etc.
0 kommentar(er)
