All,
Using WSJT-X 3.0.0.-rc1 on Windows 10, version 22H2, I was monitoring 3573 kHz FT8 this morning and got the following sequence of decodes in the Rx Frequency window: 104100 -19 0.4 1701 ~ CQ VE3TCS EN82 104130 -11 0.4 1701 ~ CQ VE3TCS EN82 104200 -18 0.4 1700 ~ *** bad message *** a7 104430 -11 0.4 1700 ~ CQ VE3TCS EN82 104500 -20 0.3 1709 ~ CQ VE3TCS EN82 104530 -20 0.4 1709 ~ CQ VE3TCS EN82 104600 -11 0.4 1709 ~ CQ VE3TCS EN82 Interestingly, there was no corresponding "*** bad message ***" decode in the Band Activity window at 104200 (or, indeed, any other decode at or near 1700 Hz df). A priori decoding was, of course, turned on. I was unable to reproduce this event. I've never seen a "*** bad message ***" decode in any WSJT-X version before, so I thought I would report it just for the record, in case this meant more to someone else. If this is considered a feature and not a bug, I would suggest making a note of possible "*** bad message ***" decodes somewhere in the version documentation, including mention that they will (may?) not be seen in the Band Activity window. 73, Ed N4II.
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
