• 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: Varying number of parameters for an AU
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Varying number of parameters for an AU


  • Subject: Re: Varying number of parameters for an AU
  • From: Stephen Blinkhorn <email@hidden>
  • Date: Sat, 17 Jul 2010 14:40:52 -0600

On 17 Jul 2010, at 11:36, Alex Weiss wrote:

Hi Stephen,

that was my first thought as well. However, as you mentioned, the problem with this approach is that in some situations the host would still show all parameters, for example when it displays the generic view or when it lets the user decide which parameters to automate.

You can flag a parameter as non real-time (kAudioUnitParameterFlag_NonRealTime) in GetParameterInfo() which should exclude a parameter from appearing in automation lists.


I don't know if there is a way to inform the host that it should hide a parameter from a generic view or not. I know you can update a parameter's name and then send a PropertyChanged notification to the host (you could set unused parameters to "N/A" or similar). Upon receiving this notification the host should call GetParameterInfo() again and update the generic view with the new names. However, this approach has varying degrees of success as many hosts don't support such dynamic behaviour. AULab does. Have you tried this approach already? You may need to write a custom view.

Stephen


Alex

On Sat, Jul 17, 2010 at 6:48 PM, Stephen Blinkhorn <email@hidden > wrote:
Hi Alex,


I'd create the AU with the maximum number of parameters your design will be asked to cater for. If you need 2 extra parameters per channel and you may be asked to process 8 channels then cater for 16 parameters upfront. You could probably show/hide these parameters in your AU view although I don't know how flexible that is for a generic view.

Stephen



On 17 Jul 2010, at 10:05, Alex Weiss wrote:

Hi,

I was wondering if the number of parameters of an AU can vary based on the number of channels it is processing. In my case, I'd like to have some separate parameters for each channel. Is that possible? If so, what would be the best way to implement it?

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

_______________________________________________
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


_______________________________________________ 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: 
 >Varying number of parameters for an AU (From: Alex Weiss <email@hidden>)
 >Re: Varying number of parameters for an AU (From: Stephen Blinkhorn <email@hidden>)
 >Re: Varying number of parameters for an AU (From: Alex Weiss <email@hidden>)

  • Prev by Date: Re: skips in file using ExtAudioFileWrite in aac
  • Next by Date: Re: 2 AUCocoaView implementation questions: How to deal with uninitialized AU, and restrict Host to single view.
  • Previous by thread: Re: Varying number of parameters for an AU
  • Next by thread: expected behavior of AU Component Manager scans?
  • Index(es):
    • Date
    • Thread