Author Archives: k6aq

Mooneer’s FreeeDV Update – October 2026

This month was fairly busy in terms of FreeDV. Besides going to Pacificon and Zero Retries Digital Conference, a lot of work was done in terms of bugfixes and testing which ultimately resulted in a 2.4.1 bugfix release going out at the end of the month. Many of these bugfixes were part of an effort to improve automated testing in the upcoming FreeDV 3.0 release, much of that directed by Claude. In the process of writing tests, it discovered many bugs that would likely have taken quite a while to discover manually if at all.

In addition, because of this automated test effort, we now have automated unit and GUI tests. The latter in particular exercise as much of the user interface as possible thanks to a Python library and a TCP/IP link to the FreeDV application that it controls. This lets us have code coverage exceeding 90%, along with a way to make sure future changes do not break anything existing.

For RADE V2, some improvements with callsign decode were made that take advantage of the fact that the same callsign is repeatedly transmitted. This allows the callsign to be decoded far more often and at lower SNRs, meaning that your transmission is far more likely to be reported by others to FreeDV Reporter and elsewhere.

Finally, after 2.4.1 released, I began (with Claude’s help) to implement a small machine learning model that takes 8 kHz audio (most commonly with Bluetooth headsets that don’t fully support the mSBC codec) and effectively “fills in” the missing features for the RADE encoder. This allows the receiver to hear a transmission that has some of the higher audio frequencies added back in, improving clarity in this (admittedly limited) scenario. Some audio samples below:

Original audio:

Audio after RADE encode/decode:

Audio after downsampling to 8 kHz, going through new model and passing through RADE encode/decode:

Some adversarial training was also suggested and performed by Claude, which improved the results further. Examples from before and after such training:

This is currently split into two pull requests: freedv-backend for the actual ML model and freedv-gui to enable it when the mic device’s sample rate is low enough.

More information can be found in the commit history below:

(Note that all commit logs above were generated with the following command line:)

git log --author="member@email" --after "Month 1, 2026" --before "Month 31, 2026 23:59:59" --all

FreeDV 2.4.1 released

FreeDV 2.4.1 has been released, including audio and rig-control related fixes for bugs found since 2.4.0. Some of these fixes are to resolve random crashes that could result during normal operation when FreeDV attempts to perform multiple simultaneous operations (such as when simultaneously receiving and transmitting data from the FreeDV Reporter server). This release also contains improvements to user interface rendering performance, allowing FreeDV to more easily run on certain older machines. It can be downloaded using the following links:

More information about this release can be found on the GitHub release pages:

Recap: Pacificon/Zero Retries Digital Conference

This weekend Mooneer K6AQ attended both Pacificon and the Zero Retries Digital Conference in San Ramon, CA, where he gave two talks about FreeDV (one more technical than the other). The Pacificon talk’s slides can be found here (ZRDC’s can be found in their Proceedings or here).

As ZRDC was on the first day of Pacificon, the FreeDV booth couldn’t be set up until Saturday. Fortunately, this was able to be done before the vendor hall officially opened to the public:

During the rest of the weekend, Mooneer met with many FreeDV supporters and gave a well-received talk near the end of the weekend. That talk was also the first time RADEV2 was introduced (outside of blog posts on this website), which was received positively.

Anyway, see you next year!

FreeDV at Pacificon/Zero Retries Digital Conference

FreeDV will once again have a booth over at Pacificon in San Ramon, CA (in the Contra Costa Room) on October 16-18, 2026. Mooneer K6AQ will be there (as well as give talks at the Zero Retries Digital Conference and Pacificon itself), so come by and chat about FreeDV! More information at https://www.pacificon.org/ and https://www.zeroretries.org/p/conference.

NEW FOR 2026: The Pacificon special event station (W1AW/6) will have FreeDV installed on their 15 meter station. If you’ve ever wanted to make QSOs as (or with) W1AW using FreeDV, now’s your chance. FreeDV will be active at 2pm on Friday and Saturday of that weekend, and there may be at least one more time slot (TBD). Hope to hear you on the air!

Mooneer’s FreeDV Update – September 2026

This past month, I was finally able to verify the official reference FreeDV application (“freedv-gui”) with RADEV2. With this, we’re now able to begin testing of RADEV2 with volunteers running this version of the software. So far, there have been mainly minor issues with the application itself and not the performance of RADEV2, which is encouraging. However, it’s still fairly early in the testing process, so there is still time for issues to come up.

Additionally, with the help of Claude, I’ve been able to finally do some optimization of the FreeDV application that I haven’t had time to do perviously. For example, it was able to attain an over 50% improvement in CPU usage on macOS in rendering the various GUI plots and other UI elements. Smaller improvements were also made for Windows and Linux (when using Wayland directly instead of Xwayland).

As another example of what AI is able to do, I also pointed it at FreeDV’s audio pipeline and it was able to find some additional optimization opportunities there. For instance, libsamplerate (which is what we use for audio resampling) has traditionally used as much or even more CPU than RADE itself for transmit. Claude simply analyzed the code, suggested some fixes, ran benchmarks to confirm and as a result, libsamplerate no longer shows up as using significant CPU usage.

Next month we’ll be at Pacificon talking about the new things going on with FreeDV as well as continuing testing of RADEV2.

More information can be found in the commit history below:

(Note that all commit logs above were generated with the following command line:)

