RE: audio priority and multitasking on iOS
RE: audio priority and multitasking on iOS
- Subject: RE: audio priority and multitasking on iOS
- From: <email@hidden>
- Date: Wed, 1 Dec 2010 13:58:32 +1300
- Thread-topic: audio priority and multitasking on iOS
Ian Esten wrote:
> Niels Bogaards wrote:
> > - I use an NSLock tryLock in the callback. Is this ok? would a
> > pthread mutex/condition be better?
>
> The thing that matters most here is that you have your locks set up
> such that the RemoteIO thread does not get blocked.
There are also corner cases where dispatching an ObjC message can result
in the runtime needing to acquire a lock. I believe this post from Greg
Parker is still correct:
http://lists.apple.com/archives/cocoa-dev/2006/feb/msg01735.html
At the very least, you're venturing into undocumented territory with
unspecified behavior. If you want to minimize the chances of audio
glitches then ObjC messages (and therefore properties as well) should
probably be avoided, especially if there is a non-Objective-C equivalent
with very similar functionality (pthread mutices in this case).
--
Michael Brown
_______________________________________________
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