Re: Moving our AU plugin to Leopard/Xcode3
Re: Moving our AU plugin to Leopard/Xcode3
- Subject: Re: Moving our AU plugin to Leopard/Xcode3
- From: Chris Johnson <email@hidden>
- Date: Tue, 13 May 2008 12:45:54 -0400
On May 13, 2008, at 11:38 AM, Olivier Tristan wrote:
tahome izwah wrote:
I agree in general.
But AUCarbonViewBase::HandleEvent() is clearly Carbon specific, and
you don't need it in a Cocoa AU.
If you tend to support all major AU host, I don't think you can
safely do Cocoa AU GUI so far. so I guess I'll wait for this.
For myself, I will be keeping a close eye on any reports of the base
AU class requiring changes, as I'm not very good at keeping abreast
of such chaos. My work is strictly generic interface in part to
protect me from just such incompatibilities, and I'll be very
disappointed if Apple manages to screw even me up, as apart from the
actual DSP code my stuff is very crude and simple. That's happened
before, however, with Apple's failure to include a working example of
initialization code in the AU templates. I strongly encourage Apple
to provide their basic 'gain change plugin' example template in
working condition and unbroken... for those of us who aren't very
smart and can only trust that the provided example is in fact correct.
Apart from that, Audio Units rock- since fixing the initialization
code as directed by Sophia Poirier, I've had zero technical
complaints or incompatibility reports from users for my generic/host
interface plugins. Thanks CoreAudio guys- please always try to not
pointlessly screw up the basic stuff :)
Chris Johnson
airwindows
_______________________________________________
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