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: William Stewart <email@hidden>
- Date: Mon, 5 Nov 2007 18:02:12 -0800
Oh, I also should include this information. With Logic,
IsHighResolution does just that; increases the internal resolution
used to represent the parameter values. It doesn't influence whether a
parameter is shown on a control surface.
So, there also seems to be some confusion about interactions here
(that this somehow means the parameter won't show up for control
surface control). I suspect that the "Is Non-Real Time" might be the
flag that could cause that behaviour (exclude from control surface
control) as you can't automate parameters marked with this flag.
Bill
On Nov 5, 2007, at 5:54 PM, William Stewart wrote:
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.
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.
Bill
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:
@apple.com
This email sent to email@hidden
_______________________________________________
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