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 06:35:14 -0800
The dialog box can be shut off so that it doesn't tell you anymore when there is an overload. I think the purpose for the dialog box is to distinguish audio drop-outs from CPU overload as opposed to audio drop-outs or glitching due to timing problems which the system would not know anything about.
In any case the CPU meters do show when they are being slammed and I can tell immediately when there is a problem with CPU performance.
I'l also add, while I do not think this is probably the right place to discuss problems in Logic, I too see the same problems with overloading one CPU while the rest are BARELY used in Logic 8. This is in a project where there are barely any plugins on tracks, no UAD plugs, nothing CPU intensive but about 20 tracks. Actually, it's really true of every project I have worked on lately. Always one CPU is VERY MUCH over-utilized compared to the others. Sometimes a start and stop will rebalance it a little and it appears looping a section makes it much worse, but nevertheless, earlier versions of logic than 8.01 seemed to use the CPUs a bit more efficiently.
That said, I am *sure* Apple knows about this. Like every third thread on the Logic discussion board talks about it. Some people have it worse than others, some people say they don't have the problem at all. Since when people's stuff works they generally aren't out exclaiming to the world that it is, it's hard to know what the real scope of the problem is.
Rick
Asylum Studio Productions
On Wednesday, March 05, 2008, at 09:19AM, "Robert Drehmel" <email@hidden> wrote:
>tahome izwah wrote:
> > This should be simple to fix (on Apple's part) - remove the annoying
> > dialog box and add an overload indicator to the Logic UI instead.
>
>There actually is a per-CPU core load indicator in Logic. The issue
>at hand doesn't look like a classical overload situation though.
>
> > Noone cares if samples are lost when you stop playback, so bringing up
> > an alert panel is overkill (IMHO) and doesn't do the user any good.
> >
> > A CPU overload indicator could take care of other situations where you
> > actually run out of CPU during playback. In any event, in my opinion
> > this is not a situation that calls for (or should enforce) any user
> > interaction.
> >
> > --th
> > _______________________________________________
> > 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
>
>
_______________________________________________
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