Laurie, thank you so much for your never ending improvements with. JT Alert!!!
toggle quoted messageShow quoted text
On Feb 11, 2021, at 2:30 PM, Joe Subich, W4TV <firstname.lastname@example.org> wrote:
And FST4W?FST4W *IS NOT A QSO MODE* it is a VLF replacement for WSPR (which
is also not supported by JTALERT for very good reason) a beacon
protocol and colossal waste of bandwidth.
... Joe, W4TV
On 2021-02-11 4:32 PM, Michael Black via groups.io wrote:
On Thursday, February 11, 2021, 03:29:08 PM CST, HamApps Support (VK3AMA) <email@example.com> wrote:
On 11/02/2021 2:08 pm, William Thomas wrote:
When using the new Q65 mode, I only see my call letters displayed in JTAlert, not the station I’m working. Another operator told me they are seeing the same thing.
73 Bill WT0DX
At the time of the current 2.16.17 JTAlert release (December 6 2020) my "Crystal Ball" was in the shop for repair so I was unable to foresee the availability of the new Q65 mode with the release of WSJT-X 2.4.0-rc1 which occurred on February 3 2021, just shy of 2 months after the current JTAlert release.
The first I became aware of Q65 was in the release announcement of 2.4.0-rc from the post by K1JT. See https://sourceforge.net/p/wsjt/mailman/wsjt-devel/thread/4e54822e-3f67-c564-dd32-0ff13d486715%40princeton.edu/#msg37211965
The next release of JTAlert recognizes Q65 decodes.
de Laurie VK3AMA