Re: Frustrated w. generic AUs not returning to settings
Re: Frustrated w. generic AUs not returning to settings
- Subject: Re: Frustrated w. generic AUs not returning to settings
- From: Stefan Gretscher <email@hidden>
- Date: Thu, 6 Sep 2007 16:22:10 +0200
Hi Chris,
Am 06.09.2007 um 04:44 schrieb Chris Johnson:
On Sep 5, 2007, at 3:36 PM, William Stewart wrote:
The AUBase class provides a SaveState and RestoreState method -
this is in turn called by the host when it saves/restores settings
with the _ClassInfo property.
When Logic is saving a document it saves the state of the AU using
this property, which turns around and calls these methods. By
default the AUBase implementation will use the parameter values
stored in the Scope/Element objects and save/restore them. So if
you are using the parameter methods we recommend (see the example
implementations in the Example code) then the state should be
saved and restored for you. If you've overidden the parameter
mechanisms yourself, then you'll also have to do the extra work of
over-riding the save/restore mechanism to save and restore these
values. You can also debug this with the AULab application - the
UI window has a save/restore preset menu (and you can save
documents in AULab that will use this mechanism as well)
Thank you- this is more information than I've ever got, about the
problem.
If I'm NOT overriding the parameter mechanisms- say, for a plugin
that's doing basic sound manipulation and barely touching the
example code- where do I go to try and debug the example
implementations?
You can debug this using AU Lab, breaking in SaveState() and
RestoreState().
Remember that you can print the contents of the various CF objects
involved there from the gdb console using CFShow(object).
It looks like the GENERIC (no GUI either carbon or cocoa) plugins'
parameter methods aren't working for all my users.
Do these users happen to work on PPC? If so, see the current thread
"AU Parameter confusion on PPC" on this list, maybe you're suffering
from the same issue.
They work for me every time- I'm on Logic Express, not Logic Pro.
There should be no difference between Express and Pro in this regard.
I've got people (OK, one guy) writing to me saying they're
switching to Mac and Logic just to use my plugins- I'd be happy to
work with the Logic guys to resolve this or change anything I need to,
You can always reach the Logic team at this AU developer support
email address: email@hidden
but I've gotta do something. Now I'm wondering if I can override
the mechanisms with exactly the same code that's supposed to
already be there, and if that would help.
We'd need some more information on when the problem strikes - as it
seems to work fine at least on your machine, you should try to find
the difference in your config and the respective user's configs.
Maybe it's the PPC/Intel thing I've mentioned above.
*g* anyone I can talk to at Apple about getting linkage for that
'switching to Mac to use airwindows plugins, which (for the time
being!) are AU-only' thing?
That would be up to the marketing guys. If you sent me some more
material about your plug-in, I can forward it to marketing.
Also, you should sign up in the Macintosh product guide:
http://developer.apple.com/business/macproductsguide
Best,
Stefan
------------------------------------
Stefan Gretscher
plug-in development & 3rd party developer support
phone: (+49)-4101-495-586 (Central European Time)
AU developer support: email@hidden
TDM developer support: email@hidden
Apple GmbH
Geschäftsführung: Georges Guyon de Chemilly
Sitz der Gesellschaft: München
Amtsgericht München, HRB 66158
_______________________________________________
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