Jtdx 2.2.160 ((link)) Today

Managing "Hound" mode during DXpeditions or running standard split configurations is more reliable. The software handles automated frequency shifts seamlessly, preventing accidental transmissions on the DX station's transmit frequency. 4. Alert and Notification Enhancements

You can also run multiple cycles per period (e.g., at 5, 10, and 15 seconds into an FT8 timeslot). jtdx 2.2.160

: Earlier release candidates saw issues with certain settings like "Fake It" and "Split Operation" disappearing when using non-English languages. These have been addressed to ensure a consistent user experience across different locales Performance: JTDX vs. WSJT-X Managing "Hound" mode during DXpeditions or running standard

If the decode button turns blue and decoding stops, first try restarting JTDX. If the issue persists, close the program, delete the JTDX.ini configuration file, and restart the application to recreate it with default settings. Alert and Notification Enhancements You can also run

Check the SHA-256 hash: JTDX-2.2.160-win64.exe → a3f5d2c9e8b1a4f6d0c8b8a3f7e2d4c5b6a1f0e9d8c7b6a5f4e3d2c1b0a9f8e7

Auto-sequencing and calling logic are heavily optimized for working DXpeditions and rare grids.

| Metric | WSJT-X 2.6.1 | JTDX 2.2.160 | Improvement | | :--- | :--- | :--- | :--- | | Total FT8 decodes (5 min) | 142 | 187 | +31.7% | | Decodes below -24 dB SNR | 11 | 34 | +209% | | False decodes (errors) | 1 | 2 | Acceptable | | CPU usage (i5-8400) | 8% | 12% | Slight increase | | Waterfall latency | 0.5 sec | 0.3 sec | Smoother |