Re: AudioDeviceStop and ioProc
Re: AudioDeviceStop and ioProc
- Subject: Re: AudioDeviceStop and ioProc
- From: Steve Checkoway <email@hidden>
- Date: Tue, 23 May 2006 20:25:44 -0700
Shaun Wexler wrote:
On May 23, 2006, at 4:37 PM, Steve Checkoway wrote:
The main thread (thread 2) only interacts with the audio when
starting the device or shutting it down or telling the decoder thread
to decode another chunk of audio.
Beware: start/stop and other HAL notification callbacks may be sent
on arbitrary threads, often one of the IOProc threads. Do not assume
or rely on them being delivered on the dedicated notification runloop
thread. ;)
Surely it can't be sent on a an arbitrary thread! If it tried to deliver
a notification on thread 2 (in this case) it'd be in a for a shock as
there is no runloop being run. I could see it happening on an arbitrary
thread that the HAL owns or one I've told it to use.
- Steve
_______________________________________________
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