Re: Coreaudio-api Digest, Vol 4, Issue 301
Re: Coreaudio-api Digest, Vol 4, Issue 301
- Subject: Re: Coreaudio-api Digest, Vol 4, Issue 301
- From: Shai Shasag <email@hidden>
- Date: Sun, 4 Nov 2007 17:32:39 +0200
On 01/11/2007, at 21:03, email@hidden wrote:
We're also working on a formal, first publication of the Audio Unit
Specification, which will include some discussion of parameters. We
expect (and hope) that this first publication will generate active
discussion. If you have requests for what should be in (or not in)
the spec document, you can email me directly or discuss on this list.
Thanks!
My first request would be that every part of the Audio Unit
Specification (function, structure, flags, etc...) shall be
documented, there should be no white spaces on the map.
My second would be that the documentation shall be precise and
unambiguous, when Bill is saying:
We have no formal requirements for the HighResolution flag; the
expectation is that the host will use as high a resolution as it is
capable of when dealing with this parameter. What that might be in
reality is dependent on all kinds of restrictions (not the least of
which is the resolution of a control source that may be attached to
that parameter).
This means that the flag has no precise definition and therefor
cannot be used reliably by hosts and plugin.
Shai Shasag
Senior Software Engineer
Waves Audio Ltd.
Phone: +972-36084007;
Fax: +972-36084056;
-----------------------------------------------------
Don’t Just Do Something, Stand There!
_______________________________________________
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