What I am noticing in 2.2.2 is a consistent pattern when responding to a good signal call and then not seeing further decoded response from that station (despite seeing the waterfall response) until I either ;
1. Halt TX and then will see the sequenced response decode, or 2, Click back to my TX red bracket to bring the green bracket back there instead of the target station and always then on the next over I see the target decode. Something is weird that I have to play with the program as above to get results, however sometimes it works as expected. Adrian Fewster -----Original Message----- From: Jim Brown [mailto:k...@audiosystemsgroup.com] Sent: Saturday, 4 July 2020 2:15 PM To: WSJT software development Subject: [wsjt-devel] 2.2.2 Decoding Performance Several members of the Slack VHF group have commented that JTDX is decoding more signals than 2.2.2. Seeing that, I've started running both programs in parallel. Since I use VOX, that's easy to do. What I'm seeing is similar to my experience simultaneously running MMTTY and 2TONE for RTTY contesting -- either program will catch a decode that the other misses. The trend I'm seeing with WSJT-X and JTDX 1.51 is that WSJT-X 2.2.2 misses more decodes than JTDX 1.51. K5TM reverted to 2.1.2 and observed that the decodes are no longer missing. His second program is MSHV, because JTDX doesn't do MSK144. 73, Jim K9YC _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
