AU Parameter confusion on PPC
AU Parameter confusion on PPC
- Subject: AU Parameter confusion on PPC
- From: Justin Carlson <email@hidden>
- Date: Tue, 4 Sep 2007 22:44:05 -0500
Hi CA-API List,
I have a peculiar problem. Has anybody noticed differences or
problems setting or recalling parameters across architectures? I have
an AU (synth) with a Cocoa UI that appears to be working perfectly
under Intel across all hosts I have tested with (Logic, GB, AU Lab,
Plogue Bidule...).
When I load this plug and UI on PPC I see very different results. I
see problems such as parameter ID offsets and some hosts not
receiving notifications for state changes, including improper state
storage and recall (again, parameter ID offset of 2 but behaviours
differ from host to host). For example, AU Lab receives notifications
from the UI for adjustments, Logic and GarageBand do not acknowledge
state changes for parameters adjusted from my UI. When settings are
recalled from AU Lab (reload the .trak document) there is a parameter
offset of 2 for the values entered from the UI. When loaded in Logic
(for example) I can adjust the UI's parameter and the values are set.
At least, they are immediately written properly because the
difference is audible. Though this parameter change does not dirty
the doc - nor is the proper state saved or recalled correctly. In
this example, it can work from the generic controls view - though
this has an offset of parameter ID + 2 when recalled. Such as:
Parameter 4's newly set value is recalled and set in parameter 6's
value.
I have verified indexed parameters are not in use and this is only on
PPC. The first parameter in use is 1 and there are hundreds of unused
parameters across the entire range of used parameters. Indexed
parameters do not appeal to me because this specific AU has hundreds
of parameters, nicely spanned into groups with room for growth.
So... has anybody had experience with this problem? If I am alone,
then that is at least an indication it is in my implementation, build
settings, or oversight in architectural differences. Practically
everything regarding this area of the implementation adheres to
examples (i.e. Demo Filter's use of AUParameterSet) -- without
overrides (of AUBase, etc.). I don't use different implementations in
this regard for each architecture.
10.4.10 and Xcode 2.4.1 was used for both machines for testing and
building. 10.4u was the target SDK. Any other info needed?
TIA,
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