On 12/11/2021 17:14, Chris Elmquist wrote:
On Tuesday (07/27/2021 at 09:53AM +0100), Bill Somerville via wsjt-devel wrote:
On 27/07/2021 06:51, Bjorn via wsjt-devel wrote:
Hello
Maybe this is a known issue. But anyway: I have 10 VAC channels going
here and I use 1 and 2 towards the WSJT-X software.
When I start the WSJT-X I get RX on ch1 and TX on Ch2. But after it has
been running for sometime, say RXing for a day. And I then hit TX it
uses Ch6 for some reason.
Restart WSJT-X fixes it.
I have used 2.4.0 and 2.5.3 RC3, same thing.
73 de SM7SJR
Hi Bjorn,
WSJT-X saves audio device names in its settings file but to access the
devices we look them up and get an index number which we must use to
interact with them. These index numbers are somewhat volatile and can change
while WSJT-X is running if other audio devices on the system appear or
disappear. It is too costly to look up the audio device index every time we
need to start a transmission, e.g. on some platforms it takes several
seconds to complete enumeration of the audio devices, so we are vulnerable
to the devices that the index numbers reference changing without our
knowledge.
We recommend that while using WSJT-X all system power options, that might
disable a device carrying audio are disabled. This should include all USB
hubs, and HDMI monitors.
I apologize for resurrecting an old thread but I came back to the list
because I continue to have a problem in this very same space.
I am running Windows 10 with WSJT-X 2.5.1 and an IC-7610 connected to
the computer with a USB cable. There is no seperate sound card as it
uses the audio interface in the radio.
What I experience is that any time the screen blanks, WSJT-X looses track
of the audio interface over which it should send the transmit audio.
It will key the radio using a CI-V command but the transmit audio
comes out the computer speakers and doesn't go into the transmitter.
WSJT-X settings still think the audio device is the IC-7610 radio.
I have absolutely disabled ALL USB power saving and indeed ALL computer
power saving and as long as I do not let the screen blank, I do not have
the problem.
However, if I manually blank the screen (with a command line tool) or I
allow the Windows screen blanker to run, then WSJT-X will loose track
of the transmit audio device every single time the screen blanks.
The only way I can let WSJT-X (in WSPR mode for example) run for any extended
period of time is to make sure that the screen blanker never goes off.
I offer that Windows is shuffling these audio device index numbers more often
than we like and if we were to revisit a method for enumerating the audio
devices either before every transmit or if we received a notification of a
screen blank event (don't you get that so that you can repaint the app's
display?) we could likely solve this problem.
Thank you and 73, Chris
-- Chris Elmquist NØJCF
Hi Chris,
I assume you are using an HDMI connected monitor. If so it is the audio
connection associated with that which is causing the issue. Can you
disable the HDMI audio devices in Device Manager, if you can the issue
should be avoided.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
