Re: What sort of timer should I use for my sequencer?
Re: What sort of timer should I use for my sequencer?
- Subject: Re: What sort of timer should I use for my sequencer?
- From: Brian Willoughby <email@hidden>
- Date: Thu, 3 Feb 2011 15:15:58 -0800
On Feb 3, 2011, at 13:37, Aran Mulholland wrote:
The problem I have found with generating and queuing up audio on a
separate thread on iOS devices is with thread priority issues. The
render thread has a high priority level. It always gets fired. I
don't know the reason for this, If it is hardware interrupt related
or if the thread setup is done correctly. I find that if I create
my own threads when there is heavy user interface interaction the
user interface thread receives the priority and my thread might not
get any run time. This happens when pushing a view controller or if
the user was to do something like continuously move a UISlider back
and forwards. If that user interface interaction continues and i
have not queued up enough audio to play then i get glitches. I
think on a multi core device, or one with a higher clock speed this
would not be an issue or the problem might be that I do not know
how to schedule threads correctly. The problem is a lot more
pronounced on an iPod touch 3rd gen compared to the iPhone 4.
If any knowledgable person out there can tell me how to set up the
thread to fix these issues I would be very grateful.
Look for discussions and examples mentioning fixed priority, i.e.
time constraint tread. One example is the CAPThread source in
PublicUtility.
Brian Willoughby
Sound Consulting
_______________________________________________
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