Re: Simple AU from VST?
Re: Simple AU from VST?
- Subject: Re: Simple AU from VST?
- From: Chris Reed <email@hidden>
- Date: Sat, 1 Mar 2003 18:53:55 -0600
On Saturday, Mar 1, 2003, at 11:07 US/Central, Jeff DuMonthier wrote:
I have a 'simple' VST plugin effect I would like to make into an AU.
The DSP is not really simple, but the interface is. It consists of a
C++ DSP engine with a VST 'wrapper' class around it that uses only the
default VST interface. There is no custom GUI. I am wondering if it
would be better to write a 'simple' AU wrapper around the engine or to
use the Emagic VST porting SDK to put an AU wrapper around the VST
wrapper. One key factor is whether or not there is a default user
interface for AU's like there is for VST. There was a rather lively
discussion here about Carbon vs. Cocoa and the inability to use a
Cocoa interface with an AU. I have not done Mac UI programming since
the days of the Think class library. I don't know Cocoa or Carbon,
but if I need to learn one or the other it is going to be Cocoa. If
even a simple AU requires writing a Carbon UI then my question becomes
how can I get the Emagic porting SDK? If not, then I guess I should
try wading through the AU documentation again. Hopefully the correct
version was installed with the latest version of the developer tools.
AUs do have a 'generic edit view' component that hosts will use
automatically if you don't provide a custom editor. So if you already
have your DSP engine encapsulated well, it should be easier to just
write directly to the AU API instead of going through a couple
different layers. I'd suggest looking at the several open source audio
units that are out there to get an idea of how things are put together.
cheers
-chris
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.