• 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: Listening To kAudioDeviceProcessorOverload From AudioUnit
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Listening To kAudioDeviceProcessorOverload From AudioUnit


  • Subject: Re: Listening To kAudioDeviceProcessorOverload From AudioUnit
  • From: Jeff Moore <email@hidden>
  • Date: Wed, 20 Jun 2007 18:30:50 -0700


On Jun 20, 2007, at 6:19 PM, Eric Eizenman wrote:

Thanks Jeff.

I'm only interested in kAudioDeviceProcessorOverload for debug purposes, so no output unit is acceptable. It would be good enough if it works only with AU Lab.

I guess you missed where I said that was not something you could find out from inside an AU. There is no API for this, inside AU Lab or otherwise.


While looking for clues, I stumbled across the AUTracer. From reading the comments I think it might do what I'm looking for. AUTracer::Establish has some code to get kAudioOutputUnitProperty_CurrentDevice which I might try.

AUTracer doesn't do what you think it does. First, it is not an Audio Unit. It is a C++ class. Second, it requires that the instantiator of the class call the Establish() method to tell the instance of AUTracer what the output unit is.


The idea is to use WTF in Shark and programmatically stop tracing when kAudioDeviceProcessorOverload is detected.

You might want to look at the IO cycle telemetry support in HALLab. It provides a glimpse inside the functioning of the HAL as well as providing kernel tracing based on telemetry events.



On Jun 20, 2007, at 2:17 PM, Jeff Moore wrote:

That's not something you can find out from inside an AudioUnit. The main problem is what to do if your AU isn't attached to an output unit or the HAL. I'm sure there are other wrinkles as well that make figuring this out dicey if it is even possible.

On Jun 20, 2007, at 1:59 PM, Eric Eizenman wrote:

I would like to programmatically listen to kAudioDeviceProcessorOverload from my AU.
What steps do I need to take in order to get the current Output Unit component instance, to be used in AudioUnitAddPropertyListener ?

--

Jeff Moore
Core Audio
Apple


_______________________________________________ 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


--

Jeff Moore
Core Audio
Apple


_______________________________________________ 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: 
 >Listening To kAudioDeviceProcessorOverload From AudioUnit (From: Eric Eizenman <email@hidden>)
 >Re: Listening To kAudioDeviceProcessorOverload From AudioUnit (From: Jeff Moore <email@hidden>)
 >Re: Listening To kAudioDeviceProcessorOverload From AudioUnit (From: Eric Eizenman <email@hidden>)

  • Prev by Date: Re: Listening To kAudioDeviceProcessorOverload From AudioUnit
  • Next by Date: Re: Multi Channel FFT Audio Anaylzer
  • Previous by thread: Re: Listening To kAudioDeviceProcessorOverload From AudioUnit
  • Next by thread: "Bit width" vs "bit depth"
  • Index(es):
    • Date
    • Thread