Hi Steve,
I have no explanation of the peculiar behavior you've reported. Is it
related to your unusual remote-operation setup? Hard to say. Nobody
else has reported such behavior.
One thing is for sure: you should not be using WSJT-X v1.8.0-rc2.
Temporary beta-release caldidates are sometimes made in advance of a new
general-availability release, in order to obtain user feedback. These
versions are labeled -rc1, -rc2, etc. Release candidates should not be
used on the air after a full release with the same version number has
been made.
-- 73, Joe, K1JT
On 2/4/2018 11:11 AM, st...@k5dog.com wrote:
Joe, & wsjt-x developement team.
Here is another wav file that caused the program to change from JT65B to
JT9 transmit.
This is from a different, but similarly constructed Windows 10 PC,
AMD FX(tm)-6300 Six-Core Processor 3.5 GHz
Ram 8.00 GB (7.73 GB usable)
64-bit Operating System, x64-based processor
and it is using:
WSJT-X v1.8.0-rc2 r8069 (different from the last wav files I sent you)
This error was produced along with a result in the "Single-Period
Decodes" window of:
1545 -30 5.9 1205
These odd decodes are always associated with a significant bird-ie in
the waterfall.
Playing back the file does not reproduce the error.
I am not a programmer, but to me, this looks like:
The JT65 decoder reaches an unexpected result which has not been
provided for, and so the program falls through to another section of the
program which changes the transmit mode to JT9.
Just my $0.02 worth.
Steve, k5dog
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
