Re: Load/Save Presets does not work
Re: Load/Save Presets does not work
- Subject: Re: Load/Save Presets does not work
- From: Bill Stewart <email@hidden>
- Date: Mon, 3 Mar 2003 10:14:53 -0800
On Monday, March 3, 2003, at 06:26 AM, Urs Heckmann wrote:
Am Montag, 03.03.03, um 14:44 Uhr (Europe/Berlin) schrieb
email@hidden:
First, thanks Urs for the quick reply. I'm (relatively) happy to see
that I'm not the only one.
I have experienced exactly the same problem. That's why I also save
my public parameters in my custom data chunk.
I was thinking of it. I would be glad to know if it could interfere
in other hosts (if it is a Logic bug).
It's not a Logic bug AFAIK. My workaround does a good job in every
host I tested with. It shouldn't be a problem.
Don't forget to call SetParameter() for each parameter to get the
stuff set / GUI notified.
SetParameter does NOT notify anyone that there is a change in the value
of a parameter... Normally we don't expect the AU to do this itself,
thus we don't have the AU do notifications...
I have sample code in my CAUGuiSDK at www.u-he.com/audiounits/
Urs - I think you should change this notification stuff.... that should
really be a comment/doc issue to say IF you have to set parameter
values behind the GUI/Users' back, then you should also explicitly call
the notification method yourself.
We really don't expect that the AU takes care of this itself (that is
why in AudioUnit Hosting when you restore a saved preset state it
actually goes through and calls the notification method itself) -
This is an onus we also place on host applications of course... So -
if you're SetParameter call is also doing notifications you will be
adding work for no reason and shouldn't do this.
Bill
I looked at Save/Restore in AUBase some time ago and have not found
the code that should save public parameters in the "data" key.
There's only the code in AUScopeElement which I havn't traced if it
gets called at all.
It is not. All loops is Save/Restore are empty, because there are no
parameters whatever scope, element.
So where do that bug come from ?
Any one at apple ? is that normal ? is there an obvious thing we did
not understand here ?
I really don't exactly understand what's going on in AUBase's
Save/RestoreState 8-)) Too many type conversions, endian swapping,
strange data structures (hdr...) and what have you...
... I can happily live with my much simpler approach...
;) Urs
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.