Hi Decodium Team,I noticed an issue regarding the frequency transmitted via UDP to external loggers (in my case, OpsLog) when using Fake It for FT8 operations. Configuration:Mode: FT8 / Data/Pkt Split Operation: Fake It UDP Server: Multicast 239.255.0.1:2237 (Primary traffic: Decode, Status, QSO logged enabled) VFO Dial Frequency : 7074.00 kHz Issue Description:When transmitting with an audio offset (e.g., DF at 2500 Hz), the Status UDP packet and the software display correctly show the recalculated RF frequency (7075.00 kHz) during transmission or when hitting Tune.However, as soon as a QSO is completed and the software returns to RX, the QSO logged UDP packet (Type 12) sends the base RX Dial frequency (7074.00 kHz) instead of the actual TX RF frequency (7075.00 kHz = VFO Dial TX Audio Offset).As a result, the external logger records the QSO on 7074.00 kHz instead of the true transmit frequency, unlike WSJT-X or JTDX which properly include the audio offset (DF) in the logged packet.(Note: Switching to 'Rig' split is not an option for my transceiver setup as it does not switch VFOs properly via CAT).Could you please update the UDP QSO logged packet generation so that it logs the recalculated TX frequency ($F_{\text{Dial}} \text{DF}$) instead of the raw RX Dial frequency when Fake It is active?Thank you for your help and for this great software!Best 73, When transmitting with an audio offset (e.g., DF at 2500 Hz), the Status UDP packet and the software display correctly show the recalculated RF frequency (7075.00 kHz) during transmission or when hitting Tune.However, as soon as a QSO is completed and the software returns to RX, the QSO logged UDP packet (Type 12) sends the base RX Dial frequency (7074.00 kHz) instead of the actual TX RF frequency (7075.00 kHz = VFO Dial TX Audio Offset).As a result, the external logger records the QSO on 7074.00 kHz instead of the true transmit frequency, unlike WSJT-X or JTDX which properly include the audio offset (DF) in the logged packet.(Note: Switching to 'Rig' split is not an option for my transceiver setup as it does not switch VFOs properly via CAT).Could you please update the UDP QSO logged packet generation so that it logs the recalculated TX frequency ($F_{\text{Dial}} \text{DF}$) instead of the raw RX Dial frequency when Fake It is active?Thank you for your help and for this great software!Best 73, Issue Description:When transmitting with an audio offset (e.g., DF at 2500 Hz), the Status UDP packet and the software display correctly show the recalculated RF frequency (7075.00 kHz) during transmission or when hitting Tune.However, as soon as a QSO is completed and the software returns to RX, the QSO logged UDP packet (Type 12) sends the base RX Dial frequency (7074.00 kHz) instead of the actual TX RF frequency (7075.00 kHz = VFO Dial TX Audio Offset).As a result, the external logger records the QSO on 7074.00 kHz instead of the true transmit frequency, unlike WSJT-X or JTDX which properly include the audio offset (DF) in the logged packet.(Note: Switching to 'Rig' split is not an option for my transceiver setup as it does not switch VFOs properly via CAT).Could you please update the UDP QSO logged packet generation so that it logs the recalculated TX frequency ($F_{\te ## Bug Report — Decodium 1.0.640 ### User Description ### System Info ``` OS: Windows 11 Version 25H2 x86_64 Qt: 6.11.0 App: Decodium 1.0.640 Screen 0: 1920x1080 @96 DPI (scale 1.00) Screen 1: 1920x1080 @96 DPI (scale 1.00) AudioIn: Signalink_micro_Ligne (USB AUDIO CODEC) AudioIn: Microphone (USB Audio CODEC ) AudioIn: Microphone (USBMIC1.) AudioIn: CABLE-A Output (VB-Audio Cable A) AudioIn: CABLE-B Output (VB-Audio Cable B) AudioIn: CABLE-C Output (VB-Audio Cable C) AudioIn: CABLE-D Output (VB-Audio Cable D) AudioIn: VoiceMeeter Output (VB-Audio VoiceMeeter VAIO) AudioIn: Voicemeeter Out A1 (2- VB-Audio Voicemeeter VAIO) AudioIn: Voicemeeter Out A2 (2- VB-Audio Voicemeeter VAIO) AudioIn: Voicemeeter Out A3 (2- VB-Audio Voicemeeter VAIO) AudioIn: Voicemeeter Out A4 (2- VB-Audio Voicemeeter VAIO) AudioIn: Voicemeeter Out A5 (2- VB-Audio Voicemeeter VAIO) AudioIn: Voicemeeter Out B1 (2- VB-Audio Voicemeeter VAIO) AudioIn: Voicemeeter Out B2 (2- VB-Audio Voicemeeter VAIO) AudioIn: Voicemeeter Out B3 (2- VB-Audio Voicemeeter VAIO) AudioOut: Signalink_HP (USB AUDIO CODEC) AudioOut: Haut-parleurs (USB Audio CODEC ) AudioOut: XG2405 (NVIDIA High Definition Audio) AudioOut: Haut-parleurs (USBMIC1.) AudioOut: CABLE-A Input (VB-Audio Cable A) AudioOut: CABLE-B Input (VB-Audio Cable B) AudioOut: CABLE-C Input (VB-Audio Cable C) AudioOut: CABLE-D Input (VB-Audio Cable D) AudioOut: VoiceMeeter Input (VB-Audio VoiceMeeter VAIO) AudioOut: Voicemeeter AUX Input (2- VB-Audio Voicemeeter VAIO) AudioOut: Voicemeeter In 1 (2- VB-Audio Voicemeeter VAIO) AudioOut: Voicemeeter In 2 (2- VB-Audio Voicemeeter VAIO) AudioOut: Voicemeeter In 3 (2- VB-Audio Voicemeeter VAIO) AudioOut: Voicemeeter In 4 (2- VB-Audio Voicemeeter VAIO) AudioOut: Voicemeeter In 5 (2- VB-Audio Voicemeeter VAIO) AudioOut: Voicemeeter Input (2- VB-Audio Voicemeeter VAIO) AudioOut: Voicemeeter VAIO3 Input (2- VB-Audio Voicemeeter VAIO) ``` ### QML Errors (5) ``` 2026-09-20T11:36:16 file:///C:/Users/lapep/AppData/Local/Programs/Decodium/qml/decodium/components/SettingsTab1.qml:802:9: QML Connections: Detected function "onCivAddressChanged" in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name. 2026-09-20T11:36:16 file:///C:/Users/lapep/AppData/Local/Programs/Decodium/qml/decodium/components/SettingsTab1.qml:846:13: Unable to assign [undefined] to bool 2026-09-20T11:36:16 file:///C:/Users/lapep/AppData/Local/Programs/Decodium/qml/decodium/components/SettingsTab1.qml:900:13: Unable to assign [undefined] to bool 2026-09-20T11:36:16 file:///C:/Users/lapep/AppData/Local/Programs/Decodium/qml/decodium/components/SettingsTab1.qml:939:17: Unable to assign [undefined] to double 2026-09-20T11:36:16 file:///C:/Users/lapep/AppData/Local/Programs/Decodium/qml/decodium/components/SettingsTab1.qml:1059:13: Unable to assign [undefined] to bool ``` ### Auto-Analysis No known bug patterns matched. This may be a new issue.