RimuSDR 1.1.20 : PC mic fixes
2 enhancements and 8 fixes across RimuSDR, RimuDAX and RimuCAT.
Version 1.1.20
Enhancements
RimuDAX
- Qt 6.12 - RimuDAX now uses Qt 6.12 on every platform, as RimuSDR has since 1.1.18. On Linux, Qt 6.12 needs a processor with SSE4.2 and POPCNT, so the amd64 .deb, RPM and AppImage also carry a second build made with Qt 6.8.3. The launcher checks the processor and starts the build that can run on it, so RimuDAX still starts on older processors such as the Intel Core 2. There is no change to how RimuDAX works. The arm64 and Raspberry Pi packages carry one build, as before.
RimuCAT
- Qt 6.12 - RimuCAT now uses Qt 6.12 on every platform, as RimuSDR has since 1.1.18. On Linux, Qt 6.12 needs a processor with SSE4.2 and POPCNT, so the amd64 .deb, RPM and AppImage also carry a second build made with Qt 6.8.3. The launcher checks the processor and starts the build that can run on it, so RimuCAT still starts on older processors such as the Intel Core 2. The arm64 and Raspberry Pi packages carry one build, as before.
Fixes
RimuSDR
- PC mic after a reconnect - With the mic input set to PC, the PC mic sent no audio after you disconnected and reconnected without restarting RimuSDR. The mic level meter did not move, and nothing was transmitted until RimuSDR was restarted. The PC mic now starts again on every connection. The log at the default level now also shows when the PC mic starts, and warns if you press MOX with the PC mic selected while it is not running. Thanks to Ron, NI0F, for the report.
- Windows: PC mic uses the mic you selected - On Windows, RimuSDR recorded the PC mic from the Windows Default Communications Device, not from the Input Device selected in Radio Setup > Audio. If a webcam held that role, RimuSDR transmitted the webcam's mic. RimuSDR now records from the selected mic, and the mic level control now sets that mic's recording level. If the selected mic is unplugged or will not start, RimuSDR uses the Windows default mic instead and writes a warning to the log. The log now names the mic being recorded each time the PC mic starts. Thanks to Ron, NI0F, for the report.
- Windows: PC mic after unplugging the mic - If the mic used for the PC mic was unplugged during a session, the PC mic stayed silent after the mic was plugged back in, until you disconnected and reconnected. RimuSDR now stops recording when that mic is unplugged, and starts again when it is plugged back in. While the selected mic is unplugged, RimuSDR does not record from another mic.
- Linux: PC mic after unplugging the mic - On Linux, if the mic used for the PC mic was unplugged during a session, the PC mic moved to another audio source and stayed there after the mic was plugged back in. That source could be the one that carries the PC's own playback, so a transmit with the PC mic could send PC audio, including RX audio, instead of your voice. RimuSDR now stops recording when that mic is unplugged, and starts again when it is plugged back in. The PC mic can no longer be moved to another source in pavucontrol or similar tools. Choose the mic in Radio Setup > Audio. If the last input device is removed while the PC mic is selected, RimuSDR now switches the mic input to MIC and shows the Microphone Unavailable dialog, as on Windows.
- RX audio after unplugging headphones - If the headphones or speakers that RX audio played through were unplugged and plugged back in during a session, RX audio did not come back to them until RimuSDR was restarted. On Windows, RX audio stopped, although other programs could be heard on the headphones. On Linux, RX audio moved to another output and stayed there. RimuSDR now plays RX audio on the default output while the device is unplugged, and moves it back when the device is plugged back in. On Linux, RX audio can no longer be moved to another output in pavucontrol or similar tools. Choose the output in Radio Setup > Audio, or change the default output in the desktop sound settings. Thanks to John, G4IRN, for the report.
- Linux: libraries load only from the package - On Linux, RimuSDR could load a shared library from the folder it was started from, before the system's own copy. The .deb, RPM and AppImage launchers, and the RimuSDR program in the .deb, now look for libraries only in the package and the system. RimuDAX and RimuCAT started from the RimuSDR RPM are covered too. There is no change to how RimuSDR works.
RimuDAX
- TCI status after a switch to DAX - After a switch from TCI mode to DAX mode with a TCI program connected, the status line could still say
TCI: 0 clients on 50001-50008, although the TCI server had stopped. It now readsTCI: off.
RimuCAT
- Passthrough port badge - In the port list, the badge of a USB passthrough port was too narrow and read "assthrough". It now reads "Passthru" in full.