• 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: Audio Unit (debug) output parameters
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Audio Unit (debug) output parameters


  • Subject: Re: Audio Unit (debug) output parameters
  • From: William Stewart <email@hidden>
  • Date: Wed, 24 Jan 2007 14:07:08 -0800

This isn't quite correct.

To get the meter you should do two things:
(1) Declare the parameter as read only - the type can be anything except a boolean - for instance we use dB in the one you mentioned
(2) Also declare the parameter to have a type of kAudioUnitParameterFlag_MeterReadOnly


Both of the generic views we provide will then treat the parameter as a read only meter parameter and provide a meter API.

The view then sets up a timer for this param to draw at some frequency - and as it wakes up it will ask your AU to provide the value for this parameter - you can either calculate it then, or returned a value that you might have calculated in the Render function.

This is why we added the meter flag for a param, so we know which params we need to treat this way. One thing that I would NOT do for this kind of parameter is send a notification that the value has changed - if you are metering audio, then this is changing very often - far more often than a UI needs or can draw it.

Bill

On 09/01/2007, at 8:42 AM, Stefan Gretscher wrote:

Hi Frank,

Am 09.01.2007 um 16:42 schrieb Frank Schoep:
How would I go about updating the value from within my Audio Unit so that the host application knows to redraw the control?
In order for the host or any views attached to the AU to pick up changes an AU might apply to its parameters, they must be notified using AudioUnitEvents as described in this technote:
http://developer.apple.com/technotes/tn2002/tn2104.html
This is true both for read-only (displays) and for read+write (automatable) parameters.


Best,
Stefan

_______________________________________________
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


References: 
 >Re: Audio Unit (debug) output parameters (From: Stefan Gretscher <email@hidden>)
 >Re: Audio Unit (debug) output parameters (From: Frank Schoep <email@hidden>)
 >Re: Audio Unit (debug) output parameters (From: Stefan Gretscher <email@hidden>)

  • Prev by Date: Re: Does CoreAudio use the alarm signal in the IO proc thread?
  • Next by Date: Re: Audio Unit UIs in Java (JNI) App
  • Previous by thread: Re: Audio Unit (debug) output parameters
  • Next by thread: Crash in MusicPlayerStart - OS X bug?
  • Index(es):
    • Date
    • Thread