• 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: ClassInfo & PresentPreset confusion
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ClassInfo & PresentPreset confusion


  • Subject: Re: ClassInfo & PresentPreset confusion
  • From: Marc Poirier <email@hidden>
  • Date: Mon, 10 Oct 2005 11:18:01 -0400

On Oct 10, 2005, at 10:43 AM, Michael Kleps wrote:

The very first thing I do is call the default implementation (AUBase::RestoreState and AUBase::SaveState). BTW, none of these methods (Restore or SaveState) are even called by the AU Validation tool...

The ClassInfo property is Set and Get by auval on my AUs, so there's a sign that something's going wrong in your case. Could it be some virtual method error (getting the function prototype wrong in some respect so that you're hiding the parent version)? Or perhaps you are doing something wrong in the way that you are monitoring whether this happens or not?


Marc, I am afraid that you are more guessing then knowing, but your quick reaction and your right use of the terminology gives most developer here the impression that your answers are right and that looking into this isn't necessary.

???

If neither property is set/get, no savestate/restorestate is called, how can the AU Validation tool possibly check for any changed names?

But that is not true. What makes you think that is true?

I don't have ANY au_presets...

So the code you just posted basicly get the current preset (although I have none?), and then sets the "name" of in my State dictionary to the name of the preset that shouldn't exist in the first place?

Note that the PresentPreset/CurrentPreset property is not strictly about factory presets. It stores the name of whatever the current AU settings state is, whether that be a user setting applied via the ClassInfo property, or a factory preset. So yes, the property applies to yours and every AU, regardless of whether the AU provides factory presets. See:


/Developer/Examples/CoreAudio/Documentation/AudioUnits/Topics/ au_properties.html#AudioUnitPresetsandPersistence

/Developer/Examples/CoreAudio/Documentation/AudioUnits/Topics/ au_properties.html#kAudioUnitProperty_CurrentPreset


Marc _______________________________________________ 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: ClassInfo & PresentPreset confusion
      • From: Michael Kleps <email@hidden>
References: 
 >ClassInfo & PresentPreset confusion (From: Michael Kleps <email@hidden>)
 >Re: ClassInfo & PresentPreset confusion (From: Marc Poirier <email@hidden>)
 >Re: ClassInfo & PresentPreset confusion (From: Michael Kleps <email@hidden>)

  • Prev by Date: Re: ClassInfo & PresentPreset confusion
  • Next by Date: Re: Speeding up MusicPlayerStart()?
  • Previous by thread: Re: ClassInfo & PresentPreset confusion
  • Next by thread: Re: ClassInfo & PresentPreset confusion
  • Index(es):
    • Date
    • Thread