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: William Stewart <email@hidden>
- Date: Fri, 22 Oct 2010 13:01:52 -0700
On Oct 22, 2010, at 9:22 AM, Paul Slocum wrote:
> "fairly complete"
>
> Why does Apple consider "fairly complete" documentation adequate? We
> kinda need "complete" documentation.
Have you read through the document?
If/when you do, then you can file bugs or raise issues about areas that are missing and we will fix them.
I am not interested in having a discussion about semantics. We attempt to respond in a timely manner to these kinds of problems and address them.
> 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.
This is a problem. however, this is not the topic of this thread. I understand that you are frustrated, but I would respectfully ask you not to use this as an opportunity to vent your frustration about other. I will certainly forward your comments to the team who's responsibility it is to document the iPhone SDK.
It is tremendously helpful to have specifics that can be acted on. Taking the time to write a bug report, detailing the areas where these issues are causing you problems is helpful to us to help us fix these problems. Your help is appreciated.
Bill
>
> -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