• 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: AudioQueueNewOutput and the runloop
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AudioQueueNewOutput and the runloop


  • Subject: Re: AudioQueueNewOutput and the runloop
  • From: patrick machielse <email@hidden>
  • Date: Wed, 14 Nov 2012 16:31:53 +0100

Op 9 nov. 2012, om 12:42 heeft Irradiated <email@hidden> het volgende geschreven:

> I believe you can pass a NULL in for the run loop modes and it will do its own thread management:
> AudioQueueNewOutput( &mDataFormat, UKSoundAQBufferCallback, self, NULL, NULL, 0, &mQueue );

That's what we tried initially.

It doesn't seem to matter if we let the queue handle its wown thread, if we supply a thread / runloop, or if we use IORemote directly instead of an AudioQueue to drive our audio processing. There seems to be some kind of issue using AVAssetReader in conjunction with playback.

https://devforums.apple.com/thread/172101

p.
 _______________________________________________
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: AudioQueueNewOutput and the runloop
      • From: Bill Phillips <email@hidden>
  • Prev by Date: Re: Forwarding Audio from an Output Device to a different output device
  • Next by Date: Re: AudioQueueNewOutput and the runloop
  • Previous by thread: Audio Units - interleaved vs deinterleaved
  • Next by thread: Re: AudioQueueNewOutput and the runloop
  • Index(es):
    • Date
    • Thread