Using Thetis with FreeDV
Posted: Fri Sep 05, 2025 2:01 am
Hi All,
The latest version of FreeDV has a new digital voice vocoder (RADEV1) which is now rivalling SSB for weak signal performance (-2 dB) providing virtually noise-free, 8 kHz audio bandwidth in a 1.65 kHz RF channel (using 33 x 50 Hz carriers).
By all accounts this digital HF setup works well on conventional transceivers with a sound-card (including IC-7300 SDR types with internal sound-cards etc) but it is reported, and I can confirm, that it does not work well using various SDRs together with Thetis, as follows:
Transmitting the FreeDV waveform using Thetis works fine and is well received by everyone, but receiving presents frequent SNR dropouts and bad decodes (sounding like gibberish) even on strong received signals. This is particularly prevalent during periods of fast, frequency-selective, ionospheric fading, probably caused by multipath propagation. Others, however, do not experience this problem during the same band conditions and signal strength. Then, at other times, the reception using Thetis is perfect.
My setup is: Apache Labs ANAN 200D - Ethernet cable - Intel i7 NUC PC - Windows 11 - Thetis 2.10.3.11 - VB Audio Cable using MME - FreeDV. The PC is running at 10% CPU. There are no VAC overflows or underflows. This setup works fine with WSJT-X and FLDIGI.
I have tried: Adjusting RX audio levels displayed on freeDV (low, mid, high) using Thetis AF and AGC gain controls. Adjusting: Thetis RX filter bandwidth; noise reduction settings; fast, slow and long AGC; 0 to 50 dB attenuation; Network Throttle Tweak, ANAN 200D Dither and Random options enabled/disabled; Filter low latency/linear phase; one and two VB cables; various VB cable gains, data rates, buffer sizes and mono/stereo select; all to no avail.
It appears that the main difference between the reported working and non-working systems is the use of Ethernet, Thetis and VAC. As general usage of this new digital mode is hotting up, I expect this may become a more significant problem. Can anyone provide an explanation, work-around or solution?
73, Joe VK3SRC
The latest version of FreeDV has a new digital voice vocoder (RADEV1) which is now rivalling SSB for weak signal performance (-2 dB) providing virtually noise-free, 8 kHz audio bandwidth in a 1.65 kHz RF channel (using 33 x 50 Hz carriers).
By all accounts this digital HF setup works well on conventional transceivers with a sound-card (including IC-7300 SDR types with internal sound-cards etc) but it is reported, and I can confirm, that it does not work well using various SDRs together with Thetis, as follows:
Transmitting the FreeDV waveform using Thetis works fine and is well received by everyone, but receiving presents frequent SNR dropouts and bad decodes (sounding like gibberish) even on strong received signals. This is particularly prevalent during periods of fast, frequency-selective, ionospheric fading, probably caused by multipath propagation. Others, however, do not experience this problem during the same band conditions and signal strength. Then, at other times, the reception using Thetis is perfect.
My setup is: Apache Labs ANAN 200D - Ethernet cable - Intel i7 NUC PC - Windows 11 - Thetis 2.10.3.11 - VB Audio Cable using MME - FreeDV. The PC is running at 10% CPU. There are no VAC overflows or underflows. This setup works fine with WSJT-X and FLDIGI.
I have tried: Adjusting RX audio levels displayed on freeDV (low, mid, high) using Thetis AF and AGC gain controls. Adjusting: Thetis RX filter bandwidth; noise reduction settings; fast, slow and long AGC; 0 to 50 dB attenuation; Network Throttle Tweak, ANAN 200D Dither and Random options enabled/disabled; Filter low latency/linear phase; one and two VB cables; various VB cable gains, data rates, buffer sizes and mono/stereo select; all to no avail.
It appears that the main difference between the reported working and non-working systems is the use of Ethernet, Thetis and VAC. As general usage of this new digital mode is hotting up, I expect this may become a more significant problem. Can anyone provide an explanation, work-around or solution?
73, Joe VK3SRC