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: "Ross Bencina" <email@hidden>
- Date: Sat, 23 Oct 2010 04:56:42 +1100
Bill Stewart wrote:
These specifications and tools should be complete, if not please file a
bug.
Oh please, this whole "please file a bug" situation is quite frankly
insulting. You know the documentation is crap Bill, just sort it out..
Here are the reports:
------------------------------------------------
Follow-Up: 123685722
Bug: After 10 years the AudioUnit specification still doesn't exist
Summary information:
The Audio Unit documentation makes reference to a definitive "Audio Unit
specification" document however the document doesn't exist. At the time of
this bug report (October 23, 2010) the Audio Unit page states "The Audio
Unit Specification document is currently in development" :
http://developer.apple.com/library/mac/#documentation/MusicAudio/Conceptual/AudioUnitProgrammingGuide/AudioUnitDevelopmentFundamentals/AudioUnitDevelopmentFundamentals.html
This is completely unacceptable. Developers don't need vague documentation
and code examples they need a definitive specification
Steps to reproduce:
Look for a definitive Specification of the Audio Unit interface.
It doesn't exist.
Many details of the interface are only available by combing mailing list
archives or by trial and error.
Results: Apple is a joke.
Workaround: use other vendor's tools who provide acceptable developer
documentation (e.g. Microsoft)
------------------------------------------------
Bug ID# 8584363.
Bug: bug and issue reports to Core Audio developer list are ignored
Summary:
If someone takes the time to email a developer mailing list with an obvious
bug it should be sufficient to trigger resource allocation.
Detail:
Posting error reports and documentation bugs to the Core Audio developer
mailing list should be sufficient to trigger bug fixes/development resource
allocation at the discretion of development management.
Day after day people report problems and bugs with the Core Audio API and
implementation via the Core Audio API mailing list. This is almost always
met with a request to "please file a bug" from the development manager Bill
Stewart.
It is completely unfathomable that the devlopment manager is not
sufficiently empowered to schedule work initiated from the mailing list
without a bug report / radar request.
If someone takes the time to email the developer mailing list that should be
sufficient to trigger resource allocation.
Steps to Reproduce:
1. Report a bug or documentation issue to the Core Audio API developer
mailing list.
2. Get acknowledged by the lead developer/manager Bill Stewart.
3. Get asked to file a radar report.
Expected Results:
1. Report a bug or documentation issue to the Core Audio API developer
mailing list.
2. Get acknowledged by someone
3. Problem gets fixed.
Actual Results:
(see steps to reproduce)
------------------------------------------------
Thanks
R.
_______________________________________________
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