I have installed version 2.2.2 and the latest version update of Win10. I notice 
that with many cycles I get no decodes even though there are many good signals. 
Sometimes there are up to 3 decodes per cycle and then none. On occasion the 
decoding stops completely and I have to hit the decode key to start it again or 
reboot the program. Many times I have to send a reply 3 or 4 times after 
someone replies to my CQ before the QSO continues. Perhaps these problems are 
related. I have never had this decoding problem before. It happens also with 
very few signals observed on the band not just when it is crowded.
Ron Schmahl K2PSD


> On June 28, 2020 at 6:12 PM Bill Somerville <g4...@classdesign.com> wrote:
> 
> 
> On 28/06/2020 19:12, David Kjellquist wrote:
> > Myself and a friend both tried operating today using fast decode (not 
> > normal or deep).  We both had crashes with other decode settings.
> >
> > Both experienced no crashes or other problems. We both use WSJT-X 
> > 2.2.2, Windows 10 (up to date), JTalert 2.16.8, N3FJP 6.03 and Flex 6600.
> >
> > Hope this helps.
> >
> > -- 
> > Dave, WB5NHL
> 
> Hi Dave,
> 
> thanks for that report. Apologies to you and others that we could not 
> identify the problem earlier. It looked like the bands were plenty busy 
> enough for working in fast decode mode without AP decodes and missing a 
> few decodes every period was not too much of a hardship.
> 
> 73
> Bill
> G4WJS.
> 
> 
> 
> _______________________________________________
> 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

Reply via email to