Re: What is the meaning of kAudioUnitParameterFlag_IsHighResolution ?
Re: What is the meaning of kAudioUnitParameterFlag_IsHighResolution ?
- Subject: Re: What is the meaning of kAudioUnitParameterFlag_IsHighResolution ?
- From: Murray Jason <email@hidden>
- Date: Tue, 6 Nov 2007 10:57:41 -0800
Hello Shai,
On Nov 4, 2007, at 7:32 AM, Shai Shasag wrote:
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.
Well stated. That's one of my goals.
As you know, audio units depend on certain interfaces from the Mac OS
X frameworks. Similarly, the Audio Unit Specification will depend on
some normative references -- most importantly, on API Reference
documentation. We're creating the reference documentation in concert
with the spec.
This partitioning of content, among our various document types of
References, Guides, Specifications, etc., follows our practice across
the board in the ADC Reference Library.
And rather than wait until it's all done before giving you any of it,
we do plan on publishing pieces as they get finished. (As always,
please let me know which headers are at the top of your list for
getting complete doc.)
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.
On Nov 5, 2007, at 5:54 PM, William Stewart wrote:
No.
It means that it is a hint to the host and that the host should do
"what it can" given that request. By not providing this hint, you
are also giving the host the liberty to use a low resolution option
if that is available. So, it might not be as definitive or as
dogmatic as you would like, but it is nonetheless a useful statement.
This is the kind of discussion we're hoping for -- so thank you. I
won't be satisfied with the spec unless it's accepted as clear,
precise, and unambiguous. At the same time, there will be instances
(such as the one here, for the IsHighResolution parameter flag) where
we clearly, precisely, and unambiguously describe a subtlety that is
neither black nor white.
The doc's role here of course is description of the API, but not
definition of the API! So, for example, if you see a need for a
different sort of parameter flag, then this email list is the perfect
place to hold that discussion.
-murray
On Nov 4, 2007, at 7:32 AM, Shai Shasag wrote:
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