Re: Listening To kAudioDeviceProcessorOverload From AudioUnit
Re: Listening To kAudioDeviceProcessorOverload From AudioUnit
- Subject: Re: Listening To kAudioDeviceProcessorOverload From AudioUnit
- From: Eric Eizenman <email@hidden>
- Date: Wed, 20 Jun 2007 18:19:05 -0700
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.
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.
The idea is to use WTF in Shark and programmatically stop tracing
when kAudioDeviceProcessorOverload is detected.
------------------------------------------------------------------
Eric Eizenman
BIAS Inc., Audio Software Development
------------------------------------------------------------------
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:
inc.com
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