View Single Post
Old 30th June 2016, 09:24   #418
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
v1.7.16

Quote:
Originally Posted by chros View Post
Maybe the "hooking" that you mentioned before can be used to workaround these?
What's new?
  • Added a means to the trace that messages written from different threads don't mix up.
  • Added more informative messages to the trace regarding the impact of un-plugging the current device.
Links:The migration feature is implemented on the basis of "hooking". If YASAPI encounters a AUDCLNT_E_DEVICE_INVALIDATED error the interfaces to the current device IAudioClient, IAudioRenderClient, and IAudioClock, respectively, are blocked until the device is migrated. Migrating the device is initiated by an IMMNotificationClient registered with the IMMDeviceEnumerator.

The new version should make it easier for you to look at the trace when un-plugging the device and observe incoming events. From that observation you should be able to state which event should initiate the migration. It should also be clear that it is impossible to migrate to a null device.

Winamp v5.666 Build 3516 (x86) + in_ffsox + out_yasapi + gen_yas
pbelkner is offline   Reply With Quote