Repository navigation
JTDX-VU v0.7.3
JTDX-VU for VUCG v0.7.3. A check for new releases, auto logging from a JTTY macro, and two fixes to the Auto CQ button. Everything else is as in v0.7.2.
What's new in v0.7.3
- Tells you when a new release is out. Once a day JTDX-VU asks GitHub for the latest JTDX-VU release: about 10 s after start, or later while it stays open, whenever a day has passed since the last check that got an answer.
- If the release is newer than yours, a window shows its release notes with Download (opens the release page in your browser), Skip This Version and Remind Me Later. Otherwise it says nothing.
- If GitHub can't be reached it says nothing, and tries again an hour later and at the next start. Nothing is downloaded or installed.
- Help > Check for Updates... checks at any time and always says what it found.
- Turn the daily check off with the tick Settings > General > "Check for updates automatically".
- The only request is one anonymous
GETtoapi.github.com(/repos/vu2cpl/jtdx-vu/releases/latest); no other server is involved. - v0.7.3 is the first version with the check, so you will be told about the releases after it.
- Auto logging from a JTTY macro. Put
%LOGin a macro (e.g. "TU %H 73 %LOG") and sending it also logs the QSO, straight in without the Log QSO dialog, the same way as Settings' auto log (log file, UDP "QSO Logged" / ADIF to your logging program).%LOGitself is not sent, and a macro of just%LOGonly logs. A QSO is logged once: pressing it again, or the "TU ..." message that normally opens the dialog, leaves an already-logged QSO alone until the DX call changes. The Log QSO button still opens the dialog. - The Auto CQ button keeps its width. The countdown is now on a second line under "Auto CQ" ("4:37", or "12m" from 10 minutes up); in v0.7.2 "Auto CQ 0:58" widened the button and the right-hand column.
- The FT8 / FT4 / FT2 countdown runs all minute. With Auto CQ (Call Non-Stop) on, v0.7.2 showed whole minutes in the first half of each minute (5:00 at the start) and only counted down in the second half. It now counts down throughout. The watchdog itself was always right; only the display lagged. As in stock JTDX, any click, key press or window activation in JTDX-VU resets the watchdog, so the count goes back to the full time then.
- The README's title line and title-bar example still said v0.6.0; they now follow the release.
AetherSDR users
AetherSDR 26.9.5 stopped sending TCI audio after a TCI client reconnected (aethersdr/AetherSDR#6006). That is fixed in AetherSDR 26.10.1: update AetherSDR if JTDX-VU says "no audio from the SDR program". The FlexRadio VITA-49 rig type avoids TCI altogether.
Downloads
| Platform | File | Runs on |
|---|---|---|
| macOS, Apple Silicon | JTDX-VU-0.7.3-macos-arm64.zip |
macOS 14 Sonoma or later |
| macOS, Intel | JTDX-VU-0.7.3-macos-x86_64.zip |
macOS 15 Sequoia or later |
| Windows x64 | JTDX-VU-0.7.3-windows-x64.zip |
Windows 10 / 11, 64-bit |
| Raspberry Pi / Linux arm64 | jtdx-vu-0.7.3-linux-arm64.deb |
Raspberry Pi OS / Debian 12 (bookworm), 64-bit |
Each file has a matching .sha256 checksum. JTDX-VU installs alongside a
stock JTDX on macOS and Windows; on the Pi the package replaces a stock
jtdx package.
How to install
macOS (Apple Silicon or Intel)
- Download the zip for your Mac (Apple menu > About This Mac: "Apple
M…" chip = arm64, "Intel" = x86_64) and double-click it to unzip. - Drag JTDX-VU into Applications.
- First launch. The app is ad-hoc signed, not notarized, so macOS
blocks the first open:- macOS 15 Sequoia and later: double-click JTDX-VU, click Done on
the warning, then open System Settings > Privacy & Security,
scroll down and click Open Anyway next to "JTDX-VU was
blocked", and confirm. - macOS 14 Sonoma: right-click (Control-click) JTDX-VU > Open >
Open. - Or, in Terminal:
xattr -dr com.apple.quarantine /Applications/JTDX-VU.app
- macOS 15 Sequoia and later: double-click JTDX-VU, click Done on
- Allow the microphone when asked; that is how macOS names access to
your radio's sound card. If you clicked Don't Allow, turn JTDX-VU on in
System Settings > Privacy & Security > Microphone. - Shared memory (one-time, every Mac). The decoder needs more SysV
shared memory than the macOS default; without it JTDX-VU stops with
"Unable to create shared memory segment". In Terminal:That lasts until the next restart. To make it permanent, downloadsudo sysctl -w kern.sysv.shmall=32768 kern.sysv.shmmax=33554432
Darwin/com.jtdx.sysctl.plistfrom
this repo and run
sudo cp com.jtdx.sysctl.plist /Library/LaunchDaemons/.
It may need redoing after a macOS upgrade. - Set up your callsign, radio and audio in JTDX-VU > Settings…
(Cmd+,).
Upgrading: quit JTDX-VU, replace the app in Applications with the
new one, and repeat step 3 if macOS asks. Settings
(~/Library/Preferences/JTDX-VU.ini) and data
(~/Library/Application Support/JTDX-VU) are kept.
Windows 10 / 11 (64-bit)
- Download
JTDX-VU-0.7.3-windows-x64.zip. Before unzipping,
right-click the zip > Properties, tick Unblock, OK; this saves
a warning for every file inside. - Right-click > Extract All… to a folder of your choice, for example
C:\JTDX-VU. No installer and no administrator rights are needed. - Run
bin\jtdx.exein that folder. If Windows SmartScreen says
"Windows protected your PC", click More info > Run anyway (the
program is not code-signed). Right-clickjtdx.exe> Send to >
Desktop (create shortcut) for a desktop icon. - If Windows Firewall asks, allow access on private networks (JTDX-VU
talks UDP to logging programs such as Log4OM, N1MM or JTAlert). - For rig control through OmniRig, install
OmniRig separately. Hamlib, TCI
and the other rig interfaces are built in.
Upgrading: quit JTDX-VU and extract the new zip over the old folder
(or into a new one). Settings are stored in your Windows profile, not
in the program folder, so they are kept.
Raspberry Pi / Debian 12 (arm64)
Needs a 64-bit Raspberry Pi OS (Bookworm) or Debian 12 on arm64 - a Pi 4
or Pi 5 is recommended.
- Download
jtdx-vu-0.7.3-linux-arm64.deb, then in a terminal in the
download folder:Keep thesudo apt update sudo apt install ./jtdx-vu-0.7.3-linux-arm64.deb
./- it tells apt to install the file rather than look for
a package by that name. apt pulls in Qt, Hamlib and FFTW. A stock
jtdxpackage can't be installed alongside; apt offers to remove it. - For CAT control over a USB serial cable, give your user access to
serial ports once, then log out and back in:sudo usermod -aG dialout $USER - Start JTDX-VU from the menu (Sound & Video / Ham Radio), or run
jtdxin a terminal.
Upgrading: install the new .deb the same way; settings are kept.
Removing: sudo apt remove jtdx-vu.
Credits
Based on JTDX by Igor Chernikov UA3DJY, Arvo Järve ES1JA and the HF community. JTDX is itself derived from WSJT-X by Joe Taylor K1JT, Bill Somerville G4WJS, Steve Franke K9AN, Nico Palermo IV3NWV and others.
JTTY is by Joe Taylor K1JT, Steve Franke K9AN, Rob Sherwood G4KLA and the WSJT-X development group (WSJT-X 3.2.0-rc1, GPL v3). FT2 was created by Martino Merola IU8LMC (ARI Caserta), with Salvatore Raccampo 9H1SR as lead C++ developer; it first went on air in Decodium on 2026-02-16 (ft2.it), and MSHV by Hrisimir Hristov LZ2HV added it in 2.76.5 on 2026-03-24. JTDX-VU uses no Decodium code: its FT2 is JTDX's own FT4 chain, with MSHV's implementation as the reference. The band/mode buttons, the "show only new" filter and the DXCC colour scheme follow MSHV by LZ2HV. The QO-100 logging follows MSHV. The FlexRadio VITA-49 backend and panel are ported from the MSHV-Mac port's native Flex backend.