Show only needed decodes. A New only tick above the decodes (since v0.6.0; a four-way "Show:" dropdown before) hides everything that doesn't get a "new" colour from Settings > Notifications - so what counts as new (DXCC, on this band, in this mode, zones, grid, prefix, call) is chosen once, there. It uses Club Log when enabled, turns amber while active, and is live: ticking it re-filters every decode already on screen, and a just-worked station drops out. Traffic with your call, your QSO partner and a Wanted Call (worked before or not, so its beep still sounds) always show, and the Rx Frequency pane is never filtered.

Notifications page redesigned (since v0.6.0): one row per kind of "new" in priority order, each with its band / mode checks, colour squares and beep on one line, plus "Already worked", "Messages and markers" and a live preview. Background highlight (since v0.6.0) off keeps the decode pane's background plain and puts the highlight colour on the text; since the next build that also covers your own Tx lines, QSY lines and the marker cell before the country (red for your call, blue for your QSO partner, the "new" colour on other stations' messages).

AutoSeq goes for what your log needs first (since v0.6.0). Always on, no switch: when picking a CQ to answer, and when choosing between stations calling your CQ, AutoSeq takes a new DXCC first, then a DXCC new on this band, then one new in this mode (the same tests as the Show selector, from Club Log when enabled), and only then the usual JTDX order. A wanted station is picked even when AnsB4 / CallB4 are off; with none heard, nothing changes.

Queue a station for AutoSeq (since v0.6.0). Right-click a decode in either pane > Queue CALL. AutoSeq calls it the next time it is decoded (its CQ, or the end of its QSO), ahead of wanted stations and callers, in queue order, and takes it off the queue once logged. The queue shows above the Rx Frequency pane while it has calls; right-click there (or the decode again) to remove one, or clear it. A queued QSO counts as your own run, so CNS carries on afterwards. FT modes only. Since v0.7.5 a queued pick also switches Enable Tx on if it was off (and moves your Tx period to the opposite one from where the station was heard), so the queue works while you are only listening. It still picks only between QSOs, with the DX Call box empty. Right-click Halt Tx > Halt and queue CALL (since v0.7.5) does it in one go for a busy station: Tx stops, the DX call is cleared and the station is queued, so AutoSeq calls it again when it sends CQ or RR73/73 to someone else (the latter needs Settings > Notifications "RR73/73" ticked).

160m crossband with India (since the next release): Misc > Crossband 160m operation with India, beside stock JTDX's Japan and Korea options. On FT8, a station outside India on dial 1.808 transmits on 1.840, and an Indian station (VU, VU4, VU7) on dial 1.840 transmits on 1.808, audio offset on top. Needs Split operation (Rig or Fake It). 1.808 FT8 is in the default frequency list; an existing profile needs it added in Settings > Frequencies, or type 1.808 in the band box.

Double-click keeps calling a busy station (since the next release). A station you double-click is called whether or not he is still in a QSO, as in WSJT-X and MSHV. JTDX used to halt Tx as soon as he answered someone else (Settings > Sequencing "Halt TX if operator I called answered to other operator", or with your Tx within his guard band), so nothing called him when he finished; that halt now applies only to stations AutoSeq picked. If you don't want to keep calling, the right-click extras wait for you: right-click his decode > Queue CALL, or right-click Halt Tx > Halt and queue CALL when already calling (asked for by KK4CDK).

Ignore a station (since the next release). Right-click a decode > Ignore CALL (never answer): AutoSeq never answers or calls it, for a caller who keeps calling after the QSO is logged. Ignoring the station being worked halts Tx and clears the DX call. The list shows under the queue, is kept per profile, and right-click there (or the decode again) removes a call. Stock JTDX's hidden version (Ctrl/Cmd + right-click Clear DX) still works but lasts only until restart and shows nowhere.

No repeat logging (since the next release). A caller who missed your RR73 keeps sending R+report, and each RR73 sent back used to log the QSO again. Automatic logging now skips the same call, band and mode within 10 minutes; the Log QSO button still logs.

LoTW user marks work again (since the next release, after JTDX 2.2.160). JTDX puts • before the country of a station that uploads to Logbook of the World (° when the decode was also hinted, which alone is *). The list bundled with JTDX 2.2.159 ends in February 2022, and only uploads in the last 365 days count, so no station got the mark. JTDX-VU bundles the October 2026 list, and Settings > General > Logbook of the World User Validation (as in JTDX 2.2.160) has the list's URL with Fetch Now, which downloads the latest list from ARRL (about 6 MB) and uses it straight away, no restart; Age of last upload less than (365 days by default) and the date of the newest upload in the list ("lotw CSV Version"). The fetched file is lotw-user-activity.csv in the data directory. It is not fetched automatically: press Fetch Now now and then.

