• 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
run loops vs. posix condition variables
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

run loops vs. posix condition variables


  • Subject: run loops vs. posix condition variables
  • From: "Aaron B." <email@hidden>
  • Date: Thu, 3 Dec 2009 13:14:11 -0500

Hi,

Let's say I am reading audio input from a device and I would like to
do some signal processing and display the results.  If the signal
processing is very computationally intensive, I expect that it should
not be done in the AudioQueue callback (I read that if real-time
threads are too compute-bound, they can be demoted in priority).  So I
should dump the audio data in a buffer that gets processed by another
thread.  My question is: do I have to fiddle with the "run loop"
methods of this second thread?  I mean, in a very simple
producer-consumer scenario such as this, is there any reason that the
run loop thread control interface is superior to simple POSIX
condition variables?

 - Aaron
 _______________________________________________
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

  • Follow-Ups:
    • Re: run loops vs. posix condition variables
      • From: William Stewart <email@hidden>
  • Prev by Date: Re: buggy AUMatrixReverb, reaper ??
  • Next by Date: Re: run loops vs. posix condition variables
  • Previous by thread: Re: iPhone - RenderCallback not called when phone is locked
  • Next by thread: Re: run loops vs. posix condition variables
  • Index(es):
    • Date
    • Thread