Report preparation

• I used the AI-assisted bug report tool (Help → Support → File an Issue)
• I have attached a support bundle or log file

What happened?

I've noticed that when using the "official" windows x64 installer that RADE is not available as a modulation mode. However, if I compile the source using MSVC 22 that RADE becomes available. Apparently (according to Google Gemini) the opus.lib being used omits code necessary for RADE and suggests that the internal source code is not being referenced during the build. Here is the data from Gemini:

It appears you’ve identified a classic mismatch between a "standard" library and a "customized" library during the compilation process. The availability of RADE (which relies on the Opus codec for digital voice) is almost certainly being omitted from the installer because that build is linking against a generic Opus library rather than the specialized version required by AetherSDR.

Here is the breakdown of why this is happening and whether it's a bug or intentional.

1. The Opus "Flavor" Requirement

The RADE mode in AetherSDR doesn't just use Opus for compression; it often requires Opus to be compiled with specific flags (like fixed-point math or specific frame sizes) that aren't enabled in the standard DLLs you find in most installers.

• Linux: Most Linux package managers or the AetherSDR build scripts for Linux pull the development headers and compile Opus specifically for the target environment, which naturally includes the hooks RADE needs.
• Windows Build from Source: When you build locally, your build_opus project is compiling Opus from the source code provided in the AetherSDR repository (under the ten9876 fork). This ensures that the resulting opus.lib is perfectly "tuned" to support RADE.

2. Why the Claude-generated Installer fails

The installer generated by the Claude scripts is likely using a Pre-Compiled Binary of Opus to save time and reduce complexity.

• The Problem: If that pre-compiled binary is a standard, "off-the-shelf" version of Qt6WebSockets.dll or a generic opus.dll, it won't have the internal support for the RADE modulation hooks.
• The Result: During the final link stage of the installer's build, the AetherSDR code checks for those RADE-specific functions in the Opus library. If it doesn't find them, it doesn't throw an error; it simply disables the mode in the UI to prevent the program from crashing.

3. Is it a bug or intentional?

It is more of a packaging limitation than an intentional omission.

• Compilation Bug: No, the code is technically doing its job by hiding a mode it can't support with the available libraries.
• Build Script Flaw: Yes. The installer script is failing to package the custom build of Opus that you are successfully creating on your machine.

How to Fix the Installer version

Since you already have a working, RADE-capable AetherSDR.exe on your machine:

1. Swap the Executable: As you did before, copy your local AetherSDR.exe into the installer's directory.
2. Swap the Opus DLL: This is the missing link. You must also find the opus.dll (or the equivalent library file) generated in your build_opus-build folder and use it to overwrite the one in the installer directory.

By using your locally compiled executable and your locally compiled Opus library, RADE should appear in the Windows 11 version just as it does on your Linux build. This confirms that the issue is simply that the installer is pulling the "wrong" version of the Opus dependency.

What did you expect?

RADE on Windows 11 using official AetherSDR - Claude installation package.

Steps to reproduce

1. Install AetherSDR with AetherSDR-v0.9.3-Windows-x64-setup.exe results in no RADE availabilty.
2. Compile from source, opus.lib compiled using source code and RADE is available.

AetherSDR version

0.9.3

Radio model & firmware

Flex 6600 FW 4.2.18

Operating system

Windows

OS version and hardware

Windows 11 24h2