Re: Initialization of parameters
Re: Initialization of parameters
- Subject: Re: Initialization of parameters
- From: Howard Moon <email@hidden>
- Date: Tue, 22 Apr 2008 15:29:14 -0700
Ok, thanks... I'll keep those SetParameter calls in, then. (And I
have verified that, at least in Logic, I need them.) But I have
three follow-up questions in that case:
1) I've traced the code for SetParameter, and it appears to me that
your point (1) below is only valid when *not* using indexed
parameters, in which case a new parameter is added to the
AUElement::mParameters map the first time SetParameter is called.
I'm using indexed parameters at the moment, so I think that only
point (2) applies. Correct?
2) What is the purpose of setting
AudioUnitParameterInfo::defaultValue for each parameter (in
GetParameterInfo), if it doesn't actually set the default value?
3) Is this information documented anywhere? (And by this I mean both
the requirement of calling SetParameter, and the purpose of the
defaultValue member.)
Thanks again,
-Howard
On Apr 22, 2008, at 2:50 PM, William Stewart wrote:
The calls in the constructor are required:
(1) Creates a space in the element for that parameter
(2) Sets the default value of the parameter
If you don't do this, then you don't have the parameter
On Apr 22, 2008, at 8:47 AM, Howard Moon wrote:
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?
_______________________________________________
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