Re: Initialization of parameters
Re: Initialization of parameters
- Subject: Re: Initialization of parameters
- From: Howard Moon <email@hidden>
- Date: Tue, 22 Apr 2008 10:14:34 -0700
In the AU examples I've seen, the constructor of the AU calls
SetParameter with default values for the parameters. Is that
needed? I would expect, since the GetParameterInfo function
override sets the default value, that the host (or some part of the
AU base class hierarchy) would use that default information to call
SetParameter for us. Am I mistaken? Or are the calls to
SetParameter in the constructor redundant?
On a more general note: am I missing something, or is there a lot of
undocumented stuff in the Audio Units world? I can't find anything
anywhere (Google, ADC search, headers, etc.) which tells me exactly
how some of these things are used (or are expected to be used).
The defaultValue member of the AudioUnitParameterInfo structure is
one example. Who uses this information, and how? Is it something
the host is supposed to use? Or is it just a convenience for me?
If I'm going to rewrite all my VST and RTAS software as native AU, it
would help to know where I *need* to make changes, and where I can
keep data structures and functionality that I've been using for years
(e.g., for such things as the minimum, maximum and default param
values). The examples are fine, as far as they go, but they don't
tell me how to proceed to expand on them to make real-world AUs.
Is there some documentation I'm not finding that explains some of
this better? (Or is this list my best bet for more information?)
Thanks,
-Howard
_______________________________________________
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