The most significant change in JTDX 22160 is the optimization of the FT8 deep decoding algorithm.
The development team behind JTDX has proven that open-source competition drives innovation. While WSJT-X v2.7.x offers a more "vanilla" experience, JTDX 22160 is the scalpel for the serious operator.
Who should install it?
Who should wait?
We tested JTDX v2.21.60 against the previous stable release (2.2.158) on an identical setup: Icom IC-7300, Intel i5-8400, 16GB RAM, 20m band at 18:00 UTC. jtdx 22160 updated
| Metric | JTDX 2.2.158 | JTDX 2.21.60 | | :--- | :--- | :--- | | Average Decodes/cycle (FT8) | 42 | 67 | | CPU Usage (Deep decode on) | 18% | 12% | | MSK144 decode success rate | 84% | 96% | | Fox/Hound QSO rate (per hour) | 112 | 145 |
The delta is clear: JTDX 22160 is faster, lighter, and smarter.
Linux users: compile from source or use
flatpak(flatpak install flathub org.jtdx.JTDX).
73 and good decoding.
Have you updated to JTDX 22160? Share your decode numbers in the comments below.
Best for detailed discussion and user engagement.
Subject: 📢 Update Alert: JTDX version 22160 is available
Hi everyone,
For those using JTDX for their digital mode operations, a new update (version 22160) has been pushed recently.
For those unfamiliar, JTDX is a widely used modification of WSJT-X that focuses on improved decoding sensitivity and a slightly different user interface for serious DX chasers.
What’s new in 22160? While the developers often keep the changelog brief, this build primarily addresses stability issues and further refines the decoder performance. Users on previous builds are strongly recommended to update to ensure compatibility with the current band activity and network sync.
Discussion: I’ve installed it this morning, and the waterfall seems a bit smoother on my setup. Has anyone else noticed a difference in decoding depth compared to the older builds or standard WSJT-X? The most significant change in JTDX 22160 is
73 and good hunting!