Hi Jeff,Thanks for the reply.I'm not sure I understand your suggestion.28/02/2014 15:55:03,228 coreaudiod[511]: +PerformDeviceConfigurationChange 28/02/2014 15:55:03,228 coreaudiod[511]: +StartIO28/02/2014 15:55:03,987 coreaudiod[511]: -PerformDeviceConfigurationChange 28/02/2014 15:55:04,013 coreaudiod[511]: -StartIOshows that the driver returns from PerformDeviceConfigurationChange at 03,987. I use AudioObjectID theDeviceObjectID = GetObjectID(); CADispatchQueue::GetGlobalSerialQueue().Dispatch(false, ^{ PtASPlugInPlugIn::Host_RequestDeviceConfigurationChange(theDeviceObjectID, myChangeAction, &mConfigChangeInfo); });to request the change.Eric GoroubenLe 28 févr. 2014 à 19:08, Jeff Moore <email@hidden> a écrit :The HAL stops IO, calls PerformDeviceConfigurationChange() and then restarts IO all in a series on the same thread (actually, from the same function in HAL’s implementation to be precise). So it seems like the only way you could get the behavior you are describing is if your driver returns from PerformDeviceConfigurationChange() before the change has actually completed. Could this be the case here? --Jeff MooreCore AudioApple 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 References: >PerformDeviceConfigurationChange sequence (From: Ploytec <email@hidden>) >Re: PerformDeviceConfigurationChange sequence (From: Jeff Moore <email@hidden>) >Re: PerformDeviceConfigurationChange sequence (From: Ploytec <email@hidden>) Prev by Date: Re: PerformDeviceConfigurationChange sequence Previous by thread: Re: PerformDeviceConfigurationChange sequence Index(es): Date Thread
28/02/2014 15:55:03,228 coreaudiod[511]: +PerformDeviceConfigurationChange 28/02/2014 15:55:03,228 coreaudiod[511]: +StartIO28/02/2014 15:55:03,987 coreaudiod[511]: -PerformDeviceConfigurationChange 28/02/2014 15:55:04,013 coreaudiod[511]: -StartIO
The HAL stops IO, calls PerformDeviceConfigurationChange() and then restarts IO all in a series on the same thread (actually, from the same function in HAL’s implementation to be precise). So it seems like the only way you could get the behavior you are describing is if your driver returns from PerformDeviceConfigurationChange() before the change has actually completed. Could this be the case here? --Jeff MooreCore AudioApple 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 References: >PerformDeviceConfigurationChange sequence (From: Ploytec <email@hidden>) >Re: PerformDeviceConfigurationChange sequence (From: Jeff Moore <email@hidden>) >Re: PerformDeviceConfigurationChange sequence (From: Ploytec <email@hidden>) Prev by Date: Re: PerformDeviceConfigurationChange sequence Previous by thread: Re: PerformDeviceConfigurationChange sequence Index(es): Date Thread