Re: AudioUnitSetProperty deadlock?
Re: AudioUnitSetProperty deadlock?
- Subject: Re: AudioUnitSetProperty deadlock?
- From: Doug Wyatt <email@hidden>
- Date: Tue, 19 Apr 2005 10:31:02 -0700
On Apr 19, 2005, at 9:46, Dominic Feira wrote:
Hello.
I have managed to create a deadlock in my Core Audio code.
Basically, I have an audio input thread that writes data to a ring
buffer which is then read from by another thread that does some
conversions on that data.
I have a notification set up on the device that I'm getting input
from to let me know when the sample rate changes. This works
fine. I then try to modify the other side of the ring buffer to
let it know that the data is now in a different sample rate.
AudioUnitSetProperty(converterUnit,
kAudioUnitProperty_StreamFormat,
kAudioUnitScope_Input,
0,
&desc,
sizeof(AudioStreamBasicDescription));
This call never returns. Anybody know why?
If you could take a sample of the process (e.g. sample <pid> 5), that
would show what's going on in all the threads -- if it's a deadlock,
the sample would provide hints if not an absolute indication of where
the deadlock is.
Doug
_______________________________________________
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