AutoSeq calls only stations decoded right now (since v0.6.0). JTDX could go back to a station that called your CQ up to 5 minutes ago and isn't heard any more; now every AutoSeq pick must be in the latest decode period.

UDP errors on the status bar (since v0.6.0). A wrong or unreachable UDP server (Settings > Reporting) used to pop up a "Network Error" box on every send; now the status bar says "UDP host:port: ... - check Settings > Reporting", and a failed name lookup is retried every 30 s.

70cm and 23cm band buttons (since v0.7.0, asked for by Frank PH2M for the European UHF/SHF FT8/FT4 activity). Tick them in View > Band & Mode Buttons... as for 4m and 2m. A 23cm FT8 working frequency (1296.174 MHz, as in WSJT-X) is in the default frequency list for new or reset lists; 70cm already had 432.174. Since v0.7.2, FT4 has its own spots there too (432.170 and 1296.170 MHz, as PH2M uses them), and there is an 8m button (FT8 on 40.680 MHz, Region 1) for stations with an 8m permit. These rows are added once to an existing frequency list on first start; no reset needed.

QO-100 (since v0.7.0). A QO-100 band button tunes FT8 on the satellite (10489.540 MHz downlink / 2400.040 MHz uplink). QSOs made on the transponder log as a satellite QSO, as LoTW wants: FREQ / BAND = uplink (13cm), FREQ_RX / BAND_RX = downlink (3cm), PROP_MODE SAT, SAT_NAME QO-100, SAT_MODE SX - as MSHV logs them - whichever side the radio's dial shows. New DXCC / band colours check against 13cm, the band these QSOs are logged on. RUMlog drops satellite fields from the usual WSJT-X UDP path, so with a secondary UDP server set (e.g. a RUMlog bridge) a QO-100 QSO is sent only as ADIF there.

