Re: Coreaudio-api Digest, Vol 5, Issue 130
Re: Coreaudio-api Digest, Vol 5, Issue 130
- Subject: Re: Coreaudio-api Digest, Vol 5, Issue 130
- From: "John Lazzaro" <email@hidden>
- Date: Mon, 7 Apr 2008 12:23:57 -0700
> From: JJB <email@hidden>
>
> Does this mean that we can use plain old 'C' for writing Audio Units
> plugins - I've been attempting to learn Objective-C so I could develop
> some rudimentary Audio Units. What would be the drawbacks of using C
> (assuming it is practical) instead of C++ or Objective-C?
You'd need to reverse engineer the C API by looking at the calls in the
C++ code. And you'd need to figure out the obscure way one creates a
component that is recognized as such by the OS. The OS X component
architecture dates back to 9, which predates audio units -- last time I checked
one needs to read 9-era documentation discussing QuickTime plug-ins to
figure it out. A project that needs this has been on my list of
things to do for
a while ... if I ever get to it, I'll document it on a web page (don't
hold your breath waiting).
--
John Lazzaro
http://www.cs.berkeley.edu/~lazzaro
john [dot] lazzaro [at] gmail [dot] com
_______________________________________________
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