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 18:07:03 -0400
On May 13, 2008, at 2:45 PM, William Stewart wrote:
I'm not sure that I understand the "fixing the initialization code"
comment - could you point me to exactly what this is.
Sure- I'd been putting initialization code in 'fooKernel::Reset()'.
This sometimes works, but didn't work on Digital Performer, and
Sophia Poirier explained that wasn't really initialization code and
gave me the following code snippet:
//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~
// foo::Initialize
//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~
ComponentResult foo::Initialize()
{
ComponentResult result = AUEffectBase::Initialize();
if (result == noErr)
Reset(kAudioUnitScope_Global, 0);
return result;
}
That fixed the problem. So it appears like the template code came
without anything guaranteed to initialize variables, and I had users
getting socked with bursts of noise from uninitialized IIR filters
and such until I applied the fix :)
I don't pretend to be very good at C coding- I make my living
largely through understanding how things sound good, and beg for help
a lot when the C coding gets too baffling. But I do know I had users,
mainly on Digital Performer and I think also Logic 8, who were
suffering until I fixed this problem.
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