Re: AU validation
Re: AU validation
- Subject: Re: AU validation
- From: Pavol Markovic <email@hidden>
- Date: Tue, 1 Nov 2005 07:03:47 +0100
On Oct 31, 2005, at 9:42 PM, Muon Software Ltd - Dave wrote:
It has set arbitrary values (with the parameter's ranges), retrieved
the "set" value, and cached that.
It then uninitialised (if you had to be initialised) the AU,
Initialises it, and gets the value for each parameter in its cache
and sees if it has changed. Its not trying to do anything clever
here, but rather trying to simulate a "typical" usage scenario that
would occur say when the sample rate of the AU had to change for some
reason...
Hmm. In use, this shouldn't affect our plugin. But when auval is
trying to
do this test there are no patches assigned on any of our multitimbral
parts
and so the parameter changes are ignored.
What's puzzling me at the moment is why some parameters get this error
and
some don't. I will take your suggestion and debug a bit in AU Lab.
Maybe some of the parameters change other parameters. Then you have to
specify Meta flag for them (and since OS X 10.4 you can also provide
dependent parameters list).
PM
_______________________________________________
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