73 and happy weak-signal hunting.
Fix: In Settings > Radio , change Serial Baud Rate to 115200 and set RTS to "High" and DTR to "High". Then uncheck "Force Control Lines".
Whether you are a casual weekend operator or a hardcore 160m DXer, delivers tangible benefits. The combination of better weak-signal decodes, faster multi-threaded performance, and ADIF 3.1.4 compliance makes it the most polished JTDX release in two years. jtdx 22160 new
| Feature | WSJT-X 2.6.1 | JTDX 2.2.160 New | | :--- | :--- | :--- | | Decoding Sensitivity | Baseline | ~1.5 dB better for FT8 deep search | | Contesting add-ons | Basic | Advanced (DX Cluster integration, custom alerts) | | CPU efficiency | Good | Excellent (multicore experimental) | | User interface | Classic, minimal | More detailed, customizable | | Stability | Rock solid | Very high (minor Qt rendering bugs remain) | | Recommended for | Beginners, contest rule-strict ops | DXers, weak-signal enthusiasts, contesters |
Fix: Disable "Smooth Waterfall" in View > Waterfall > Smoothing . This is a known Qt5 rendering bug. 73 and happy weak-signal hunting
The only caveats are the minor waterfall glitch on some Windows configurations and the experimental nature of multicore decoding. However, the developers have been responsive—a bug report thread on Groups.io shows three patches released within 10 days of launch.
Fix: In Advanced > Multi-threading , reduce the number of threads to 4 (even if you have 8+ cores). The 2.2.160 experimental scheduler can overload USB audio buffers. How "JTDX 22160 New" Compares to WSJT-X 2.6.1 Many hams ask: Should I switch? Here’s a direct comparison. Whether you are a casual weekend operator or
| Metric | JTDX 2.2.159 | JTDX 2.2.160 ("New") | Improvement | | :--- | :--- | :--- | :--- | | Minimum decode S/N (FT8) | -23.1 dB | -24.2 dB | +1.1 dB | | CPU usage (single decode) | 12% | 9% (with multicore off) | 25% reduction | | Waterfall refresh lag | ~200 ms | ~120 ms | 40% faster | | False decode rate (noise) | 0.8% | 0.3% | 62% fewer ghosts |