Decodium don't start to transmit CQ (MacBook Air with MacOS 13.7.8 (22H730)) TX6 field stays empty... TRX is a Yaesu FTX-1, tried with hamlib direct and with hamlib/flrig. Transmitting for tuning works as expected. [2026-08-02 18:56:00.071] [INFO] SoundOutput: Sending [2026-08-02 18:56:00.071] [INFO] SoundOutput: Idle [2026-08-02 18:56:01.071] [INFO] SoundOutput: Sending [2026-08-02 18:56:01.071] [INFO] SoundOutput: Idle [2026-08-02 18:56:01.244] [INFO] syncLegacyBackendState: legacy TX enable off while AutoCQ active -> rearm TX [2026-08-02 18:56:01.384] [INFO] [LegacyAudio][PCM] samples=240 rms=0.01378 peak=0.03607 nonzero=239 mode=FT8 monitor=1 [2026-08-02 18:56:01.764] [INFO] [LegacyAudio][WATERFALL] bins=400 min=0 max=127 mean=46.7 nonzero=375 mode=FT8 [2026-08-02 18:56:02.245] [INFO] syncLegacyBackendState: legacy TX enable off while AutoCQ active -> rearm TX [2026-08-02 18:56:03.079] [INFO] SoundOutput: Sending [2026-08-02 18:56:03.079] [INFO] SoundOutput: Idle [2026-08-02 18:56:03.245] [INFO] syncLegacyBackendState: legacy TX enable off while AutoCQ active -> rearm TX [2026-08-02 18:56:03.400] [INFO] [LegacyAudio][PCM] samples=240 rms=0.01516 peak=0.03812 nonzero=240 mode=FT8 monitor=1 [2026-08-02 18:56:03.768] [INFO] [LegacyAudio][WATERFALL] bins=400 min=0 max=205 mean=46.0 nonzero=375 mode=FT8 [2026-08-02 18:56:04.494] [INFO] syncLegacyBackendState: legacy TX enable off while AutoCQ active -> rearm TX [2026-08-02 18:56:05.073] [INFO] SoundOutput: Sending [2026-08-02 18:56:05.073] [INFO] SoundOutput: Idle ## Bug Report — Decodium 1.0.508 ### User Description ### System Info ``` OS: macOS Ventura (13.7.8) x86_64 Qt: 6.11.0 App: Decodium 1.0.508 Screen 0: 1440x900 @72 DPI (scale 1.00) AudioIn: Built-in Microphone AudioIn: USB Audio Device AudioOut: Built-in Output AudioOut: USB Audio Device ``` ### QML Errors (1) ``` 2026-08-02T18:49:06 file:///Applications/Decodium4.app/Contents/Resources/qml/decodium/components/SettingsDialog.qml:2819:29: Unable to assign [undefined] to bool ``` ### Auto-Analysis No known bug patterns matched. This may be a new issue.