Re: Effect units in iOS > 4
Re: Effect units in iOS > 4
- Subject: Re: Effect units in iOS > 4
- From: Brian Willoughby <email@hidden>
- Date: Sat, 06 Sep 2014 10:53:42 -0700
I would like to add to Chris' comments: AudioUnits are basically self-documenting. Each parameter is listed by the plugin, along with the name of the parameter, data type, and range. This "documentation" is thorough enough that an AU host can create an interface on the fly.
Brian Willoughby Sound Consulting
On Sep 6, 2014, at 10:31 AM, Chris Adamson wrote: Undocumented != private APIs. AUComponent.h is one of the public headers you import as part of AudioUnit.framework. If you do old-fashioned framework linking in your Xcode project (as opposed to the "@import" new hotness, or Swift), you'll see this header file as part of your project, as seen here: https://alpha.app.net/invalidname/post/38235684/photo/1 . Basically, if you can find it with open-quickly (cmd-shift-O), it's public.
Some of the contents of these headers are in the Xcode documentation bundle, and some aren't, but that's a fault of Xcode's documentation, not of Core Audio. In fact, for Audio Unit properties and parameters, the comments in these header files are the *only* public documentation you'll find for their use and semantics.
This stuff isn't "undocumented". It's just "really, really crappily documented". Big difference. And even if it has no documentation comments in the header files, if it's in a public header file, it's fair game.
|
_______________________________________________
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