• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: iPhone and time constraint threads
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: iPhone and time constraint threads


  • Subject: Re: iPhone and time constraint threads
  • From: Jeff Moore <email@hidden>
  • Date: Wed, 25 Nov 2009 14:58:33 -0800

Near as I can tell, there isn't any restriction on a user application making a time constraint thread. In fact, the AURemoteIO does exactly that as part of it's operation. We just use the CAPThread code from our PublicUtility code in our SDK.

Is your code significantly different from what CAPThread is doing? If not, I'm at a loss to explain what you are seeing.


On Nov 25, 2009, at 12:02 PM, Stéphane Letz wrote:

> We are testing audio code that uses the low level mach API to set up "time constraint" for real-time threads (using thread_policy_set with THREAD_TIME_CONSTRAINT_POLICY_COUNT). The same code runs OK on OSX but gives the KERN_INVALID_ARGUMENT error when running on an iPhone (actually an iPod Touch)
>
> Are there any special restrictions concerning threads on iPhone OS? If yes are they any other API to be used instead to setup high-prority (even real-time) threads?


--

Jeff Moore
Core Audio
Apple



 _______________________________________________
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

References: 
 >iPhone and time constraint threads (From: Stéphane Letz <email@hidden>)

  • Prev by Date: Re: Re: iPhone - RenderCallback not called when phone is locked
  • Next by Date: Re: choppy audio recording
  • Previous by thread: iPhone and time constraint threads
  • Next by thread: Problem with same DeviceID for input and output for Playback
  • Index(es):
    • Date
    • Thread