running state of driver
running state of driver
- Subject: running state of driver
- From: "Robert Penland" <email@hidden>
- Date: Thu, 7 Aug 2003 17:20:31 -0700
- Thread-topic: running state of driver
In my audio driver code, when I receive a input selector change call I perform the following operations:
pauseAudioEngine();
beginConfigurationChange();
...
(change my hardware)
...
completeConfigurationChange();
resumeAudioEngine()
What I am noticing in some applications is that if my driver was in a running state before the inputSelectorChange call is made is that it doesn't return to the running state after the call. In the IOAudioFamily code I see that the resumeAudioEngine() call just puts the audio driver into the kIOAudioEngineResume state and sends a kIOAudioEngineResumedNotification notification. Is it up to the application to respond to the kIOAudioEngineResumeNotification and get the engine running again?
Thanks,
Rob
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.