Re: Changing the latency from within the render callback.
Re: Changing the latency from within the render callback.
- Subject: Re: Changing the latency from within the render callback.
- From: Jim Wintermyre <email@hidden>
- Date: Thu, 26 Feb 2004 00:50:47 -0800
On Mon, 23 Feb 2004, William Stewart wrote:
On 23/02/2004, at 1:51 PM, Philippe Wicker wrote:
> Hi all,
>
> I've read in the documentation (html AudioUnits doc coming with the
> SDK) that an AU can publish a Latency property and that the AU is free
> to change the value of this property. I could have to use this feature
> and have some questions about this.
Not typically = the property is described generally as a read only
property and in most cases will be read only (though of course, some
AU's can/will want to have this configurable).
Just to clarify, Bill you mean that a host would not change the property,
but it is expected that a plugin still may change it at any time, right?
Because Philippe was talking about the plugin itself changing it, and I
think that then you were replying about hosts changing it. Maybe I'm
misreading, though...
My read on that is that Bill was saying that typical AU's will not
change that property. But some (like ours) will want to set it
depending on other things (buffer size for example). However it
seems to me that it might be unreasonable to expect hosts to read
this at *any* time, i.e. every render call. If you were changing
this on render calls I would imagine that would cause mayhem (or just
not work) in hosts that are doing automatic delay compensation. I
think typically plugs would want to set this in Initialize(), and
possibly change it when the stream format or the max frames per slice
changes.
Jim
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.