RE: Question about stopAudioEngine()
RE: Question about stopAudioEngine()
- Subject: RE: Question about stopAudioEngine()
- From: "David Tan" <email@hidden>
- Date: Wed, 7 Jan 2009 09:36:23 +0800
Hi Jeff,
Many thanks for your
reply!
I have found the reason. I
didn’t call setState(kIOAudioEngineStopped) in the my overridden stopAudioEngine().
It seems IOAudioFamily expects this state change to terminate the session.
Otherwise it will keep on
call stopAudioEngine().
Sincerely yours,
David Tan
Dextrys, Co., Ltd.
From:
coreaudio-api-bounces+david.tan=email@hidden
[mailto:coreaudio-api-bounces+david.tan=email@hidden] On Behalf Of Jeff Moore
Sent: 2009年1月7日
4:08
To: CoreAudio-API Mailing List
Subject: Re: Question about
stopAudioEngine()
That's pretty odd. I've never seen a problem like
that. I imagine that there is something going on in your driver that is
keeping things from stopping even after stopAudioEngine() is called. Perhaps
there is some bit of state you aren't updating correctly or an inherited
function that you are forgetting to call?
On Dec 23, 2008, at 11:13 PM, David Tan wrote:
I encounter a strange problem
while debugging a FireWire audio driver.
While using application to play music (iTunes
and HALLab), it seems that the IOAudioFamily gets into a loop of calling
stopAudioEngine().
In output of FireLog, the message of
stopAudioEngine() keeps outputting unless I unload the KEXT. I added a log to
print the current status of the audio engine and it indicates Running.
Anyone has idea of it? Thanks a lot!
--
Jeff Moore
Core Audio
Apple
|
_______________________________________________
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