Hey @gkkpch,
Assuming that you are referring to the T802 Farzi, this is MCX to SMA female:
Kind Regards,
Hey @gkkpch,
Assuming that you are referring to the T802 Farzi, this is MCX to SMA female:
Kind Regards,
I nicked the plug form this one ![]()
Dear Volumionauts,
Version 1.1.0 replaces mainstream distribution binaries with our own custom-compiled fn-* binaries, bringing full RTL-SDR Blog V4 dongle support and faster installation.
What’s New
Custom fn- Binary Suite*
RTL-SDR Blog V4 Support
Installation Speed
Kind Regards,
Dear Volumionauts,
Version 1.2.0 introduces RDS support for FM stations. Your FM radio now displays live broadcast metadata.
What’s New
RDS Metadata Display
Signal Quality Handling
Display Priority
Technical Implementation
Bug Fixes
Note: RDS quality depends on signal strength.
Kind Regards,
Still need to install manually?
Hey @Gelo5,
Plugin is available in Music Services category:
You can install manually or using store, plenty of choices.
Kind Regards,
Ohh, thank you @nerd - I’m old and blind
Wel done @nerd
A little shocked and really confused, that the template master turns out to be blind…
Dear Volumionauts,
Behind the Scenes: Custom Binary Infrastructure
For those interested in the engineering effort behind versions 1.1.0 and 1.2.0, here’s an overview of the build infrastructure I’ve created.
The Challenge
RTL-SDR plugins traditionally require users to compile binaries on-device. On a Raspberry Pi Zero, this means 20-30 minutes of waiting, potential build failures, and dependency headaches. Additionally, the standard Debian rtl-sdr package is stuck at version 0.6 - significantly outdated compared to current development.
The Solution
I’ve built a Docker-based cross-compilation system producing ready-to-install binaries based on rtl-sdr 2.0.2 - bringing years of upstream improvements to Volumio users.
Version Comparison
| Source | Version | V4 Dongle Support | Tuner Precision Fixes |
|---|---|---|---|
| Debian packages | 0.6 | No | No |
| Our custom build | 2.0.2 | Yes | Yes |
Build Repositories
| Repository | Purpose | Source |
|---|---|---|
| rtlsdr-osmocom | RTL-SDR libraries (2.0.2) | Osmocom upstream |
| rtlsdr-blog | Alternative RTL-SDR libraries | RTL-SDR Blog fork |
| dab-cmdline | DAB/DAB+ decoder (fn-dab, fn-dab-scanner) | Jan van Katwijk, heavily modified |
| redsea-builds | RDS decoder (fn-redsea) | Oona Raisanen |
Why Osmocom Over RTL-SDR Blog Fork?
Both repositories now support V4 dongles (osmocom merged V4 support October 2023). We evaluated both for FM/DAB use:
| RTL-SDR Blog Extras | Relevant to FM/DAB? |
|---|---|
| VCO PLL current fix (stability above 1.5 GHz) | No - L-band only |
| Auto-direct sampling for HF below 24 MHz | No - FM/DAB above 87 MHz |
| Bias tee via offset tuning toggle | No - convenience feature |
| Force bias tee EEPROM hack | No - convenience feature |
| L-band VGA gain tweaks | No - L-band only |
| Osmocom 2.0.2 Improvements | Relevant to FM/DAB? |
|---|---|
| r82xx: improved tuner precision | Yes |
| r82xx: avoid redundant register writes | Yes - faster tuning |
| r82xx: batch register writes | Yes - faster tuning |
| Round gain input to nearest value | Yes |
Key Finding
The rtl_fm tool is identical in both repositories. Neither claims better FM demodulation, DAB reception, or audio quality. For broadcast bands (FM 88-108 MHz, DAB 174-240 MHz) there is no functional difference.
Decision: Osmocom
| Reason | Explanation |
|---|---|
| Upstream canonical source | Community standard, wider testing |
| Recent tuner improvements | 2024 precision and speed fixes |
| Cleaner codebase | No vendor-specific additions we don’t need |
| Full V4 support | Same as blog fork since October 2023 |
The blog fork’s extras target HF reception (direct sampling), L-band satellite work (VCO PLL, gain tweaks), and bias tee convenience - none of which affect FM or DAB reception quality.
Architecture Support
| Architecture | Device Examples | Binary Prefix |
|---|---|---|
| armv6 (arm) | Pi Zero, Pi Zero W, Pi 1 | fn-* |
| armv7 (armhf) | Pi 2, Pi 3 (32-bit) | fn-* |
| arm64 (aarch64) | Pi 3/4/5 (64-bit) | fn-* |
| x64 (amd64) | x86 systems, VMs | fn-* |
Why Custom Prefixes?
| Decision | Rationale |
|---|---|
| fn-rtl_fm instead of rtl_fm | Avoids conflicts with Debian rtl-sdr package |
| fn-dab instead of dab-cmdline | Clear identification of our optimized builds |
| fn-redsea instead of redsea | Plugin can verify correct binary is installed |
| libfn-rtlsdr instead of librtlsdr | Coexists with system libraries |
Result
All repositories are open source. Contributions and issue reports welcome.
Kind Regards,
Dear Volumionauts,
Cheap RTL-SDR dongles can now work with DAB radio. Add PPM correction in settings (try values 40-60).
Since initial version of this plugin, I have been chasing a frustrating ghost. The cheap blue RTL-SDR dongles - you know the ones, the generic USB sticks that flood online marketplaces for under $10 - would work perfectly for FM radio but completely fail on DAB.
The maddening part? They work on Windows.
This led to weeks of investigation, reverse engineering, and increasingly desperate hypotheses. I examined Windows driver behavior, analysed USB traffic, studied the RTL2832U datasheet, and dug deep into the R820T tuner specifications. I tried everything:
Nothing worked. The blue dongles stubbornly refused to decode DAB, while quality dongles from Nooelec and RTL-SDR Blog worked perfectly with identical code.
After extensive analysis comparing Windows driver behaviour with our Linux implementation, I finally identified the culprit: the crystal oscillator.
The cheap blue dongles use the absolute lowest-cost components available. The crystal oscillator - the component that sets the reference frequency for the entire device - has terrible accuracy. Where a quality dongle might be accurate to within 1-2 PPM (parts per million), these budget units can be off by 50 PPM or more.
At DAB Band III frequencies (around 220 MHz), a 50 PPM error translates to approximately 11 kHz of frequency offset.
For FM radio, this is irrelevant - FM is designed to be robust against frequency drift, which is why your cheap dongle works fine for FM.
But DAB uses OFDM (Orthogonal Frequency-Division Multiplexing), a technology that requires precise frequency alignment. An 11 kHz error completely destroys the orthogonality between subcarriers, turning your DAB signal into noise. The decoder cannot even begin to synchronise.
The Windows drivers include automatic frequency calibration routines that measure and compensate for crystal offset. This happens silently in the background - the user never knows their dongle is defective.
On Linux, the rtl-sdr library exposes this as a manual PPM correction parameter, but most software either ignores it or sets it to zero. Without proper calibration, cheap dongles simply cannot receive DAB.
Version 1.2.1 adds a PPM Correction setting for DAB reception.
Each dongle has its own specific PPM value due to manufacturing variance. You may need to experiment to find the exact value for your hardware. The tolerance is narrow - being off by even 10 PPM can mean the difference between perfect reception and complete failure.
PPM (Parts Per Million) measures frequency accuracy. A crystal rated at 28.8 MHz with 50 PPM error could actually oscillate at anywhere from 28.7986 MHz to 28.8014 MHz.
This error propagates through the tuner. When you tune to 225.648 MHz (DAB channel 12B), your dongle might actually be receiving 225.637 MHz or 225.659 MHz - completely missing the signal.
The “PLL not locked!” warning message from R820T tuners sent me down the wrong path. I assumed this warning indicated a fundamental hardware limitation at the 2.048 MHz sample rate required for DAB.
After extensive testing, I discovered this warning is cosmetic - the tuner works correctly despite the message. The real problem was frequency offset, not sample rate compatibility.
I even implemented professional-grade audio resampling using the libsamplerate library, attempting to run the tuner at a higher sample rate and downsample to DAB rate. This approach, while technically elegant, actually made things worse by introducing timing jitter that further degraded OFDM synchronisation.
Sometimes the simplest explanation is correct: cheap parts produce cheap results.
The lesson here is one that RF engineers have known for decades: frequency accuracy matters. DAB was designed for professional broadcast equipment with high-precision oscillators, not $8 USB dongles with components sourced from the lowest bidder.
That said, with proper PPM correction, even budget hardware can achieve acceptable DAB reception. Version from 1.2.1 makes this possible without requiring users to understand the underlying RF theory - just adjust the slider until it works.
For reliable, frustration-free operation, I still recommend investing in a quality dongle from Nooelec or RTL-SDR Blog. The additional cost (typically $25-35 vs $8-10) buys you a TCXO crystal, better filtering, and components that actually meet their specifications.
But if you already own a drawer full of cheap blue dongles, they are no longer paperIights. Welcome to DAB radio.
This investigation consumed considerable development time across multiple plugin versions. I examined USB protocol traces, studied Windows driver internals, analysed RF theory, implemented and discarded multiple workarounds, and performed extensive testing across different hardware configurations.
The RTL-SDR community documentation, particularly the work by the osmocom and rtl-sdr-blog teams, provided invaluable reference material. The dab-cmdline project by Jan van Katwijk forms the foundation of our DAB implementation.
Special recognition goes to the users who reported issues and provided test data from their own hardware. Without real-world failure reports, I would never have identified the pattern that led to this solution.
RTL-SDR Radio Plugin v1.2.1
“Making cheap hardware work since 2025”
Kind Regards,
May I ask, if price is not a factor, which one is the better choice?
– RTL-SDR Blog V3
– RTL-SDR Blog V4
– NooElec NESDR SMArt XTR
Thank you !
Dear Volumionauts,
DAB Metadata Architecture Overhaul
Version 1.2.3 introduces a cleaner, more reliable DAB metadata system with proper support for broadcast-provided artwork.
What’s New
DL Plus (Dynamic Label Plus) Support
MOT Slideshow Support
Improved Display Layout
Reliable Text Handling
Artwork Priority
Regional Note
Testing shows UK commercial broadcasters (Bauer, Global) currently transmit basic DLS text only - no DL Plus tags or MOT slideshow. Users in Netherlands, Germany, and other regions with DL Plus/MOT support will see automatic artwork. UK users see raw DLS text with our DAB placeholder image.
This is a limitation of UK broadcast infrastructure, not the plugin. The architecture is ready when UK broadcasters adopt these features.
Kind Regards,
![]()
Hey @dewen
RTL-SDR Dongle Comparison for FM/DAB Radio Plugin
| Feature | RTL-SDR Blog V3 | RTL-SDR Blog V4 | NooElec NESDR SMArt XTR |
|---|---|---|---|
| Tuner Chip | R820T2 | R828D | R820T2 |
| FM Reception | Excellent | Excellent | Excellent |
| DAB Reception | Inconsistent | Excellent | Inconsistent |
| TCXO | Yes (1 PPM) | Yes (1 PPM) | Yes (0.5 PPM) |
| HF Support | Yes (direct sampling) | Yes (improved) | No |
| Driver Support | Standard | Requires custom libs | Standard |
| Price (approx) | $30 | $40 | $25 |
Detailed Analysis
RTL-SDR Blog V3
RTL-SDR Blog V4
NooElec NESDR SMArt XTR
Clear Winner: RTL-SDR Blog V4
Our testing revealed the R828D tuner in the V4 handles DAB’s OFDM modulation significantly better than R820T2-based dongles. The phase noise characteristics of R828D are better suited for DAB’s complex signal processing.
For FM-only use, all three perform equally well. For DAB or mixed FM/DAB use, the V4 is the clear choice.
Important: Plugin version 1.1.0 or later required for V4 support - earlier versions lack the custom libraries needed for V4 initialization.
Kind Regards,
Friday this boy will arrive.
Very curious if the reception will improve when using a powered antenna.
You’re moving way too fast, nerd
! I ordered the RTL-SDR Blog V3 from Amazon after your post on November 10th, and it only just arrived today… only to discover that RTL-SDR Blog V4
is now your top recommendation. Thankfully, Amazon’s return policy is excellent, so I’ve already swapped it out for the V4
.
Really looking forward to tinkering with it and adding even more enjoyment to my Pi + Volumio setup.
I just want to say—you’re doing an incredible job. The knowledge and skills you freely share with this community are genuinely inspiring. Thank you for all the patience, kindness, and support you show to everyone here.
Hear, hear !
( A very British way of saying bl**dy fantastic! )