DABcast is a Node.js web application that orchestrates the full ODR-mmbTools process chain to produce and broadcast a DAB+ digital radio multiplex. It is designed to run on a dedicated Linux server or a Raspberry Pi 4/5, and is accessed from any browser on the local network.
| Feature | Description |
|---|---|
| Full ODR integration | Manages odr-audioenc, odr-padenc, odr-dabmux and odr-dabmod in a coordinated process chain. |
| Audio-based failover | Detects stream failures via audio probing (not just HTTP checks). Automatically switches to a backup stream and returns to main when audio is restored. |
| Mux input monitoring | Reads the input buffer statistics of odr-dabmux (underruns, overruns, silence, no data) for every service while ON AIR, revealing dropouts even when the encoder process is still running. |
| Telegram notifications | Forwards logs and critical broadcast alerts to a Telegram bot, with configurable severity, silent delivery and a built-in connection test — and, optionally, a RESOLVED message when a transmitter or a service is back on air. |
| Live metadata — DLS, DL+ & SLS | Now Playing text, DL+ tags and album art in real time, from the stream (ICY), a JSON API (Server-Sent Events feeds included) or manual text. Covers alternate with the station logo; the logo comes back on its own when a track is over (ads). |
| Web player | Listen to any service in the browser, decoded from the multiplex output itself, with level meters, DLS, DL+ and the slides on air. |
| Audio levels assistant | Measures every service over 5 to 30 minutes, flags encoder clipping and suggests a gain that keeps 3 dB of headroom for AAC. |
| Guided service setup | Stream URL test with the current title, automatic detection of JSON API keys, live hints on PI, PS8 / PS16 and multiplex capacity. |
| Raspberry Pi ready | Runs on amd64 servers and Raspberry Pi 4/5 (arm64). Ships as a self-contained .deb package — no separate Node.js installation required. |
| Browser-based UI | Clean dark-themed interface accessible from any device on your local network. No desktop environment required on the broadcast server. |
| Integrated secure sign-in | DABcast sign-in page, signed private sessions, login rate limiting and automatic invalidation after credential changes. Account, password and web port in the ⚙ Settings window; command-line reset for lost credentials. |
| Preset management | Save and restore complete multiplex configurations as JSON presets. Import/export individual services or full configurations. |
| Transmitter outputs | One or several transmitters at once, each added as an output: EasyDAB V2 (ZMQ), commercial modulators (EDI/UDP), converters and remote sites (EDI/TCP), raw ETI, and an SDR plugged into the server (HackRF, LimeSDR, BladeRF, PlutoSDR… through SoapySDR) — with their connection state, an alert when a transmitter goes away and an automatic restart of the local SDR. |
DABcast manages the following ODR-mmbTools process chain:
odr-audioenc × N ──ZMQ──► odr-dabmux ──EDI──► [odr-dabmod ──SoapySDR──► SDR] odr-padenc × N ──FIFO──► odr-audioenc └──► EasyDAB, modulators, converters…
Each radio service (programme) runs its own odr-audioenc and odr-padenc
instance. All audio streams are fed into a single odr-dabmux instance. With an SDR output,
odr-dabmod generates the RF signal and drives the SDR itself through SoapySDR (a HackRF output
saved by an earlier version still uses hackrf_transfer until it is saved again).
install-tools.sh
script installs them, then DABcast, in one go (see below).
The script installs DABcast itself as well: there is no package to download
separately. It ends with the latest DABcast release for the machine (amd64 or arm64), started as a
service, ready at http://<server-ip>:9090. Before that, it installs everything DABcast can use:
the ODR-mmbTools (odr-audioenc, odr-padenc, odr-dabmux,
odr-dabmod), dablin and ffmpeg (web Player), ImageMagick (slides),
the build tools, sudo (one-click updates) and a time synchronisation if none is running.
Only three questions are asked, each with a default (Yes, just press Enter):
wget https://dabodr.github.io/DABcast-diffusion-software/download/install-tools.sh sudo bash install-tools.sh
non-free component is enabled automatically (odr-audioenc uses fdk-aac).plugdev (SDR) and audio groups; DABcast runs as this user.--yes answers every question with its default (unattended installation).To install the DABcast package yourself: the tools only with --tools-only (DABcast is then not installed), then the package of your machine:
sudo bash install-tools.sh --tools-only # PC / server (amd64) sudo dpkg -i dabcast_1.10.11_amd64.deb # Raspberry Pi (arm64) sudo dpkg -i dabcast_1.10.11_arm64.deb
The packages are on the latest release page.
The service is enabled and started by the package (sudo systemctl status dabcast to check).
Open a browser on any device on the same local network:
http://<server-ip>:9090
DABcast displays its own secure sign-in page. The default login is
admin / dabcast. Change the password immediately
on first login — the interface will prompt you to do so. You can keep a trusted device
signed in, and use the ⚙ Settings button (top bar) to change the credentials
or the web port, or to sign out.
hostname -I on the server to get its IP address.
Example: http://192.168.1.50:9090
Click Multiplex in the top bar to configure your multiplex:
F401); its first digit is the country code (with the ECC) — a ⚠ hint shows when it is 0 or differs from the first digit of the services' PI codesClick + Add service (or double-click a row / Edit to change one). The dialog has three tabs:
| Tab | Fields |
|---|---|
| General | Identity: PI (unique 4-digit hex, e.g. F9A3), PS8 (short name, 8 chars), PS16 (long name, 16 chars), language, PTY (genre). Live hints flag an invalid or duplicate PI and a PS8 whose letters are not in the PS16.DAB coding: bitrate, codec (HE-AAC v1 / v2 / AAC-LC), protection EEP-A 1–4, sample rate, channels, PAD size. The capacity used by the whole multiplex (CU) is shown live. |
| Audio source | Input mode: GStreamer (recommended, HTTPS), VLC, or ZMQ / EDI direct (an external encoder sends DAB+ audio). Main and backup stream URLs, each with a Test button (answer, format, current title), audio gain, and the failover settings. |
| Metadata | Where the titles come from (stream ICY, JSON API, manual text), the default text, DL+, the station logo and slides. See Metadata & slides. |
Click the Start button on the dashboard. DABcast will:
odr-audioenc + odr-padenc per enabled serviceodr-dabmux with the generated .mux configodr-dabmod (it drives the SDR through SoapySDR; plus hackrf_transfer for a HackRF output saved by a former version)| Dot colour | Badge | Meaning |
|---|---|---|
| Green | RUNNING | Service is live on the active stream |
| Orange | WARNING | Running on backup stream, or backup is unstable |
| Red | ERROR / CRASH | Encoder crashed, attempting restart |
| Grey | STOPPED | Service is stopped or mux is not running |
While ON AIR, a second tag next to the status badge shows how odr-dabmux receives
each service's audio. DABcast reads it every 5 seconds from the dabmux management port
(read-only, no action is taken). Hover a tag for details; the full list is in the Sys. info dialog.
| Tag | Meaning | What to do |
|---|---|---|
| STARTING | Just after Start: buffers are filling up and start-up underruns are normal. Ends on its own once the radio has had no new underrun for 5 seconds (usually about 15 s after Start, at most 1 minute). No warning or alarm is raised during this phase. | Nothing |
| BUFFER OK | Audio arrives regularly, no buffer incident in the last 30 seconds. Shown even while dabmux itself still reports Unstable for old glitches (e.g. the buffer filling up right after Start) — the tooltip says so. | Nothing |
| UNSTABLE ▲ | Underruns increased during the last 30 seconds: the buffer ran empty and listeners may hear dropouts (▲ = increase since the previous reading) | Check the source stream, network and encoder of that service |
| SILENCE | Data arrives but the audio is (almost) silent | Check the source programme |
| NO DATA | Nothing arrives from the encoder | Check the encoder and its logs |
The Mux inputs card sums these tags; SILENCE and NO DATA inputs are added to the Alarms card.
The Multiplex dialog lists the transmitter outputs: add one output per transmitter (EasyDAB V2, commercial modulator, converter, remote site, SDR plugged into this server). They all carry the same multiplex, at the same time.
Configurations made with a former version (TX mode EASYDAB, EDI or HackRF) are shown as the equivalent output when the dialog opens — same address, port and settings — and only saved that way when you press Save: an updated server keeps broadcasting exactly as before. A raw ETI copy (port 9901) is always kept for the Player and Dablin.
Add one output per transmitter with the menu and + Add. All outputs carry exactly the same multiplex; each one has its own name and ON/OFF switch.
| Output | Who connects | What to set on the transmitter |
|---|---|---|
| ZMQ — EasyDAB V2 | The EasyDAB V2 connects to DABcast | Mux address = this server, port of the output (18081 by default). Optional send timestamps (metadata): DABcast adds the transmission time of each frame and suggests a TIST offset of 2 s (needs Internet access at start-up for the leap-second list). Off by default: the EasyDAB V2 works with or without it. Only one ZMQ output can send timestamps. |
| EDI/UDP — commercial modulator | DABcast sends to the modulator | EDI input in UDP, on the port of the output; enter the modulator's IP address in DABcast. PFT / FEC is turned on. |
| EDI/UDP multicast | DABcast sends to a group | Several transmitters join the multicast group (e.g. 239.20.10.1) on the same network; set the TTL for routed networks |
| EDI/TCP | The transmitter, a converter or a remote odr-dabmod connects to DABcast | EDI source = this server, port of the output (13000 by default) |
| ETI/TCP | The receiver connects to DABcast | Raw ETI over TCP, for equipment that reads ETI |
| SDR — HackRF, LimeSDR, BladeRF, PlutoSDR… | odr-dabmod on this server (internal EDI port) | An SDR plugged into the DABcast server, driven by odr-dabmod through SoapySDR (see SDR output below). Only one SDR output. |
Two outputs cannot listen on the same port, and the ports already used by DABcast (service inputs, ETI copy, dabmux control ports, web interface) are refused when you save. ON AIR, an invalid change is refused before the multiplex is stopped.
odr-dabmod modulates the multiplex and drives the SDR itself through SoapySDR (one process, no hackrf_transfer). Choose the Device: its starting values are filled in and can be changed.
| Device | TX gain | Master clock | Notes |
|---|---|---|---|
| HackRF (tested) | 61 = VGA 47 + 14 dB amplifier (0–61) | 0 | Bandwidth 1.75 MHz; same level as the former HackRF output with TX gain 47 |
| LimeSDR (not tested) | 40 | 32768000 | Module soapysdr0.8-module-lms7 |
| BladeRF (not tested) | 20 | 0 | Module soapysdr0.8-module-bladerf |
| PlutoSDR (not tested) | 40 | 0 | Module SoapyPlutoSDR. A stock PlutoSDR does not go below 325 MHz: Band III (174–240 MHz) needs the well-known AD9364 modification |
| Other (SoapySDR args) | 20 | 0 | Any SoapySDR device, e.g. driver=uhd,type=b200 |
serial=… to pick one device among several. TX antenna and Bandwidth (0 = automatic) are passed as they are.SoapySDRUtil --find (never transmits). The device needs its SoapySDR module: SoapySDRUtil --info lists the installed ones.hackrf_transfer chain) is shown as the SDR HackRF (TX gain + 14) and saved that way at the next Save; ON AIR the restart banner shows, the new chain is applied by the restart.While the multiplex is ON AIR, each output of the Multiplex dialog shows who is connected, refreshed every 5 seconds: "1 connected: 192.168.1.85" (green), "no transmitter connected" (orange), or "sending to …" for EDI/UDP (UDP has no connection: DABcast cannot tell whether the transmitter receives). A connected transmitter is not a proof that it is on air (its amplifier may be off), but a disconnection is seen at once.
odr-dabmux has one value of each for the whole multiplex: the fields are shown in the blocks of the outputs that use them and stay in sync. A different delay per site is set on the site itself (transmitter or converter, below).
Over the Internet or a long link, send EDI over TCP (reliable) to a small Linux machine next to the transmitter, which delivers it locally and buffers it. The digris-edi-zmq-bridge tools (GPL v3, developed for Opendigitalradio) do this.
sudo apt install build-essential automake libtool libzmq3-dev git git clone https://github.com/digris/digris-edi-zmq-bridge.git cd digris-edi-zmq-bridge ./bootstrap.sh && ./configure && make && sudo make install
# EDI/UDP to the local modulator 192.168.10.20, port 12000, FEC 2,
# each frame delivered 1 s before its timestamp
digris-edi-tcp-converter -c <dabcast-address>:13000 -w -1000 \
-d 192.168.10.20 -p 12000 -f 2 -C "chronyc waitsync 2 0.01"
# or ZMQ for an EasyDAB on the site (it connects to this machine, port 18081)
digris-edi-tcp-converter -c <dabcast-address>:13000 -w -1000 -z *:18081Several sites can each run a converter connected to the same EDI/TCP output (or each to its own output). Run the converter under a process supervisor (e.g. a systemd service) so that it restarts automatically.
A machine with an SDR board on the site can run odr-dabmod fed by an EDI/TCP output of DABcast. Main settings of its configuration file:
[input] transport=edi source=tcp://<dabcast-address>:13000 [output] output=soapysdr [soapyoutput] device=driver=hackrf master_clock_rate=0 ; HackRF: no settable clock channel=5A txgain=40
Start from the complete example.ini of ODR-DabMod and validate the RF settings (gain, filter, channel) on the real hardware.
Each service sends a text (DLS), optional DL+ tags (artist / title) and pictures (SLS slides). Everything is set in the Metadata tab of the service dialog; the panel On air now on the right shows, live, the slide, the DLS and the DL+ tags really sent, with the reason of the last update.
| Source | Use |
|---|---|
| Stream (ICY) | The title sent inside the audio stream (Icecast / Shoutcast). Nothing else to set. |
| JSON API | A now-playing address of the station (JSON, or a Server-Sent Events feed). Gives artist, title and usually the track cover. |
| Manual text | A fixed text (the default DLS). |
The green Validate button saves the metadata settings only, keeps the dialog open and restarts nothing (even ON AIR): the result appears in On air now within a few seconds.
Keys use dots for nested fields and numbers for lists (now_playing.song.title, data.0.artist); a|b means "b if a is empty".
Click Player in the top bar, choose a service and press play. The audio is decoded from the multiplex output itself (the same signal as the receivers), with left / right level meters, the DLS, the DL+ tags and the slides with their size. Two listeners at most. It requires dablin and ffmpeg on the server (installed by install-tools.sh).
Click Levels (or the Mux inputs card) while ON AIR. DABcast measures the peaks of every service while this window is open and suggests a gain:
| Setting / column | Meaning |
|---|---|
| Target typical peak | Where the usual peaks should be (−6 dBFS by default). |
| Analysis window | 5, 15 or 30 minutes. 15–30 minutes (songs, ads and jingles) gives a more reliable suggestion. |
| Max | Highest peak, in red above −3 dBFS: AAC encoding raises the decoded peaks by 1–3 dB, so higher peaks can crackle in receivers. |
| CLIP ×N | The encoder saturated N times: a cut of at least 2 dB is suggested. |
Apply (or Apply all) saves the gain and restarts only that service's encoder (2–3 s gap on that service; the multiplex keeps running). An isolated peak does not make a quiet station quieter.
DABcast uses an audio-based watchdog to detect stream failures.
Rather than simply checking HTTP connectivity, it starts a lightweight probe encoder
(odr-audioenc -s 15) against the main stream URL. If the encoder crashes
or detects silence within 15 seconds, the stream is considered failed.
| Parameter | Value | Description |
|---|---|---|
| Watchdog interval | 5 seconds | How often the watchdog checks each service |
| Crash threshold | 1 crash | Number of crashes before switching to backup |
| Probe silence timeout | 15 seconds | Time for audio probe to detect silence |
| Stable window | 30 seconds | Uptime needed to reset crash counter |
The whole configuration (multiplex settings and services) can be saved and restored with the
Import / Export menu: Export config / Import config (JSON),
Export selected service / Import service (.dct with its logo), and
Export all services (.zip), named all-services-<multiplex name>.zip.
The active configuration is stored as /var/lib/dabcast/presets/demo.json.
Tick Start multiplex at startup in the Multiplex dialog. DABcast will automatically restart the multiplex 2 seconds after the web server starts — ideal for unattended broadcast servers. The systemd service is configured to start on boot by default.
The round ⚙ button of the top bar opens the Settings window:
PORT= line in /etc/default/dabcast takes precedence and locks the field.The Telegram button forwards log lines to a Telegram bot (your phone, a group):
https://api.telegram.org/bot<token>/getUpdates and read chat.id (-100… for a group)./var/lib/dabcast/.telegram.json (readable by DABcast only) and is never shown again nor exported; a Telegram failure never affects the logs or the broadcast.The Logs button shows the DABcast log, refreshed every 3 seconds. It opens on the latest lines and follows the new ones; scroll up to read, it stays there (back at the bottom: it follows again).
sudo systemctl status dabcastsudo ufw allow 9090sudo grep -m1 '"port"' /var/lib/dabcast/settings.jsonsudo journalctl -u dabcast -n 50curl -I <url>lsusb) or missing SoapySDR module (SoapySDRUtil --info)odr-audioenc is listed as RUNNING in the process listss -tlnp | grep 900managementport is disabled (0) or not reachable on localhostodr-padenc is running (shown in the process list)sudo /opt/dabcast/bin/dabcast --reset-password sudo systemctl restart dabcast
The password becomes dabcast (username kept) and a new one is required at the next sign-in. Add a username after --reset-password to change it too.
Report a bug or ask a question on the GitHub Issues page. Attach the relevant lines of /var/lib/dabcast/logs/dabweb.log (remove any private URL or token first).
# Live log output sudo journalctl -u dabcast -f # DABcast internal logs (Logs button in the web UI) sudo tail -f /var/lib/dabcast/logs/dabweb.log
sudo -u dabcast env DABCAST_DATA_DIR=/var/lib/dabcast /opt/dabcast/bin/dabcast
sudo dpkg -r dabcast
sudo dpkg --purge dabcast sudo rm -rf /var/lib/dabcast
Run the included uninstall-tools.sh script (available in the DABcast source repository).