ChatGPT
I'm experiencing an issue with AetherSDR, a Linux/macOS/Windows SDR client
for FlexRadio transceivers (https://github.com/ten9876/AetherSDR).
My system:
- AetherSDR version: 26.5.1
- Qt version: 6.11.0
- OS: macOS
- Radio: FLEX-8600 fw 4.2.18.41174
Before writing the bug report, please read the AetherSDR project context at
https://raw.githubusercontent.com/ten9876/AetherSDR/main/CLAUDE.md
for architecture overview, data flow, protocol details, and known issues.
Based on my description below, write a complete GitHub bug report.
Do NOT ask me follow-up questions — just write the best report you can
from what I've provided. Output it in one response, ready to paste.
Use GitHub-flavored Markdown formatting (headers, code blocks, bullet points).
Format it as:
Title: (short, descriptive)
What happened?
(expand on my description with clear, specific language)
What did you expect?
(infer the expected behavior from context)
Steps to reproduce
(numbered steps based on my description)
Radio model & firmware
(pre-filled above)
OS & version
(pre-filled above)
Developer Notes
(After reviewing the codebase, suggest which source files and functions
are most likely involved, what logging categories to enable in
Help → Support to capture diagnostic data, and any potential root causes
based on the code architecture. Reference specific file paths and line
numbers where possible.)
Here is my issue:
RADE receive audio does not work on MacOS. Works with Windows and Linux using the same settings.
Title: RADE receive audio does not function on macOS while working correctly on Windows and Linux
What happened?
RADE receive audio processing does not work on macOS in AetherSDR when connected to a FLEX-8600 running SmartSDR firmware 4.2.18.41174.
The same RADE settings and radio configuration work correctly on both Windows and Linux installations of AetherSDR, but receive audio processing is non-functional on macOS.
Observed behavior:
Standard receive audio path functions normally on macOS
Radio connection, panadapter, waterfall, and general audio streaming appear operational
Enabling RADE processing has no audible effect on receive audio
No processed RADE audio is heard through the macOS audio output path
The identical configuration works correctly on Windows and Linux using the same radio and comparable settings
This appears to be platform-specific behavior affecting the macOS audio pipeline, DSP path, plugin loading, audio device handling, threading/timing, or sample format conversion associated with RADE receive processing.
What did you expect?
RADE receive audio processing should function identically across all supported platforms.
When RADE receive processing is enabled on macOS:
Processed receive audio should be heard through the selected audio output device
RADE DSP changes should audibly affect RX audio
Behavior should match Windows and Linux operation using the same settings and radio
Audio routing and processing should remain stable during normal receive operation
Steps to reproduce
Launch AetherSDR 26.5.1 on macOS
Connect to a FLEX-8600 running firmware 4.2.18.41174
Configure normal receive audio output
Enable RADE receive audio processing
Verify that standard RX audio otherwise functions normally
Observe that RADE receive audio processing does not function on macOS
Repeat the same configuration on Windows or Linux
Observe that RADE receive audio processing works correctly on those platforms
Radio model & firmware
Radio: FLEX-8600
Firmware: 4.2.18.41174
OS & version
OS: macOS
AetherSDR version: 26.5.1
Qt version: 6.11.0
Developer Notes
Based on the AetherSDR architecture and the platform-specific nature of the issue, the most likely areas involved are the macOS audio backend, DSP processing chain integration, or platform-specific audio format handling.
Potentially relevant areas to inspect include:
Audio pipeline and platform backend
src/audio/
src/audio/output/
src/audio/coreaudio/
Any macOS CoreAudio-specific device initialization and callback code
Audio buffer format conversion between Qt multimedia and CoreAudio
Likely suspects:
CoreAudio sample format mismatch
Float/int16 conversion issue
Incorrect channel mapping
Unsupported buffer size or timing assumptions
Audio callback starvation or threading synchronization issue on macOS only
RADE DSP integration
src/dsp/
src/rade/
RX audio processing chain insertion points
DSP enable/disable state handling
Conditional compilation sections for macOS
Potential root causes:
RADE processing object not initialized on macOS
DSP chain bypassed due to platform conditional logic
Failure loading RADE-related libraries or models on macOS
Incorrect audio stream format passed into the RADE pipeline
SIMD/vectorization differences between platforms
Timing or buffer alignment assumptions failing under CoreAudio
Qt Multimedia / device handling
Qt 6.11.0 may expose platform-specific behavior differences between:
WASAPI (Windows)
PulseAudio/PipeWire/ALSA (Linux)
CoreAudio (macOS)
Areas worth checking:
Audio device negotiation
Requested vs actual sample rate
Buffer frame sizes
Audio callback threading model
Stereo/mono handling
Latency compensation logic
Logging recommendations
Enable the following logging categories from:
Help → Support
Recommended categories:
Audio
DSP
RADE
Network audio streams
Device initialization
Qt multimedia/backend logging
RX stream processing
Particularly useful diagnostics would include:
Selected audio device information
Actual negotiated sample rates
Audio buffer sizes
DSP chain initialization success/failure
RADE model/plugin load status
RX stream format information
Audio callback underruns or dropped frames
Any macOS CoreAudio warnings/errors
Additional debugging suggestions
Useful comparisons:
Compare startup logs between macOS and Windows/Linux
Compare negotiated audio formats across platforms
Verify whether RADE processing callbacks are invoked on macOS
Verify whether processed audio buffers contain valid sample data before output
Test with alternate macOS output devices
Inspect any platform-specific #ifdef Q_OS_MACOS handling in audio or DSP code
Because the issue is isolated to macOS while identical settings function correctly on Windows and Linux, the problem is likely in:
macOS-specific audio backend integration
format conversion
DSP insertion into the CoreAudio playback path
or a platform-specific initialization failure being silently ignored.
support-bundle-20260513-112400.tar.gz
ChatGPT
I'm experiencing an issue with AetherSDR, a Linux/macOS/Windows SDR client
for FlexRadio transceivers (https://github.com/ten9876/AetherSDR).
My system:
Before writing the bug report, please read the AetherSDR project context at
https://raw.githubusercontent.com/ten9876/AetherSDR/main/CLAUDE.md
for architecture overview, data flow, protocol details, and known issues.
Based on my description below, write a complete GitHub bug report.
Do NOT ask me follow-up questions — just write the best report you can
from what I've provided. Output it in one response, ready to paste.
Use GitHub-flavored Markdown formatting (headers, code blocks, bullet points).
Format it as:
Title: (short, descriptive)
What happened?
(expand on my description with clear, specific language)
What did you expect?
(infer the expected behavior from context)
Steps to reproduce
(numbered steps based on my description)
Radio model & firmware
(pre-filled above)
OS & version
(pre-filled above)
Developer Notes
(After reviewing the codebase, suggest which source files and functions
are most likely involved, what logging categories to enable in
Help → Support to capture diagnostic data, and any potential root causes
based on the code architecture. Reference specific file paths and line
numbers where possible.)
Here is my issue:
RADE receive audio does not work on MacOS. Works with Windows and Linux using the same settings.
Title: RADE receive audio does not function on macOS while working correctly on Windows and Linux
What happened?
RADE receive audio processing does not work on macOS in AetherSDR when connected to a FLEX-8600 running SmartSDR firmware 4.2.18.41174.
The same RADE settings and radio configuration work correctly on both Windows and Linux installations of AetherSDR, but receive audio processing is non-functional on macOS.
Observed behavior:
Standard receive audio path functions normally on macOS
Radio connection, panadapter, waterfall, and general audio streaming appear operational
Enabling RADE processing has no audible effect on receive audio
No processed RADE audio is heard through the macOS audio output path
The identical configuration works correctly on Windows and Linux using the same radio and comparable settings
This appears to be platform-specific behavior affecting the macOS audio pipeline, DSP path, plugin loading, audio device handling, threading/timing, or sample format conversion associated with RADE receive processing.
What did you expect?
RADE receive audio processing should function identically across all supported platforms.
When RADE receive processing is enabled on macOS:
Processed receive audio should be heard through the selected audio output device
RADE DSP changes should audibly affect RX audio
Behavior should match Windows and Linux operation using the same settings and radio
Audio routing and processing should remain stable during normal receive operation
Steps to reproduce
Launch AetherSDR 26.5.1 on macOS
Connect to a FLEX-8600 running firmware 4.2.18.41174
Configure normal receive audio output
Enable RADE receive audio processing
Verify that standard RX audio otherwise functions normally
Observe that RADE receive audio processing does not function on macOS
Repeat the same configuration on Windows or Linux
Observe that RADE receive audio processing works correctly on those platforms
Radio model & firmware
Radio: FLEX-8600
Firmware: 4.2.18.41174
OS & version
OS: macOS
AetherSDR version: 26.5.1
Qt version: 6.11.0
Developer Notes
Based on the AetherSDR architecture and the platform-specific nature of the issue, the most likely areas involved are the macOS audio backend, DSP processing chain integration, or platform-specific audio format handling.
Potentially relevant areas to inspect include:
Audio pipeline and platform backend
src/audio/
src/audio/output/
src/audio/coreaudio/
Any macOS CoreAudio-specific device initialization and callback code
Audio buffer format conversion between Qt multimedia and CoreAudio
Likely suspects:
CoreAudio sample format mismatch
Float/int16 conversion issue
Incorrect channel mapping
Unsupported buffer size or timing assumptions
Audio callback starvation or threading synchronization issue on macOS only
RADE DSP integration
src/dsp/
src/rade/
RX audio processing chain insertion points
DSP enable/disable state handling
Conditional compilation sections for macOS
Potential root causes:
RADE processing object not initialized on macOS
DSP chain bypassed due to platform conditional logic
Failure loading RADE-related libraries or models on macOS
Incorrect audio stream format passed into the RADE pipeline
SIMD/vectorization differences between platforms
Timing or buffer alignment assumptions failing under CoreAudio
Qt Multimedia / device handling
Qt 6.11.0 may expose platform-specific behavior differences between:
WASAPI (Windows)
PulseAudio/PipeWire/ALSA (Linux)
CoreAudio (macOS)
Areas worth checking:
Audio device negotiation
Requested vs actual sample rate
Buffer frame sizes
Audio callback threading model
Stereo/mono handling
Latency compensation logic
Logging recommendations
Enable the following logging categories from:
Help → Support
Recommended categories:
Audio
DSP
RADE
Network audio streams
Device initialization
Qt multimedia/backend logging
RX stream processing
Particularly useful diagnostics would include:
Selected audio device information
Actual negotiated sample rates
Audio buffer sizes
DSP chain initialization success/failure
RADE model/plugin load status
RX stream format information
Audio callback underruns or dropped frames
Any macOS CoreAudio warnings/errors
Additional debugging suggestions
Useful comparisons:
Compare startup logs between macOS and Windows/Linux
Compare negotiated audio formats across platforms
Verify whether RADE processing callbacks are invoked on macOS
Verify whether processed audio buffers contain valid sample data before output
Test with alternate macOS output devices
Inspect any platform-specific #ifdef Q_OS_MACOS handling in audio or DSP code
Because the issue is isolated to macOS while identical settings function correctly on Windows and Linux, the problem is likely in:
macOS-specific audio backend integration
format conversion
DSP insertion into the CoreAudio playback path
or a platform-specific initialization failure being silently ignored.
support-bundle-20260513-112400.tar.gz