Re: Why is CoreAudio C++ not Objective-C?
Re: Why is CoreAudio C++ not Objective-C?
- Subject: Re: Why is CoreAudio C++ not Objective-C?
- From: Paul Slocum <email@hidden>
- Date: Fri, 22 Oct 2010 12:22:15 -0400
"fairly complete"
Why does Apple consider "fairly complete" documentation adequate? We
kinda need "complete" documentation. Coreaudio (for the iPhone at
least) is the most poorly documented embedded SDK I've worked with in
many, many years. When somebody asks a question on here not covered
by documentation, it should be added to the docs.
-paul
On Thu, Oct 21, 2010 at 8:55 PM, William Stewart <email@hidden> wrote:
> Specification:
> https://developer.apple.com/library/mac/#documentation/MusicAudio/Conceptual/AudioUnitProgrammingGuide/Introduction/Introduction.html
> - provides a fairly complete discussion of the Audio Unit API and its expectations. It does use some of the AUBase sample code in places, but these can be seen as illustrations of the point. If there is a
>
> The AudioUnit framework header files also provide substantial detail about the specifics of the various properties and API calls, their semantics and expected behaviour.
>
> Tools:
> The auval tool can be used to do an extensive test of the correctness of your implementation.
>
> The AULab application can be used to do a first-approximation test of the correctness of your implementation (in particular how you interact with an audio unit's view)
>
>
> These specifications and tools should be complete, if not please file a bug.
>
> Thanks
>
> Bill
>
>
> _______________________________________________
> 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