TX and RX sliders (since v0.6.0). The Pwr slider is now labelled TX. With TCI audio it shows the SDR program's own drive setting and moves with it, so nothing changes the radio's power until you move it (it used to show 0 after a start, and moving it set the SDR program's RF power). With sound card audio it is the transmit audio level as before, now shown at its saved level from the start. A new RX slider beside it raises or lowers the received audio going to the decoder and the level meter (-20 to +20 dB, 0 = as received), for any radio.

Choose which wanted filters show (since v0.6.0): View > Wanted filters (or right-click a filter's label) shows or hides Callsign, Prefix, Grid and Country one by one, to give the Rx window more room. A hidden filter with text in it still applies.

A new band starts with no automatic calling (since v0.5.2). Changing band - from the band buttons or combo box, or on the radio / SDR program - switches Auto CQ off, and the status bar says so. AnsB4 and 1 QSO stay as you set them (they were switched off too up to v0.5.3); a mode change leaves all of them alone.

No crash while TCI is reconnecting (since v0.7.0). A frequency, PTT or rig restart arriving while the TCI link was still connecting could crash JTDX-VU (same fault as the quit crash fixed in v0.4.0, now closed for every path).

Settings boxes ignore a passing scroll (since v0.7.5). A drop-down or number box in Settings reacts to the mouse wheel only after you click it, so scrolling down the page can't change the rig, a port or a device by accident.

Bypass button back (since v0.7.5): the Auto CQ button had been drawn over the Bypass button below it, so Bypass looked missing (iw1gb).

Safer double-click on a decode (since v0.7.5). Double-clicking a separator line, a free-text line under AutoSeq, or a <your-call> 73 / RR73 line that names no sender no longer flips the Tx period, clears the DX call or arms an empty message, and RR73 is never taken as a callsign. Contributed by Vinod VU3ESV.

No cut-off late transmission (since v0.7.5). Enable Tx (or an AutoSeq reply) late in your Tx period no longer keys up and sends only the tail of the message, which the other station can't decode. A late start is allowed only in the first fifth of the period (FT8 3 s, FT4 1.5 s, FT2 0.75 s, JT65 / JT9 12 s); after that Enable Tx stays on and Tx starts at your next period (KK4CDK). JTTY and WSPR are unchanged.

Stays in the QSO when the DX works someone else first (since the next release). If a station calls you and gets your report, then finishes a QSO with another station first, its 73 to them no longer makes AutoSeq start over with your grid call; it keeps sending your report (issue #6, marinfyi).

Rig mode shown (since v0.7.0). The round rig-status light left of the frequency is now a box showing the mode the rig reports (DIGU, USB, LSB...), in the frequency's font: green when it is the mode set in Settings > Radio, yellow when not - a radio left in LSB after a band change stands out. Orange while connecting, red ERR on a rig control failure (click it to reset, as before). Works in light and dark style.

Show US State (since v0.7.4; Settings > General, beside Show DXCC names). U.S.A. stations show as U.S.A.:FL. The grid in the message is used first, and a square that covers several states lists them, largest share first (U.S.A.:KY-IN-OH). Without a grid, the callsign's state comes from the FCC licence database. That is the licence address, so a portable or moved station can show its home state. Both tables are built into the app from public-domain data: US Census state boundaries (tools/build_us_grid_states.py) and the FCC's weekly amateur dump (tools/build_us_call_states.py, the same rules as DXCA's WAS lookup). A newer us_call_states.txt in the log directory overrides the built-in one. Asked for by KK4CDK (Miguel), after the option in JTDX 2.2.160. Canadian stations get their province or territory the same way (Canada:ON, since v0.7.5; the box now reads Show US State / VE province): from the grid first (Canada:QC-ON for FN25), from Natural Earth's public-domain boundaries (tools/build_ca_grid_provinces.py), else from the callsign's prefix - VE/VA 1-9 (VE3 = ON), VO1/VO2 = NL, VY0 = NU, VY1 = YT, VY2 = PE, and the special-event prefixes by the same digits. A station that moved province but kept its call shows its old one when it sends no grid. Also asked for by Miguel KK4CDK.

FlexRadio over VITA-49, no SmartSDR needed (since v0.7.0). Rig FlexRadio VITA-49 Slice A..H with the radio's address (e.g. 192.168.1.20:4992) in the FlexRadio: field of Settings > Radio — or press Discover (since v0.7.4) beside it to find radios on the LAN (not over a VPN or between VLANs) — talks SmartSDR straight to a FLEX-6000/8000: it takes or creates a slice, tunes it, sets DIGU and keys it, and with Use TCI / VITA-49 Audio ticked the receive audio comes in as a DAX stream over VITA-49 and the transmit audio goes out the same way, so no DAX driver, virtual sound card or TCI bridge sits in the path. The radio sends that audio to the computer over UDP. JTDX-VU first sends the radio a packet, so the audio gets back through a firewall, NAT or VPN (since v0.7.4). If no audio arrives on two connects in a row, it stops reconnecting and says why (usually the firewall), and clicking the red ERR box reconnects. Audio that was flowing and then stops (a VPN or network drop) is not a firewall: it keeps retrying until the link is back, and goes back to the frequency you were on (both since v0.7.5). A key-up the radio is slow to confirm (over 3 s) skips just that over and keys again next cycle; only three in a row reconnect, and any reconnect goes back to your frequency instead of the radio's default 14.100 slice. If the link dies mid-over (the computer's address changed), the unkey is lost: JTDX-VU reconnects at once and closes its old session, which unkeys the radio (both since v0.7.6). One API session, so the radio's relays click once per over. Ported from the MSHV-Mac backend. No split: use Fake It or None. The TX slider is the radio's RF power (it follows the radio, which keeps power per band; while tuning it is the tune power). View > FlexRadio Panel... shows the radio's meters and the slice's antennas and mode, and sets transmit power, the antenna tuner and the M-series front speaker, as MSHV's Flex panel does; antennas are remembered per band for transverter users. Each connection puts the slice back on your last frequency in your data mode. To go to a frequency that is not in your list (a DXpedition on 28.088, say) type it over the band name in the main window's band box and press Enter; the radio follows. Several copies on one radio (since v0.7.5): run one JTDX-VU profile per slice, each set to its own slice letter (Slice A, Slice B...). A Flex lets only two programs be GUI clients at a time (multiFLEX; the 6700 answers a third with client gui refused (0xf3000001)), so the third and fourth copies join the first copy's station as non-GUI clients, the way SmartSDR's DAX program does, and take one of the radio's remaining slices: FLEX-6400 and Aurora 510 have 2 slices, 6600, 8600 and Aurora 520 have 4, 6700 and 8800 have 8 (an M suffix changes nothing). Start the copies one after another, give every copy a different slice letter, and close them with Quit so each removes the slice it made. Asked for by KK4CDK. Only the first two copies can transmit: on a real FLEX-6700 the third and fourth copies receive and key PTT, but the radio takes no transmit audio from them (their DAX TX stream stays tx=0), so they would go out silent; since the next build they say so on the status bar instead ("the radio gives this copy no transmit audio"). To transmit from four copies, run them all through SmartSDR and DAX with your usual CAT and DAX sound devices, as stock JTDX does (DAX mixes the copies onto one station), not as VITA-49 copies. Connecting and receiving work on a FLEX-6600; transmit is so far verified only against a software stand-in (tools/flex_selftest.sh). Each connection appends a trace to flex_trace.txt in the profile's data folder. If you copy a QO-100 profile for the Flex, set its QO-100 rig IF back to 0.

TCI reconnects on its own (since v0.5.2). If the SDR program (AetherSDR, ExpertSDR, Thetis, ...) is closed or restarted, Tx halts and the status bar says "TCI: ... reconnecting every 5 s" instead of the Rig Control Error box; once the SDR program is back it shows "TCI reconnected" and carries on. Other rig types behave as before. Up to v0.7.6-rc1, a drop in the middle of an over left every later over silent (PTT keyed, no TX audio) until JTDX-VU was restarted; fixed for the next build. With TCI audio on, JTDX-VU also watches the receive audio: if none arrives for 10 s (Tx aside), it asks for it again once, then says "no audio from the SDR program - restart it" and keeps retrying until audio is back ("TCI audio back"). AetherSDR 26.9.5 can stop sending TCI audio after the last audio client has been gone for over 10 s; restarting AetherSDR clears it, JTDX-VU can stay open. If the SDR program's opening message leaves out your receiver's frequency (AetherSDR can, when its slice sits on the other TCI receiver), JTDX-VU asks for it instead of reconnecting every 5 s with "TCI sent an unrecognized frequency" (since v0.7.5). If the SDR program refuses a frequency change and stays where it is (AetherSDR with an IC-705's dial lock on), JTDX-VU carries on at that frequency instead of dropping the link mid-over with "TCI failed set rxfreq"; with Split = Fake It that used to happen on every over (fixed for the next build). Unlock the dial (Aether's slice lock button sets the IC-705's) for Fake It to work.

Call Non-Stop: the Auto CQ button in the right-hand button column, directly under Monitor in every mode (since v0.5.3), also "CNS" in the AutoSeq menu. After each logged QSO, JTDX-VU goes straight back to CQ or the next caller instead of halting Tx. Only QSOs from your own CQ continue: when you answer someone (double-click their CQ or QSO), Tx halts after that QSO, as with 1 QSO, and while CNS is on AutoSeq answers only stations calling you, never other CQs. CNS is off in Hound mode. A station that doesn't answer is dropped after the AutoSeq counters (Settings > Sequencing), as usual. While CNS is on the Tx watchdog is the Auto CQ time limit (Settings > JTTY, 5 minutes by default; 10 minutes fixed up to v0.5.0), so unanswered CQ still stops. While CNS is on, the button counts that watchdog down (since v0.7.2) - "4:37", or "12m" from 10 minutes up, on a second line under "Auto CQ" so the button keeps its width (since v0.7.3; v0.7.2 widened it): it runs down while you transmit and holds still while Tx is idle, like the "WD" box. Auto CQ and 1 QSO exclude each other (since v0.6.0): switching Auto CQ on clears 1 QSO, and pressing 1 QSO during an Auto CQ run means "finish this QSO, then stop" - both go off when Tx halts after it.

No Stop button: Monitor is the one start/stop control for monitoring (switching it off also ends a "Decode remaining files" run).

Needed-DXCC alerts when a decoded station is ATNO, a new band or a new mode (in this mode on no band yet), as in MSHV. Alerts go to macOS notifications and/or Telegram, with a per-call/band cooldown (5–60 min).

• The Club Log app password and the Telegram bot token are stored in the macOS Keychain (service JTDX-VU), never in the .ini.

JTTY (new in v0.3.0): WSJT-X 3.2's period-free RTTY-style keyboard mode, ported from 3.2.0-rc1 — decoder, transmit, macros, Call next and Serial Number. Click, double-click or select a callsign in either decode pane to put it in DX Call, as in N1MM; punctuation around it is ignored.

• A JTTY screen of its own (new in v0.5.0): the FT-only controls (Report, CL, Hound, AutoTX, AutoSeq, Wanted and the wanted filters, Bypass, 1 QSO, AnsB4, Enable Tx, Hint, SWL, AGCc, Filter, Decode, TX Even, the period progress bar) are hidden while JTTY is selected and come back in the other modes. The rest is regrouped: all the buttons (Tune, Monitor, Auto CQ, Halt Tx, Log QSO, Erase, Clear DX) in the right-hand column, the macro panel across the bottom, and S / R / Name QSO fields in a column beside Tx / Rx (RST sent and received, logged instead of a fixed 599; the name comes from the log when known), and a Calls heard list of the stations sending in the JTTY decodes (the call after DE, a call sent twice, the call in a CQ - not the station being called; since v0.6.0), coloured like Band Activity from the log / Club Log (new DXCC, new on the band, new in JTTY, new call, worked). Click a call to make it DX Call and put Rx on its frequency.
• 24 macros in three banks: F1–F8, Shift+F1–F8 and Option (Alt)+F1–F8, shown eight at a time as labelled buttons (Bank 1/2/3); each key works whichever bank is on screen. A Set picker on the panel switches macro sets. Macros and their button labels are edited in Settings > JTTY.
• Type-ahead: a macro or typed message sent while another is on the air is queued ("Next: …" on the panel) and goes out as soon as the current one ends. Halt Tx or Esc clears the queue.
• Variables: %M my call, %H DX call, %Q Call next, %N serial, %E the set's exchange, %RST the RST sent, %NAME his name, and station details %OP (name), %QTH, %TX (radio), %ANT (antenna). Set Serial Number to "none" for a non-contest QSO and %N is left out of %E.
• Auto logging from a macro (since v0.7.3): put %LOG in a macro (e.g. "TU %H 73 %LOG") and sending it also logs the QSO, straight in without the Log QSO dialog; %LOG itself is not sent, and a macro of just %LOG only 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.
• Auto CQ (right-hand button column) repeats a macro with a gap after each call, 10 s by default, and stops after the time limit (5 minutes by default, since v0.5.1), which the button counts down while it runs (since v0.7.2); pressing it again turns it off and halts a CQ on the air (Esc and Halt Tx stop any JTTY send). In the FT modes the same button is Call Non-Stop. Settings > JTTY sets the macro, gap, call limit and stop-on-my-call, the station details, and named macro sets, each with its own %E exchange ("Contest (WSJT-X)" sends %RST %N, "Ragchew / DX" sends %RST). Serial Number shows only when the active set uses %N.
• JTTY QSOs are logged as ADIF MODE MFSK / SUBMODE JTTY, like FT4.

JTTY is by Joe Taylor K1JT, Steve Franke K9AN, Rob G4KLA and the WSJT-X team.

Profiles (Profile menu): one complete settings set per rig — VITA-49, TCI, DAX, a QO-100 setup with its own CAT and audio — each with its own log and data directory. New profile from current... copies the current settings, switching restarts the program, and a plain launch opens the profile last used. Under the hood these are JTDX's -r <name> instances (JTDX-VU - <name>.ini), so -r on the command line still works. QO-100 through a transverter with SDR-Control for Icom: Settings > Frequencies > Frequency Calibration > QO-100 rig IF (e.g. 28.540) is what JTDX-VU sends the rig for the QO-100 channel; the readback (downlink, uplink or IF) is shown as 10489.540 and the log carries 2400.040 / 10489.540, PROP_MODE SAT, SAT_NAME QO-100.

FT2 (new in v0.3.0): FT4's protocol at twice the speed — 3.75 s periods, 41.67 baud. 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 LZ2HV added it in 2.76.5 on 2026-03-24. JTDX-VU uses no Decodium code: it decodes and transmits FT2 with a scaled copy of JTDX's own FT4 chain, with MSHV's implementation as the reference. Default dial frequencies follow MSHV (14.084, 7.052, 21.144 MHz …). Add the FT2 button in View > Band & Mode Buttons... if you want it on the switcher. Since v0.6.0 the decoder also has MSHV's log-sum-exp demapper and "AP7": once a call pair has been decoded, the station's expected reply two periods later is matched against the likely messages for that pair, so reports a few dB below the normal floor still decode (shown with a trailing 7). Measured on identical audio (a scripted QSO plus noise played to both over TCI, 2026-10-07): JTDX-VU and MSHV decode FT2 to the same floor, everything at -12 dB, about half at -15, nothing at -17, with no false decodes. MSHV prints FT2 reports 2-3 dB lower than JTDX-VU for the same signal, so compare counts, not numbers. Since v0.7.0 AP7 keeps a call pair across short quiet spells and accepts decodes by MSHV's own rule; at -15 dB that roughly doubled the decodes (25 -> 47 of 120, MSHV 61), with no false AP7 decodes.