• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Coreaudio-api Digest, Vol 4, Issue 301
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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 17:54:14 -0800


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: 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
  • Follow-Ups:
    • Re: Coreaudio-api Digest, Vol 4, Issue 301
      • From: William Stewart <email@hidden>
References: 
 >Re: Coreaudio-api Digest, Vol 4, Issue 301 (From: Shai Shasag <email@hidden>)

  • Prev by Date: Re: Trying to gifure out why adding kAudioDeviceProcessorOverload listener fails
  • Next by Date: Re: Coreaudio-api Digest, Vol 4, Issue 301
  • Previous by thread: Re: Coreaudio-api Digest, Vol 4, Issue 301
  • Next by thread: Re: Coreaudio-api Digest, Vol 4, Issue 301
  • Index(es):
    • Date
    • Thread