• 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: OSX callback, is this OK?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OSX callback, is this OK?


  • Subject: Re: OSX callback, is this OK?
  • From: Neil Mix <email@hidden>
  • Date: Tue, 18 Jan 2011 21:27:54 -0600

On Jan 18, 2011, at 6:51 PM, Brian Willoughby wrote:

> Isn't NSNotificationCenter based on Objective C?  If so, then I'd say: No, that is not the way to go, at least not from within your CoreAudio callback.

Is that true for AudioQueue callbacks?  I know you can't block in an AudioUnit render callback, but I thought AudioQueue buffer callbacks were scheduled differently.  It lets you specify the runloop on which to execute the callback -- surely it doesn't block the internal render to wait for the buffer callback to execute on another thread...?


 _______________________________________________
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: 
 >OSX callback, is this OK? (From: Paul Fredlein <email@hidden>)
 >Re: OSX callback, is this OK? (From: Brian Willoughby <email@hidden>)
 >Re: OSX callback, is this OK? (From: Paul Fredlein <email@hidden>)
 >Re: OSX callback, is this OK? (From: Brian Willoughby <email@hidden>)

  • Prev by Date: Re: OSX callback, is this OK?
  • Next by Date: Big Top results
  • Previous by thread: Re: OSX callback, is this OK?
  • Next by thread: AC-3 decode in Leopard+
  • Index(es):
    • Date
    • Thread