Locked WSJT-x 2.6.1 #decode


Fred Roberts
 

Folks....I am running Windows 10, 8 G of RAM, Intel core i3-7100 CPU at 2.4 GHz, 64 bit OS. I'm also running JTalert 2.60.5 and DXkeeper 17.0.0....800+ Gig left on the hard drive.
I installed 2.6.1 last night - I had been running 2.5.4. immediately I noticed that new decodes were still scrolling on WSJT-x long after the next time slot started. (I was just monitoring at the time.) In addition, there were many decodes that had "a7" displayed to the right of the decoded messages. I tried cold booting the computer...no help. I re-installed 2.5.4 and have had no problems since. Fred, WB4QOC


Jamie WW3S
 

Its a new “feature”…..you might also notice some decodes before the decode indicator turns on….you might see some other a indicators, its some sort of predictive algorithm, I dont understand it completely, but based on the sequence, and what should be received, and partial decodes, etc, it “predicts” the rest….I think its selectable, I’m not in front of the software right now, but look for API, and uncheck it…..

On Feb 14, 2023, at 12:26 PM, Fred Roberts <fred5352@...> wrote:

Folks....I am running Windows 10, 8 G of RAM, Intel core i3-7100 CPU at 2.4 GHz, 64 bit OS. I'm also running JTalert 2.60.5 and DXkeeper 17.0.0....800+ Gig left on the hard drive.
I installed 2.6.1 last night - I had been running 2.5.4. immediately I noticed that new decodes were still scrolling on WSJT-x long after the next time slot started. (I was just monitoring at the time.) In addition, there were many decodes that had "a7" displayed to the right of the decoded messages. I tried cold booting the computer...no help. I re-installed 2.5.4 and have had no problems since. Fred, WB4QOC





Reino Talarmo
 

Hi Fred,
Most probably disabling AP would "solve" your problem. But you may get less decodes. Fast or Normal should do.
73, Reino OH3mA