Re: HostCallback_GetBeatAndTempo malfunction in Logic?
Re: HostCallback_GetBeatAndTempo malfunction in Logic?
- Subject: Re: HostCallback_GetBeatAndTempo malfunction in Logic?
- From: MeldaProduction <email@hidden>
- Date: Wed, 17 Nov 2010 03:29:37 +0100
Well, no I didn't, but what would be the point? At the end it would need to have the whole buffer for the audio interface anyway. From the positions it looks like one thread is always ahead, so this would actually higher the latency, woudn't it?
2010/11/17 Paul Davis
<email@hidden>
On Tue, Nov 16, 2010 at 8:47 PM, MeldaProduction
<
email@hidden> wrote:
> Very! For example, if current position is 6.5 (which I can only guess in
> Logic...), then all plugins in one thread get 6.5, the others get 6.7, and
> the next block is say 7.0.
> In the log sorted in time it looks like.
> Thread+Plugin PPQ
> A+1 6.5
> B+1 6.7
> A+2 6.5
>
> A+1 7.0
> B+1 7.3
> A+2 7.0
data for the future? Logic has some fairly hairy capabilities in this
respect, and you cannot assume that every track is computing data
"just in time". I don't recall the terminology for sure, but it might
be something like the "current focus track". i seem to recall that
this track will process data with a different buffer size, to provide
lower latency while doing GUI manipulation.
_______________________________________________
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