git log --author="member@email" --after "Month 1, 2026" --before "Month 31, 2026 23:59:59" --all

Mooneer’s FreeDV Update – August 2026

This past month, I focused mainly on getting version 2.4.0 released. This involved resolving remaining bugs, as well as enabling Profile Guided Optimization (PGO) on Windows and macOS to improve performance. Some bugs that were fixed include:

In addition, work on improving the behavior and usability of the Level meter for the upcoming version 3.0. This involved having the Level meter take audio directly from the microphone (previously, it was taken post-AGC) as well as having the meter use log scale instead of linear scale.

For the next month, work on integrating RADEV2 with FreeDV and tests will continue.

More information can be found in the commit history below:

(Note that all commit logs above were generated with the following command line:)

git log --author="member@email" --after "Month 1, 2026" --before "Month 31, 2026 23:59:59" --all

FreeDV 2.4.0 released

FreeDV 2.4.0 has been released, including bug fixes, reporting and Push To Talk handling improvements and the ability to automatically start decoding on startup. It can be downloaded using the following links:

Additionally, for those with a FlexRadio or web SDR, version 2.4.0 of the official integrations is available:

More information about this release can be found on the GitHub release pages:

Mooneer’s FreeDV Update – July 2026

This past month was a continuation of work required for the upcoming 3.0 release of FreeDV. During the first part of the month, I worked on user interface improvements, namely consolidating all configuration into one Settings window (similar to most other ham radio applications). The Easy Setup window was also removed and replaced with a Setup Wizard, which asks for much of the same information that Easy Setup did but in a hopefully easier to understand manner (along with being able to be used with more setups; a limitation of Easy Setup in the past was that many audio device configurations were relegated to the “advanced” setup workflow).

Besides user interface improvements and other feature enhancements (for example, adding a setting to automatically start decoding on application startup), much of the work done has been around integrating the new RADEV2 mode into FreeDV. This included discussions about how to verify proper behavior of applications integrating RADEV2 as well as performing the required updates at the code level to make it encode and decode.

For August, RADEV2 integration and testing work will continue. I am also beginning to give talks about FreeDV again after having taken a few months off.

More information can be found in the commit history below:

(Note that all commit logs above were generated with the following command line:)

git log --author="member@email" --after "Month 1, 2026" --before "Month 31, 2026 23:59:59" --all

Mooneer’s FreeDV Update – June 2026

During the month of June, I was focused mainly on fixing bugs and integrating previously approved feature requests:

One major bug that was resolved (or at least improved) was related to how users’ callsigns are transmitted. For RADE, there’s a packet that’s sent before transitioning from TX to RX; I had noticed during testing locally that this seemed to be cut off, preventing proper decode of the packet on the receive side. We had tried to avoid this in the past by calculating a delay based on CAT control responses, but this was apparently not sufficient. After experimentation, I changed this to a static delay and was able to consistently transmit this packet with my setup.

Additionally, there were bugs in the backend side that contributed to being unable to reliably decode callsigns. For example, there was a floating-point precision bug that interfered with LDPC decode at higher SNRs; fixing this dramatically improved decode performance in testing by others. We also removed the r8brain audio resampler and returned to using libsamplerate (which is what FreeDV was using prior to 2.3.0) due to varying RADE loss figures (more info here if interested).

On the FlexRadio integration, there were fixes to improve the behavior of the audio limiter (for microphone input). This allows users to use microphone audio levels such that peaks are closer to 0 dB; prior to this change, users had to set their microphone levels approximately 10 to 15 dB lower than they would have to otherwise for acceptable audio quality at the receive station.

During the last part of the month, I also began preparations for RADEV2 in the freedv-gui repository. I created a new branch called v3.0-dev to track FreeDV 3.0 development and merged several pull requests to remove the legacy FreeDV modes (700D/E and 1600) and switch our official convention over to being USB-only. I also began looking into further improvements to callsign decode, mainly using a lower rate LDPC code to allow decoding the callsign at a few dB lower signal level (currently, FreeDV needs around 2 dB SNR in order to reliably decode callsigns). This work will continue during July as well as other bugfixes and improvements.

More information can be found in the commit history below:

(Note that all commit logs above were generated with the following command line:)

git log --author="member@email" --after "Month 1, 2026" --before "Month 31, 2026 23:59:59" --all

Mooneer’s FreeDV Update – May 2026

This month two releases of FreeDV went out–2.3.0 followed by 2.3.1 a few weeks later. 2.3.1 had some audio quality and other fixes for issues discovered after 2.3.0’s release. In particular, the FreeDV integration on Flex had different audio than the FreeDV application for the same signals, not to mention some issues with Windows audio not reaching FreeDV on some user’s machines.

More importantly, however, is that the code shared between the Flex/KA9Q integrations and freedv-gui has been split out into its own repository, allowing those who want to integrate FreeDV into their own hardware or applications an easier path for doing so. In addition, the Flex and KA9Q integrations were branched off into their own repository, both so that those who want to include FreeDV have a simpler example to follow as well as to allow the integrations to follow a different release cadence from freedv-gui. This should hopefully allow more people to integrate FreeDV more quickly.

Besides bugfixes and the work to split the code into separate repos, a few other features managed to merge post-2.3.1 release:

More information can be found in the commit history below:

(Note that all commit logs above were generated with the following command line:)

git log --author="member@email" --after "Month 1, 2026" --before "Month 31, 2026 23:59:59" --all