[hpsdr] Windows 10/PowerSDR/WSJT-X sound settings

[John Ackermann N8UR]

Not sure if I followed up on this, but I discovered the reason for the
audio failures.

When my monitor went into sleep mode, the audio paths got screwed up.  I
had been very careful to make sure the machine never went into suspend
or sleep mode, but the "turn off monitor after X" setting apparently was
the culprit.

The only reason I can think of that makes sense is that I was using HDMI
audio output for non-PowerSDR audio tasks.  Maybe when the monitor goes
to sleep, that loses the HDMI audio device, and somehow Windows takes
that as a clue to reassign other audio ins and outs?  I dunno...

John
----

On 9/8/19 3:06 PM, Scott Traurig wrote:
> Windows updates are notorious for damaging sound driver related software
> such as Muzy VAC, Voicemeeter, etc. Recommend you uninstall whatever you
> are using for virtual audio connections, reboot, reinstall, reboot,
> reconfigure, and see if that fixes the problem.
> 
> 73,
> 
> Scott/w-u-2-o
> 
> On Sun, Sep 8, 2019 at 2:38 PM John Ackermann N8UR <jra at febo.com
> <mailto:jra at febo.com>> wrote:
> 
> 
>     I am seeing my sound settings mysteriously change or fail when running
>     PowerSDR and WSJT-X through VAC on Windows 10.
> 
>     The symptom is that WSJT-X stops seeing audio input, though the sound
>     settings in both programs select the correct VAC cable, or the WSJT-X TX
>     audio output is routed to the speakers instead of PowerSDR, again where
>     the VAC cables are properly selected.
> 
>     This will happen while the system is stable (well, as stable as Windows
>     ever gets...), i.e., everything is running fine, I leave without
>     changing anything, and come back a couple of hours later to find these
>     problems.
> 
>     Usually I have to restart WSJT-X and sometimes both programs, then
>     things start working again.
> 
>     Any ideas about what might be causing this, or a cure?
> 
>     Thanks,
>     John
>