Re: Question about Hog Mode
Re: Question about Hog Mode
- Subject: Re: Question about Hog Mode
- From: "Stephen F. Booth" <email@hidden>
- Date: Sat, 9 Jan 2010 12:57:04 -0800
Hi Jeff,
Thanks for your reply!
> When the hog mode state changes, the HAL stops IO. This I know for sure and you can see this yourself using HALLab.
You're right, I hadn't noticed this before.
> I'm less sure about what AUHAL does in this circumstance. But, I'm pretty sure that AUHAL will not restart IO when this happens without your intervention. As to what may be still calling your input callback and render notifications, I can't really say other than they aren't being driven by the HAL at that point.
So my next question is: what is the best way to restart IO at this
point? Get the AudioDeviceID from the output unit and call
AudioDeviceStart() with a NULL IOProc? Would I need to do something
with my AUGraph to ensure continuity?
As for the notifications, perhaps it is AUGraph's internal machinery
that is still processing. The call stack looks normal:
#0 0x10000c9f4 in AudioPlayer::DidRender at AudioPlayer.cpp:1655
#1 0x10000b4bd in auGraphDidRender at AudioPlayer.cpp:150
#2 0x7fff8439c4fb in AudioUnitGraph::HandleRenderNotify
#3 0x7fff8439c559 in AudioUnitGraph::GraphRenderCallback
#4 0x10061f8cc in dyld_stub_realloc
#5 0x100624fe7 in AUGenericOutputEntry
#6 0x7fff83cd986d in HP_IOProc::Call
#7 0x7fff83cd963f in IOA_Device::CallIOProcs
#8 0x7fff83cd9475 in HP_IOThread::PerformIO
#9 0x7fff83cd7484 in HP_IOThread::WorkLoop
#10 0x7fff83cd6d57 in HP_IOThread::ThreadEntry
#11 0x7fff83cd6c85 in CAPThread::Entry
#12 0x7fff83482f8e in _pthread_start
#13 0x7fff83482e41 in thread_start
Stephen
_______________________________________________
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