AudioQueueNewOutput and the runloop
AudioQueueNewOutput and the runloop
- Subject: AudioQueueNewOutput and the runloop
- From: patrick machielse <email@hidden>
- Date: Thu, 18 Oct 2012 01:06:56 +0200
In my (iOS) application I use an AudioQueue. It is created like this:
AudioQueueNewOutput(&asbd, queueCallback, (__bridge void *)self, NULL, kCFRunLoopCommonModes, 0, &newQueue);
in 'queueCallback', eventually AVAssetReader is used to decode frames from an audio file
CMSampleBufferRef nextBuffer = [output copyNextSampleBuffer];
Sometimes this call hangs:
Thread 21 AQClient, Queue : (null)
#0 0x3a0bdeb4 in mach_msg_trap ()
#1 0x3a0be04c in mach_msg ()
#2 0x38043044 in __CFRunLoopServiceMachPort ()
#3 0x38041da2 in __CFRunLoopRun ()
#4 0x37fb4ebc in CFRunLoopRunSpecific ()
#5 0x37fb4d48 in CFRunLoopRunInMode ()
#6 0x3842e658 in -[AVRunLoopCondition _waitInMode:untilDate:] ()
#7 0x383e49b8 in -[AVAssetReaderOutput copyNextSampleBuffer] ()
When this happens, the main thread is stopped at an @synchronized() block.
Is there any connection between the runloop of the main thread and the runloop configuration of the AudioQueue that might explain this?
Could I configure my queue in AudioQueueNewOutput() in a different way?
Thanks,
patrick
--
Patrick Machielse
Hieper Software
http://www.hieper.nl
email@hidden
_______________________________________________
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