• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Frustrated w. generic AUs not returning to settings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Frustrated w. generic AUs not returning to settings


  • Subject: Re: Frustrated w. generic AUs not returning to settings
  • From: William Stewart <email@hidden>
  • Date: Wed, 5 Sep 2007 12:36:51 -0700

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)

Bill

On 04/09/2007, at 8:03 PM, Chris Johnson wrote:


So I'm not sure where exactly to turn here, but I've just seen the 9,000,000th example of one of my users being sad because Logic doesn't retain their settings on my plugins after saving and quitting. This makes me crazy because I'm using the generic interface and to the best of my knowledge my AU code doesn't have ANY way to remember or return to its own settings- it tells Logic what controls are there and Logic saves them somehow and feeds the plugin back the desired settings- or not.


Does anyone have any idea what's happening? Why can't Logic do this, am I missing something? Why does Logic sometimes grab the control (including on my Density plug which can put out dangerous levels of boost) and, on click, slam it to full crank? Is there ANY way I can control these things within my plugin? Is there any way I'm inadvertently causing them through mistake or negligence? The generic AU stuff looks pretty direct to me and I don't see any angle from which I can attack the problems.

	Help?

	Chris Johnson
	airwindows
_______________________________________________
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

--
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
________________________________________________________________________ __


_______________________________________________
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


  • Follow-Ups:
    • Re: Frustrated w. generic AUs not returning to settings
      • From: Chris Johnson <email@hidden>
References: 
 >Frustrated w. generic AUs not returning to settings (From: Chris Johnson <email@hidden>)

  • Prev by Date: Stuck notes - dropped midi events - solved.
  • Next by Date: Re: AU Parameter confusion on PPC
  • Previous by thread: Frustrated w. generic AUs not returning to settings
  • Next by thread: Re: Frustrated w. generic AUs not returning to settings
  • Index(es):
    • Date
    • Thread