Reply to thread

Message

<blockquote data-quote="michael_t" data-source="post: 1032710" data-attributes="member: 85139">So I think it is something different: PS handles the problem that after the end of away mode or wakeup from standby Windows (or better some audio drivers?) does not always unmute the default audio device. Moreover on some HDMI connected sound devices it takes some seconds until they are &quot;seen&quot; by Windows again after wakeup and therefore they keep unmuted too. The PS client plugin checks the deafault audio device if it is still the same as before entering away mode or sleep mode (waits some seconds for the device to &quot;reappear&quot; if needed) and then unmutes the default audio device if it was not muted before entering away mode or sleep mode.But ofc this is no function that should be done by PowerScheduler any longer but it should become part of the MP client core (which would also need to modify the MP core's power event functions to recognize entering and leaving away mode).Michael</blockquote>

[QUOTE="michael_t, post: 1032710, member: 85139"] So I think it is something different: PS handles the problem that after the end of away mode or wakeup from standby Windows (or better some audio drivers?) does not always unmute the default audio device. Moreover on some HDMI connected sound devices it takes some seconds until they are "seen" by Windows again after wakeup and therefore they keep unmuted too. The PS client plugin checks the deafault audio device if it is still the same as before entering away mode or sleep mode (waits some seconds for the device to "reappear" if needed) and then unmutes the default audio device if it was not muted before entering away mode or sleep mode. But ofc this is no function that should be done by PowerScheduler any longer but it should become part of the MP client core (which would also need to modify the MP core's power event functions to recognize entering and leaving away mode). Michael [/QUOTE]

Verification