Re: AU Parameter confusion on PPC [solved]
Re: AU Parameter confusion on PPC [solved]
- Subject: Re: AU Parameter confusion on PPC [solved]
- From: Justin Carlson <email@hidden>
- Date: Thu, 6 Sep 2007 10:46:33 -0500
Hi Chris,
I replied last night but the email bounced. Here was that reply:
I did a list search following Chris's suggestion of SaveState. I'll
have a look into this (below) when I am at the G5 next. Auto-
Vectorization was defined in my builds and Chris's solution was to
disable optimization - gcc enables Auto-Vectorization only when
optimization is 2 or greater so this sounds promising.
> Subject: Re: Bug in saving user presets [Solved]
> From: Robert Abernathy <email@hidden>
> Date: Fri, 27 Jan 2006 13:00:35 +0000
>
> The problem turns out to be in AUElement. If the Auto-
> vectorization flag is set in the compiler, SaveState and RestoreState
> shift the order of the preset values. This may not show in AU's with
> a small number of presets.
In the time since I wrote that email I have done more work:
Disabling Auto-Vectorization appears to have cured the SaveState
issues on PPC. Since that aspect has been working, I have been able
to diagnose the UI <---> Parameter issues. In my implementation,
parameters were written and stored properly (assuming proper
SaveState behaviour) from the UI. My solution basically comes down to
the host you are using and how you expect your AU to behave. Once
parameters saved/loaded properly on PPC I found everything working
(i.e. in Logic) - the main difference is the differences in
mechanisms used for listening by hosts along with their response to
those events. For example, the Filter Demo (and AUNetReceive) may not
dirty Logic's document (for example) with each parameter change,
unless they are of certain types of events. If you open Filter Demo
in Logic, adjust parameters from the graphic interface - you'll see
the doc is dirtied. If you save the doc and enter the frequency into
the text field - the doc is not dirtied although the parameter is
set. This behaviour differs from host to host - these events are
recognized by AU Lab. So my confusion was really just hosts handling
things differently - which I did not realize because SaveState was
such a problem. For the time being, I have placed AUParameterSet
within gestures.
Now everything appear to be working across the hosts in PPC and
Intel. Neither of my solutions are ideal nor horrible, but they do
the job for now.
Chris, thank you again for the SaveState pointers and examples - it
was really the heart of the issue for me.
Best,
Justin
_______________________________________________
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