Re: What Are AudioUnits?
Re: What Are AudioUnits?
- Subject: Re: What Are AudioUnits?
- From: Philippe Wicker <email@hidden>
- Date: Thu, 7 Oct 2004 07:11:25 +0200
On Oct 7, 2004, at 5:17 AM, Daniel Todd Currie wrote:
I sort of know the answer to this question, but not really...
I released Perfect Pitch (a musical instrument tuner) back in December
2003. A number of people respond, tell me I need to make it an
AudioUnit. I'm also having trouble with third-party hardware, and I
have been told that an AudioUnit implementation is the answer (opposed
to the original HAL implementation).
I have my tuner working using Audio Units now, but I don't really know
where to go from here. Simply by being written using AudioUnits, will
my application be accessible to an AU Host?
Yes.
For that matter, what do people hope to accomplish by using my tuner
as an AU?
I never intended this application to be more than a stand-alone app,
but if more can be done with it, I am interested in filling that gap.
You can build a stand-alone app starting with the AudioUnistHosting
code available in the CoreAudio SDK.
Someone mentioned AUValidation to me, so I grabbed the validator and
played around with it. Running "auval -a" gives me a list of ~20 AUs;
should my application/AU be listed among these?
Your AU should be listed, not your app.
My app is running on the "auou ahal appl - Apple:
AudioDeviceOutput" component, so should I be validating that component
while my app is running?
No. Hopefully the Apple AUs (should) have passed the auval test :))
If my AU validates, what does this mean?
'auval' checks that your AU complies with the AU semantic. If your AU
validates, then it means that it has correctly implemented a
significant part of the AU API. It gives you also the right to
distribute your product with the AU compliant logo, which is a
"quality" label for the user.
Do I need to do something with UIViews in order for people to use my
tuner in their AU Host?
I presume that your AU needs some interaction with the user: e.g. show
the actual pitch, give the user the possibility to bypass the effect
when he's done, ... That kind of job is to be done in the AUView.
I guess the primary problem I am having is that I am not familiar with
audio production software. I am simply an instrumentalist who thought
it would be cool to tune instruments using his computer. AUs seem to
be pretty popular among pro audio users, yet I can't find a single
website that describes the fundamentals of what an AU does!
That's still a problem. Things are getting better and better with time
on that matter but a comprehensive step by step tutorial based on the
SDK for each kind of AU is still a missing piece, particularly for
newcomers developers who didn't follow the discussions on this list for
the couple of past years :(
Anyway, have a look at:
http://developer.apple.com/documentation/MusicAudio/Reference/
CoreAudio/index.html
Is it perhaps a lost cause to try and develop an AU without any
experience using one, or without any facility to test one? I need
some direction here, even a simple link or two with some useful
information would be greatly appreciated.
-- Daniel Todd Currie
_______________________________________________
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
Philippe Wicker
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