Sunday, January 16, 2022, 1:01:32 PM, you wrote:
> But in this case the audio interface is used to transfer signals to/from the
> rig, so why should it ever become 'unavailable' during operation ?
as an example, you start WSJT-X and your screen with an built-in audio is
already 'active. Windows 'enumerates' the audio channels. The screen is audio
channel number '1' since power on, WSJT-X will be using audio channel '2'.
Now your screen goes to sleep mode - audio channel number '1' is gone. In fact,
there is now only one audio channel, but WSJT-X software, still in the settings
after startup, want to use audio channel '2'. So the pointer for channel '2'
(in the settings of WSJT-X) can not find any hardware = your rig is unavailable.
73 de Wolfgang
OE1MWW
----------
under construction: https://www.oe1mww.work/
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
