v2.4.0-pre2 — six bug fixes, a new Audio Filter dialog, and lots of small improvements

[mm5agm]

⚠️ Pre-release / experimental. This is the second public pre-release on the v2.4.0 line. The auto-updater will not install it — you have to download it yourself. If you're running v2.3.9 happily, there's no urgency to update; if you tried pre1 and stuck with it, this is the same line but with a stack of fixes and small new features on top.

Voice control v1 from pre1 is still in here, unchanged. If you missed pre1, see USER_MANUAL.md §17 Voice Control for what voice does and how to enable it.

What's new since pre1

Eleven commits' worth — most are reporter-driven (thanks to Alessandro IK2XRW, Bill W1WRH, solson888, and Jacek SP3L in particular).

Bug fixes

• PROC button now actually drives the radio ([BUG] #51). Reported by solson888 on the FTdx10, confirmed broken on every supported Yaesu HF radio. YWC was sending PR0; / PR1; which the Yaesu CAT manual defines as read commands, not set commands — so the on-screen toggle never reached the radio. The fix sends PR00; / PR01; (and uses the values the radio actually accepts, not the ones the manual lists, which are wrong — the manual will be reporting itself shortly). The PROC level slider also now reads back from the radio after each write, so the on-screen number is always what the radio really has.
• Old "IF Low Cut" dropdown was a phantom control. The CAT command it sent (SL) isn't in any current Yaesu HF transceiver's CAT command list. It looked like it was doing something on screen, but nothing was reaching the radio. Replaced with the new Audio Filter popout (see below).
• Ctrl+F no longer hijacks the browser's find-in-page. Bare F still toggles fullscreen as documented; Ctrl+F now goes to the browser as it should.

New features

• Audio Filter popout — new button in each VFO panel (where the broken Low Cut dropdown used to be). Opens a popout dialog for the per-mode LCUT FREQ / LCUT SLOPE / HCUT FREQ / HCUT SLOPE. The radio stores these per-mode internally; the dialog reads back the current mode's values when opened and re-queries when you change mode. On the FTdx101 family you can open one dialog per VFO and adjust both at once.
• ZIN button for CW (ZIN button for CW #55), requested by Alessandro. Per-VFO ZIN button on each VFO panel header (always visible, S&P-friendly) and a ZIN button in the CW Keyer popout. Triggers the radio's CW Auto-Zero-In so received CW signals snap to your configured pitch.
• Fldigi launch button (Start button for fldigi #52), requested by Bill W1WRH. Same pattern as the WSJT-X / JTAlert / Log4OM / GridTracker buttons — configure path in Application Setup, tick Show, save. Off by default.
• DX Spots list click sets mode too (Click spot on spectrum → set frequency and mode. #57), requested by Alessandro. Clicking a row in the DX Spots popup now follows the QSY with a band-plan-aware mode change, matching what spectrum-panel clicks already do. Click an FT8 spot from USB and the radio flips to DATA-U in one step.
• SDRplay DLL auto-detect ([BUG] no SDR-Play recognized #53), prompted by Alessandro. YWC now actively searches for sdrplay_api.dll rather than relying on Windows PATH. New SDRplay install path field on the Settings page with an auto-detect display and a native Browse… folder picker. Standard installs just work; non-standard installs can point YWC at the right folder.
• Spectrum click crosshair stays on the clicked frequency. Used to drift left/right by hundreds of Hz until you next moved the mouse; now snaps to the canvas centre at click time and only moves again when you move the mouse.

Install

1. Download the v2.4.0-pre2 installer from the Releases page — the .exe asset appears once the build workflow finishes (a few minutes after this post goes up).
2. Run the installer — upgrades over v2.3.9 or v2.4.0-pre1 cleanly. Your settings, memories, calibrations and per-band profiles all carry over.
3. Launch YWC. If you were on pre1, voice control and all your settings remain as they were.

If you find anything broken, please raise a GitHub Issue using the Report a bug button on the About page (it pre-fills the diagnostics). General "tried this, here's how it went" comments here in this Discussion are perfect.

73,
Colin MM5AGM