Re: Porting Vst to AU
Re: Porting Vst to AU
- Subject: Re: Porting Vst to AU
- From: Urs Heckmann <email@hidden>
- Date: Wed, 24 Mar 2004 17:06:40 +0100
Hiya,
I think the easiest way is to derive your AU "WrapperLayer" from the
appropriate BaseClass as well as from your VST class. Then, from the
methods inherited from the AU part you can just jump into the VST
methods (like retrieving Parameter list & information etc.).
For the gui, you have to implement a custom property that gives your
AUCarbonView class a pointer to your VST class, so you can jump into
open() etc. (Don't forget to remove timers for idle() when the gui
component is closed 8-)
For VSTGUI, make sure you have the latest version from SourceForge.
Despite sounding easy, I strongly recommend to create a minimal AU from
scratch for learning. Many things differ from VST, like Factory Presets
in AU vs. Programs in VST, or conventions for Initialize/Reset in AU,
Open/Suspend/Resume in VST.
Good luck,
;) Urs
Am 24.03.2004 um 12:58 schrieb Olof Westman:
I am thinking about porting my VST plug to AU.
As I see it I can take two routes: building in
a wrapper, VST host - AU plug, or loose
the VST and go PLUGGUI on VSTGUI. Any suggestions?
/Olof W
_______________________________________________
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.
_______________________________________________
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.