Re: AU from scratch...?
Re: AU from scratch...?
- Subject: Re: AU from scratch...?
- From: William Stewart <email@hidden>
- Date: Wed, 13 Oct 2010 10:49:28 -0700
We have an example AU for an instrument: The SinSynth example.
On Oct 12, 2010, at 9:08 PM, Brian Willoughby wrote:
>
> On Oct 12, 2010, at 14:08, audioboy 77 wrote:
>> I am looking to port an existing VST instrument to AU. Basically what I am looking for are the relevant entry callbacks, and callbacks for the get & set parameter calls, the midi input, plus the audio process function. The XCode example seems to be very complicated, with a large class hierachy and lots of dependencies. I also havent found a way to add this to an existing XCode project (I already have an XCode project with a standalone version, and want to add a AU target - but I coudn't get this to work).
>>
>> Are there any known examples of a "minimal" AU implementation, or at least pointers to some docs that explain the "raw" API? All the docs I saw seem to tell me to just use the template example, but there must surely be a much more clean way to set things up..??
> In my opinion, the example AudioUnit sources are minimal. Sure, there are many class files in the project, but they are all segregated into a separate group, and you don't really need to look at them unless you have questions about how everything works. There is only one file that you really need to look at, at that is Filter.cpp or MultitapAU.cpp, depending upon which example you look at.
>
> If you want to do a decent job of porting from VST to AU, then you really need to understand both API. There really isn't a shortcut for doing a professional job. Of course, if this isn't a professional project, then I can see why you might not want to put the usual amount of effort into it.
>
> Start with the ReadMe.rtf in the CoreAudio Examples, then read the header files and comments in the sources for the particular projects. If you have thorough knowledge of VST, and you also have an understanding of the new features in AudioUnits (real parameter units, support for arbitrary multichannel setups, in-place versus out-of-place processing) then you should be able to figure it out.
>
> The quickie VST-to-AU converters out there will not enable any of the new features in AU that are still missing from VST. Your users will particularly miss out if the parameters do not have realistic values, because the simple 0.0-1.0 range of VST is counter-intuitive.
>
> Brian Willoughby
> Sound Consulting
>
> _______________________________________________
> 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
_______________________________________________
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