Re: AU, plugin tempo, musical time information
Re: AU, plugin tempo, musical time information
- Subject: Re: AU, plugin tempo, musical time information
- From: Paul Davis <email@hidden>
- Date: Tue, 3 Nov 2009 18:57:52 -0500
On Tue, Nov 3, 2009 at 4:59 PM, James McCartney <email@hidden> wrote:
> In any case arguing this is quite academic since the API has shipped.
I'm not really attempting to argue it, although i think it is an
interesting discussion, albeit not for this list. The docs are not
really clear on whether on not "beat == quarter note". I asked for
clarification. Doug seemed to be offering a defense of "beat ==
quarter note", but i have still not seen a clear statement on whether
this is what plugins should expect from the host ...
it also remains unclear how plugins can identify their position beyond
beat position since they have no access to a tempo map, nor can they
handle meter/tempo changes that occur in the middle of a rendered
buffer. it would be interesting to hear how the API is intended to
handle, or is not intended to handle, these issues. finally a clear
state on precisely what "transportStateChanged" is supposed to be
relative to would be nice.
--p
_______________________________________________
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
References: | |
| >AU, plugin tempo, musical time information (From: Paul Davis <email@hidden>) |
| >Re: AU, plugin tempo, musical time information (From: Doug Wyatt <email@hidden>) |
| >Re: AU, plugin tempo, musical time information (From: Richard Dobson <email@hidden>) |
| >Re: AU, plugin tempo, musical time information (From: Doug Wyatt <email@hidden>) |
| >Re: AU, plugin tempo, musical time information (From: Paul Davis <email@hidden>) |
| >Re: AU, plugin tempo, musical time information (From: James McCartney <email@hidden>) |