• 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: kAudioUnitProperty_ParameterList
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: kAudioUnitProperty_ParameterList


  • Subject: Re: kAudioUnitProperty_ParameterList
  • From: William Stewart <email@hidden>
  • Date: Thu, 11 May 2006 12:57:20 -0700


On 10/05/2006, at 6:05 PM, Bjorn Roche wrote:

On Wed, 10 May 2006, William Stewart wrote:


On 10/05/2006, at 3:55 PM, Bjorn Roche wrote:

Hay all,

when I query the parameters in an AudioUnit with kAudioUnitProperty_ParameterList, am I guaranteed to always get the same parameters in the same order, provided I have set the sample format and so on the same way each time?
No

(I am trying to manager persistence of automation data and I need to know to what extent I need to verify that the Audio Unit gave me what I expected in the order I expected it. Order is important.)

Order is irrelevant.

Parameter's are keyed by an ID (and the ID's may NOT be contiguous) and the developer's AU is responsible for managing the persistence and applicability of these IDs.

Good to know they might come out of order. Will I always get the same set of parameters?
No, parameter lists can change and the AU is responsible for notifying the host of these changes. It is up to the AU developer to maintain some semblance of commpatibility between parameters an AU publishes and their actions.


As a side note: Is there any significance to the order?
We use it as a display order in the generic view - which displays parameters in ascending order. (CoreAudioKit/AUGenericView.h)

Right now, I am using the order to for the order I display to the user, but I plan to use the clumpID for that, since that seems to be the intent of clumpID.

Sure, but within the clumps themselves you still have to display parameters - have a look at the AUMultibandCompressor in AULab as a good example I think of clumps and param ID values.


Bill

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


References: 
 >kAudioUnitProperty_ParameterList (From: Bjorn Roche <email@hidden>)
 >Re: kAudioUnitProperty_ParameterList (From: William Stewart <email@hidden>)
 >Re: kAudioUnitProperty_ParameterList (From: Bjorn Roche <email@hidden>)

  • Prev by Date: Re: 'AudioUnitScheduleParametersProc' does not name a type
  • Next by Date: Re: Simple AudioCodec question
  • Previous by thread: Re: kAudioUnitProperty_ParameterList
  • Next by thread: ramp parameters
  • Index(es):
    • Date
    • Thread