I answered on the WSJT group as well... This has been a problem in JTAlert for the MSK144 mode for as long as I can remember.

I stay logged in, but it's responding slowly at the refresh intervals. -- John P. WA2FZW

Without going back to look at the release notes, seems to me I recall there were changes to the FT8 decoding process; not sure about other modes.

Well, I'm gonna chalk this one up to the usual Windows goofy behaviors! I set things up to actually do a screen capture of what is (was) happening and it isn't happening today; I rebooted the computer

I will get more accurate times tomorrow when there is enough activity to cause the problem. The decode period is possibly extending into the next cycle, but only by a second or two; nowhere near the 8

Referring back to my original post, what is happening is that with 2 pass decoding and AP enabled in WSJT, at the end of a period, The Callsigns window gets populated with a bunch of stations, then al

2nd round of decodes is almost instantenous. Machine: Intel i3-4300 CPU @ 3.4GHz 8GB Ram Windows 10 Pro Highest CPU seen during decode time ~40% WSJX-X Version 2.6.0 JTAlert Version 2.60.5

Hi Laurie! When I have 2 pass decoding and Enable AP turned on, the Callsigns window sometimes gets erased between decoding passes. Stations disappear before I have a chance to see them.

On Sat, Dec 17, 2022 at 02:49 PM, JTAlert Support (VK3AMA) wrote: Send the zipped HamApps folder to me direct, not via this group. Email sent!

I'm running 2 instances of WSJT-X version 2.5.4 and 2 instances of JTAlert version 2.60.3 on 2 different radios (FT-891 and IC-9700). The FT-891 instance is instance #1 and is using Commander between

Thanks Laurie & Joe! I figured it had something to do with the UDP stuff which makes my head hurt every time I try to figure it out! For the record, MSHV seems to becoming more popular for folks using

I started playing with MSHV this morning for MSK144. I installed the MSHV version of JTAlert and have everything configured to work with the DxLab Commander and DxKeeper software for my FT-891 on 6 me

Seems like same problem here! EDIT: Never mind! - Missed the note about the .NET 6 Desktop Runtime update. Working now!

Problem solved! - Found the right checkbox under "Applications - WSJT-X / JTDX"!

Both the "Clear when Wsjtx decodes cleared" and the "Clear when band changes" boxes are un-checked in the automation options. None of the calls in the callsign window are showing a pin (not sure how t

Even though I do not have the "Clear when Wsjtx decodes cleared" box checked in the settings, the window does clear when I "Erase" the calls in the WSJT-X window. It also clears after I log a QSO.

Laurie I posted the same problem in another thread this afternoon (Fatal error on WSJT false decode). I can be a bit more specific about what happened I think. I was listening on 2 meter EME in JT65B

I got the error shown in the attachment twice this afternoon while listening on 2 meter JT65B with WSJT-X. It coincided with a false decode "WA2FZW KK4MA <grid>"

Thanks Laurie! - That did the trick!

After my 'C' drive crashed, my computer guy replaced it with an SSD and upgraded the Windows-7 machine to Windows-10. I re-installed all the latest versions of everything. I run 2 instances of WSJT-X;