Too many mistakes, this morning. At the bottom of my email announcing availability of Candidate Release WSJT-X 2.7.0-rc1, I listed my colleague Uwe Risse's callsign as DG3YCB. As most of you know, and

#general

Dear WSJT-X Users, We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc1 is ready for download by beta testers. WSJT-X 2.7.0 Release Candidate 1 introduces a new program called "QMAP", a

#general

From the User Guide: "To start a measurement session, check the Measure option ..." The Measure checkbox is just above and right of the Date/Time display. -- 73, Joe, K!JT

#FreqCal

Hi Andy, The most common user mistake in using Echo mode seems to be forgetting to select "Own Echo" for Doppler Tracking. But there are other possible routes to failure, too. From the info you provid

#Echo

Hi Don, I don't know exactly what you mean by "Scanning ADIF file from "Colors" drop down, colors do not change," or by "The LOG Dir. that contains my wsjt-x.txt file is highlighted but does not open.

#logging #Dell #windows11

Something is wrong at SourceForge. I suggest going to https://sourceforge.net/projects/wsjt/files/wsjtx-2.6.1/ and selecting the file you need. -- Joe, K1JT

#install

Hi John, A program enhancement is not needed: you can make all instances of WSJT-X use the same CALL3.TXT file. Merge all your callsign information into CALL3.TXT in your base Log directory. For me, t

#EnhancementReqest

Hi Hugo and all, I'd like to suggest that you've focused on the wrong metric. We could make the FT8 decoder significantly faster than the one in WSJT-X 2.6, but the result would be significantly fewer

#IssueReport

Hi Al, Perhaps you need to use the (releatively new) feature on the Settings | Frequencies tab. You can identify a preferred dial frequency there, even if it's only temporary. I recommend one of these

#EnhancementReqest

Look in Section 8.1: https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.6.1.html#VHF_SETUP As a general matter: use the search feature of your browser to find needed information in the WSJT-X User Gui

#EnhancementReqest

Hi Juergen, Standard callsigns are defined in Section 17.1 of the WSJT-X User Guide: https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.6.1.html#PROTOCOL_OVERVIEW "A standard amateur callsign consists

#IssueReport

Why do you think we would be surprised? Of course we understand that people use a wide range of different computer speeds. We test on slower machines, too, but this morning for convenience I did the t

#IssueReport

We always make extensive timing tests after making changes to the decoders. Timing a single Rx sequence doesn't tell you much. Here are some timing results from decoding 10 test files recorded on a mo

#IssueReport

Hi Frode, Of course you are correct. My 82-year-old brain is slowly doing its best to replace all references to the physics.princeton.edu website with references to the SourceForge site, but this glar

#general

The WSJT Development Team is pleased to announce that today the Solar Flux Index is 234 and Sunspot Number is 195. Oh, yes: and the WSJT-X 2.6.1 General Availability (GA) release is now available for

#general

This is NOT correct. DT values even larger than 0.7 s cause no loss of SNR or decoding ability. -- 73, Joe, K!JT

#WSJTX_config #Windows10

Hi Rick, N6XI wrote: Yes. It's active only when the Active Stations window has been activated. -- 73, Joe, K1JT

#decode

Sorry about the missing T/R period control in WSJT-X 2.6.0. This was completely unintentional; the problem had been recognized and corrected, but the corrected code was inadvertently not moved into th

#Q65

Hi Bill, This is embarrassing: you are, of course, correct. This bug was found and corrected on December 28, but unfortunately the correction never made it into the master code branch. This bug will l

#general

Hi Frank, How did that proofreading lapse get past us? Of course you are right, and the posted Release Notes have been corrected. -- 73, Joe, K1JT

#general