How to handle "mode" parameters that fix the value of other parameters?
How to handle "mode" parameters that fix the value of other parameters?
- Subject: How to handle "mode" parameters that fix the value of other parameters?
- From: "B.J. Buchalter" <email@hidden>
- Date: Fri, 30 May 2014 12:54:40 -0400
Hi Folks,
We have an AU we are working on that is currently failing auval in the "retain value across reset and initialization":
> Testing that parameters retain value across reset and initialization
> ParameterID=XXXX, Scope=0, Element=0: Saved Value = 4587.036133, Current Value 500.000000
> ParameterID=YYYY, Scope=0, Element=0: Saved Value = 433.105469, Current Value 500.000000
> ERROR: Parameter did not retain set value when Initialized
These parameters are affected by a different "mode" parameter. The "mode" parameter is declared as global meta, and these parameters are dependent on it. When the mode parameter is set to a specific value, then these parameters are free to be set by the user. But if the mode parameter is any other value, it controls the values of these parameters and they cannot be changed by the user.
auval does not seem to check for the dependent parameters property during its testing.
So, the problem appears to be that auval does the following:
Sets the values of XXXX and YYYY
Resets the AU
Initializes the AU
Checks the values of XXXX and YYYY
At the Initialize phase, the AU re-sets the values of XXXX and YYYY based upon the value of the mode parameter.
Should I be rejecting changes to XXXX and YYYY when the mode has them fixed? Will that work, or cause a different auval failure?
How should I be handling this so that the plugin passes (1) auval, and (2) continues to work as expected.
B.J. Buchalter
Metric Halo
http://www.mhlabs.com
_______________________________________________
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