Hi Chris,
On 5/2/2019 12:52 PM, Topher Petty AI8W wrote:
... I don't believe it's available processor power, or RAM availability.
With only WSJT-X, TQSL, and Chrome (six tabs open) running, the T410 has
more than enough processor (24 threads) to handle these decodes, yet
they're not being decoded.
I'm not judging, here. I'm only bringing information to the discussion.
Long before FT8 was released for general use, we analyzed many thousands
of received FT8 waveforms under a wide variety of conditions. Soon
after FT8 was released, and again after it was upgraded to use 77-bit
message payloads, hundreds of thousands of additional FT8 waveforms were
analyzed. The FT8 decoder in WSJT-X (and also those in derivative
programs like JTDX) could not exist without that extensive work.
Without the relevant .wav file -- and better still, an indication of the
most likely message content for the signal in question -- reports that
say something like "the signal was strong but it didn't decode" can't be
very useful.
Tx messages changed in mid-stream are among the most likely causes of
failed decodes. If 40% of a transmission contains one message and 60%
contains a different message, decoding is necessarily doomed to failure.
-- 73, Joe, K1JT
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
