On Sat, Jul 25, 2015 at 2:47 PM, Brian Willoughby <[email protected]> wrote:
> Once you implement GetLatency, AU Hosts like Logic will automatically send > your plugin the audio data in advance of when it is needed, so that the > output audio is time aligned with the other AU plugins in the graph, even > though the input audio is not aligned. This works great for all graphs > except those that involve live inputs, which necessarily must introduce > latency. That is a host-side implementation detail that isn't a description of all hosts. What is true on all hosts that support latency compensation is that the output from your plugin will remain synchronized with the output of other less (or more) latent plugins and signal pathways. > One tricky aspect of the above is that an AU is supposed to support Process > calls with fewer than the expected N frames of input / output. put slightly more stridently: your plugin MUST function when asked to render ANY number of samples, not just your imagined blocksize. _______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
