Re: Is a CoreAudio bug the cause of the annoying "overload" messages in Logic 8 ?
Re: Is a CoreAudio bug the cause of the annoying "overload" messages in Logic 8 ?
- Subject: Re: Is a CoreAudio bug the cause of the annoying "overload" messages in Logic 8 ?
- From: Richard Burnett <email@hidden>
- Date: Wed, 05 Mar 2008 15:49:12 -0800
I can say that I am very confident my system is setup properly, with regards to clocking, drivers, etc. I spent a lot of time going through this very carefully and also in my questions of other users having the problem. I absolutely agree that it seems certain combinations cause these problems and tracking them down has been rather difficult. For instance, I know that using UAD plugins can easily cause an overload on one CPU at low buffer settings. This makes sense and is coincident with Universal Audio's statements saying if you use their plugins, you need to set the buffer size higher.
However,
There are many people who are using the same hardware and the same settings between Logic 7.2 and Logic 8.01 and seeing DRASTICALLY different results regarding CPU usage and the pegging of one CPU with regards to the rest being almost near zero. I've witnessed this myself. In addition, in other applications like Digital Performer when using the Activity Monitor using the same Drivers and as close to the same settings as I can, I do not see this problem.
As you've mentioned, people on Leopard seem to have a bit more problems than Tiger. I'll also agree that this is what I see as well.
Now, there are certainly many aspects of what Logic is doing and how it has changed that could cause this. Some people have demonstrated the same problem with just Built-It audio and that's it! I myself use an Aggregate device and noticed that it didn't matter if I used the Aggregate or Built-In audio, the same overloading of one CPU was still happening.
Clearly something has changed in Logic and/or CoreAudio with respect to how Logic uses it. Or maybe the CPU meters are not displaying what is REALLY happening accurately. These people (and myself) can only go on what Logic is telling them, and unfortunately, people will draw the conclusion there is a problem.
While I agree a troubleshooting guide will help in many instances, I am VERY proficient with my setup and have tried everything I could. Nothing I do makes this problem go away.
Rick
On Wednesday, March 05, 2008, at 05:23PM, "Brian Willoughby" <email@hidden> wrote:
>
>Sorry to contribute to an off-topic thread, but Logic is very close
>to home for those of us who develop AudioUnits, and also for those of
>us who extensively work with CoreAudio.
>
>I use Logic extensively, and this "overload" problem only rarely
>happens. Usually, it's when my interface is not clocked correctly
>(such as set to external word clock, but the other device is missing
>or glitchy). There are times when I try to do too much, and actually
>do overload the CPU. I have also noticed more of a problem on
>Leopard, so I stick to using Logic on Tiger. Many years ago, the
>popup was quite a problem (annoyingly so), but perhaps I have learned
>how to get my audio interface and other parts of the OS set
>correctly. This is a difficult issue to track, but I just wanted to
>point out that it does not affect everyone who uses Logic
>extensively. Perhaps it is only present in certain combinations, and
>then only for some people. Perhaps Logic should come with a
>troubleshooting guide, so that users can correct the problems with
>their system when this popup appears.
>
>Brian Willoughby
>Sound Consulting
>
> _______________________________________________
>Do not post admin requests to the list. They will be ignored.
>Coreaudio-api mailing list (email@hidden)
>Help/Unsubscribe/Update your Subscription:
>
>This email sent to email@hidden
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden