RE: AudioDeviceStop and ioProc
RE: AudioDeviceStop and ioProc
- Subject: RE: AudioDeviceStop and ioProc
- From: "Tim Dorcey" <email@hidden>
- Date: Thu, 11 May 2006 15:55:29 -0700
- Importance: Normal
> The HAL uses a mutex to force things that affect the IO thread to
> happen when the IO thread isn't running. This says nothing about how
> long a call to AudioDeviceStop() will have to wait before
> it's effect
> is achieved when called from a thread other than the IO thread.
>
> For example, if you make a call to AudioDeviceStop() and there are
> other threads of a higher priority already waiting for the IO thread
> mutex, then there's a very good chance that the thread calling
> AudioDeviceStop() won't get time to execute for a while. This can
> lead to any number of calls to your IOProc in the meantime.
Okay, but that means my AudioDeviceStop() will not return until the last
call to my ioProc has been made, right? I don't care how long the Stop
actually takes to complete, just that there will be no more calls to my
ioProc once my AudioDeviceStop *returns.* That's what I meant to ask. Is
that right, then?
Tim
_______________________________________________
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