Monthly Archives: June 2026

David May 2026, V2 C Port, V2 Stored file test campaign

This month I spent some time planning, investigating, and moving project wide files from individually owned accounts to project wide resources. This is part of the process of ensuring the FreeDV project is not tied to any one individual. We’ve done a lot of work since the ARDC grant started 3 years ago so there are quite a few digital artifacts (as well as the code).

Work started on a C port of RADE V2 using Claude code. The technique of using AI to assist C ports is getting commonplace now! This only took about a days effort, in particular as the classical DSP C code required for of RADE V2 is much simpler than V1. I put some thought into suitable automated tests to validate the port and have good results when testing against the reference Python code. There is still some work to do to ensure the V2 algorithms are well tested before we distribute a C library version. I will complete the C port after the stored file test campaign is successfully completed.

Most of the work this month was around planning and coordinating the RADE V2 stored file test campaign. The goals of this campaign are to gather stored file OTA samples to support the initial test results, but from a wider range of speakers, HF channels, and radio hardware. I set up a web based processing system so the test team can encode and decode their own RADE V2 samples, and worked with the test team to coordinate and guide the tests. So far the OTA results are consistent with the simulation results which is a fine result.

Thank you very much to Rick W7YC, Kanda JH0PCF, Yuichi JH0VEQ and Take JS1MAV for your samples. Take has also been contributing PAPR measurements.

Finally, I have started work on a RADE V2 paper. There are a lot of novel concepts in RADE V2, which need documenting at the professional and Ham level.

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