Broadcast systems built by broadcast engineers.
Build the mux your modulator expects.
MuxTraffic takes the transport streams you already receive and builds the services you choose into one constant-bit-rate output for your modulator. One program on one Linux server, with its dashboard built in.
Every input is measured once a second. A backup source takes over when the first one fails, and hands back.
- Signed licence
- Signed updates
- Rolls back by itself
- Runs without root
All 10 are in the program you install today. The list is under 03 Licensing.
Your feeds in. Any mix of services. One constant rate to the modulator.
Pick services from many feeds, give them the numbers your network plan needs, and send one steady stream on. One program on one Linux server.
PAT, PMT and SDT are written, PCRs re-stamped, null packets hold the rate.
Manual 4.2 · The Mux for a modulator ›Set the service ID and every PID to match your network plan, or pass a whole stream through.
Manual 5.2 · Service id, PMT PID, PCR PID, ES PIDs ›A second source for an input. It takes over when the first fails or turns bad, and hands back.
Manual 6.1 · A backup source ›A tuner card in the server: DVB-S/S2, DVB-T/T2 or DVB-C, with the tuner signal on the dashboard.
Manual 3.10 · DVB tuner ›Seven steps for every channel.
UDP, RTP, HTTP, SRT or a tuner
The input’s PAT · PMT · SDT
The services you choose
Service ID · PMT PID · stream PIDs
Each PCR, as its packet leaves
Null packets hold the rate
UDP, RTP, SRT or an HTTP link
A relay skips steps 3–6: the whole input goes on as it arrives, with PIDs and names changed if you want. The picture and the sound are never decoded.
Your server calls us. We never connect in.
One licence per server, signed by us. A check-in is a short HTTPS call from your server; the answer says whether the licence is good. Nothing is pushed to your server, so your server has to be able to reach us.
Each key works only on the server it was made for.
A reboot or an hour of bad line costs nothing; 72 hours with no check-in stops the outputs.
One Ubuntu server and a way out to us.
| Part | Needed | Note |
|---|---|---|
| System | Ubuntu Server 22.04 LTS or 24.04 LTS · systemd | muxd runs as a systemd service |
| Processor | x86_64 | The installer stops on any other |
| Access | root, through sudo | For the install and the update; muxd itself runs without root |
| Streams | IPv4 · an IGMP querier for multicast | Without a querier a switch may stop a group after a few minutes |
| Dashboard | A management network | Plain HTTP on port 8080: keep it off the media network |
| Tuner card | Only if you receive RF | A card of the one supported family, with its driver installed |
| Internet | Outgoing HTTPS to us | For the install, the update and the check-in |
Everything you run on the server, in one terminal.
Check system a systemd service named muxd
Restart. Stops and starts it in one step. The outputs drop and come back — usually a second or two, depending on how much you have configured. Use it after changing something muxd only reads at startup.
Stop. Takes your outputs off air and leaves them off until you start it again. That is the whole difference from a restart. A reboot brings it back too, because the service is enabled. Nothing else does — there is no timer or watchdog that will start it for you.
Start. Brings it back after a stop. Inputs are re-joined and every enabled output begins again on its own — unless your licence has run out, or the outputs are stopped from this panel. Either way the dashboard says which, under Settings → Licence. There is nothing to re-enter.
Status. Says whether it is running, since when, and shows the last few log lines.
It does not mean you are on air — active (running) is a fact about the process, not about
packets leaving the machine.
The installer leaves muxd running as a systemd service named muxd, enabled, so it also comes back on
its own after a reboot. The three that change state need sudo; reading the status does not.
Is it actually transmitting? status cannot answer that — watch the output itself,
filling in your own interface and output address:
sudo timeout 3 tcpdump -ni <interface> host <output address> -c 20
Packets scrolling means the mux is transmitting.
For more than the last few lines of log:
journalctl -u muxd -n 50 --no-pager
Stop it through these commands rather than by killing the process by name: a pattern that matches
muxd tends to match more than you meant, up to and including the session you typed it in.
Uninstall system takes muxd off for good
for u in muxd-netapply.path muxd-netapply-revert.timer muxd-netapply.service muxd-netapply-revert.service; do sudo systemctl disable --now "$u" 2>/dev/null; done
sudo /usr/local/sbin/muxd-netapply revert --any 2>/dev/null
for u in muxd-update.path muxd-update.service muxd-clock-wait.service; do sudo systemctl disable --now "$u" 2>/dev/null; done
sudo systemctl disable --now muxd 2>/dev/null
sudo rm -f /etc/systemd/system/muxd.service
sudo rm -f /etc/systemd/system/muxd-update.path /etc/systemd/system/muxd-update.service /etc/systemd/system/muxd-clock-wait.service
sudo rm -f /etc/systemd/system/muxd-netapply.path /etc/systemd/system/muxd-netapply.service /etc/systemd/system/muxd-netapply-revert.timer /etc/systemd/system/muxd-netapply-revert.service /etc/sudoers.d/muxd-netapply
sudo rm -rf /etc/systemd/system/muxd.service.d
sudo systemctl daemon-reload
sudo systemctl reset-failed muxd.service muxd-update.service muxd-update.path muxd-clock-wait.service muxd-netapply.path muxd-netapply.service muxd-netapply-revert.service muxd-netapply-revert.timer 2>/dev/null
sudo rm -rf /usr/local/bin/muxd /usr/local/bin/muxd.prev /usr/local/sbin/muxd-self-update /usr/local/sbin/muxd-netapply
sudo rm -rf /var/lib/muxtraffic /var/lib/muxd-netapply /run/muxd-netapply
sudo find /root/backups -maxdepth 1 -type f \( -name 'config-preupdate-*.json' -o -name 'config-preupgrade*.json' \) -delete 2>/dev/null
sudo find /root -maxdepth 1 -type d -name '.muxd-selfupd.*' -exec rm -rf {} + 2>/dev/null
sudo rmdir /root/backups 2>/dev/null
sudo userdel muxtraffic 2>/dev/null
sudo groupdel muxtraffic 2>/dev/null
It runs at once, with no prompt, so be sure you are on the right server.
To take muxd off a server for good, run these on the server itself. They stop the service and delete what
the installer put there — the program, its systemd services (muxd, any drop-ins you added for it, its
self-update watcher, its wait for the clock at boot, and the Change IP service, if it was turned on), the muxtraffic account, the whole state directory and the configuration copies
kept before each update, including this server’s configuration and its licence file.
Nothing else on the machine is touched. They leave the DNS as it is: an /etc/resolv.conf
the installer wrote stays, with the old file it kept beside it. On a server with a tuner card
they also leave /etc/modprobe.d/muxd-dvb.conf, which keeps a tuner’s LNB powered.
Manual 1.8 lists what they remove and what they leave.
This does not free your licence on our side — tell us when you retire a server and we release its licence so you can use it on another.
- Open the dashboard at the address the installer printed. The installer also prints the user name and password to sign in with the first time.
- Change the password on the first sign-in.
- Activate your key — Settings → Licence → Activate. Sign in here to see each server’s key.
Release notes
The signed release notes the dashboard’s Update card shows.
The release notes appear here once a release is published.
Already running MuxTraffic? Your servers are one sign-in away.
Licences, check-ins and versions for every server.
The manual
One Java server. Every signal in, every format out.
Receive satellite, terrestrial, ASI, SDI and IP streams, change them on a graphics card or the CPU, and send them anywhere: your modulator, IPTV, phones or the web. All in our own Java code.
If one card fails or fills up, its channels move to the next one by themselves.
- Two-step sign-in
- HTTPS everywhere
- Encrypted streams
- Signed updates
All 41 are tested before each new version goes out, with a report.
From the dish, the cable or the network. Out to anywhere.
Signals come in through PCIe cards (tuners, ASI, SDI) or the network. One Java program does all the work and sends the new streams out. You control it from a browser.
MPEG-2 to AV2 for video, MP2 to MPEG-H for audio, SD to 4K, on a graphics card or the CPU.
Manual 1.2 · Where the work runs ›A channel can pass through untouched: no decode, no resize, no encode.
Manual 1.1 · The path of one channel ›From UDP inside the head end to SRT over the internet and HLS to phones.
Manual 4 · Which protocol ›Put a tuner, ASI or SDI card in, press Scan: the driver is installed and each port gets a line.
Manual 3 · Supported modules ›Seven steps for every channel.
Tuner, ASI, SDI or network
Find channels by SID
GPU or CPU
SD · HD · FHD · 4K
MPEG-2 → AV2
PAT · PMT · SDT · PCR
UDP, SRT, HLS, ASI and more
Copy skips steps 3–5 (decode, resize, encode): the channel passes through untouched and costs almost nothing.
Each server has its own key. It calls us; we never connect in.
As planned for the first release: the same licence line as every MoJ Ocean system. One key per server, a short HTTPS call from your server, nothing pushed in.
Each key is signed by us and works only on its own server.
A reboot or a bad line costs nothing; 72 hours with no check-in stops the outputs.
One Ubuntu server, sized for your channels.
| Part | Minimum | Recommended |
|---|---|---|
| System | Ubuntu 24.04 LTS | Ubuntu 24.04 LTS |
| CPU | 8 cores · AVX2 | 16+ cores · AVX-512 |
| Memory | 16 GB | 64 GB (for 4K) |
| Disk | 120 GB SSD | 500 GB NVMe (for HLS) |
| Network | 1 GbE | 2 × 10 GbE (in and out apart) |
| Graphics card | none · copy only | a supported graphics card |
| PCIe cards | only if you use them | tuners · ASI · SDI |
| Internet | outgoing HTTPS | outgoing HTTPS |
Minimum is enough to copy channels and a few HD transcodes. Recommended is for many channels and 4K.
Everything you run on the server, in one terminal.
sudo diving-source add
sudo apt update && sudo apt install diving-transcoder
sudo diving setup
The first line adds our signed package source, one time: only our signed packages install. Setup asks for the admin password and your licence key, makes the HTTPS certificate and scans the cards. Then open the address it prints.
sudo diving statusStatus. Service, version, licence days left, inputs and outputs, engine load.
sudo diving cardsCards. PCIe cards, drivers, each tuner’s lock and signal, ASI and SDI ports.
sudo diving update # backup, then update
sudo diving update --check # is there a new version?
sudo diving rollback # back to the one before
Most servers update from their own panel: Settings › Updates, now or tonight. If a step fails, the server goes back by itself.
sudo diving backup --out ~/diving-backup.dtbak
sudo apt purge diving-transcoder
sudo diving-source remove
Keep the backup first. You can restore it on any server later. The licence is freed for another server.
- Open the panel at the address setup printed, and sign in with the password you chose during setup.
- Turn on two-step for the admin user.
- Check the cards on the PCIe page, then add your first channel.
Release notes
In buildIn build, no releases yet. Each version will come with signed release notes, here and in the panel’s Settings › Updates.
Want it on your own head end first? Ask for early access.
No prices and no dates yet. Tell us what you receive and what you send out.
The manual
Customer sign-in
Sign in to see your licences and your servers.
Your servers
Open a row to see that server’s key and its controls. Keys start with MUX-….
Your account
- Account · Invoices
- Under your company name, top right.
- Sign out
- Signs out this browser only.
Your licences
| Server | Key | Plan | Time left | Renew |
|---|
Your invoices: open the invoice list.
Downloads
Server tools
RUN ON THE SERVERCheck or restart a serveris it running, its recent log, restart it
Run these on the server itself, over SSH or at the console.
Whether muxd is running and since when, with its last few log lines. It is a fact about the program, not proof of being on air — the dashboard shows what is actually leaving the machine.
Its last fifty log lines — the first thing we ask for when something is wrong.
Stops and starts it in one step. The outputs drop and come back, usually within a second or two. Nothing you have configured is lost.
Remove muxd from a servertakes it off for good
It runs at once with no prompt, so be sure you are on the right server.
Stops the service and deletes what the installer put there — the program,
its systemd services (muxd, any drop-ins you added for it, its self-update
watcher, its wait for the clock at boot, and the Change IP service, if it was turned on), the muxtraffic account, its state directory and
the configuration copies kept before each update, including that
server’s configuration and licence file. It leaves the DNS as it is: an
/etc/resolv.conf the installer wrote stays, with the old file it kept beside it. On a
server with a tuner card it also leaves /etc/modprobe.d/muxd-dvb.conf, which keeps a tuner’s
LNB powered.
for u in muxd-netapply.path muxd-netapply-revert.timer muxd-netapply.service muxd-netapply-revert.service; do sudo systemctl disable --now "$u" 2>/dev/null; done
sudo /usr/local/sbin/muxd-netapply revert --any 2>/dev/null
for u in muxd-update.path muxd-update.service muxd-clock-wait.service; do sudo systemctl disable --now "$u" 2>/dev/null; done
sudo systemctl disable --now muxd 2>/dev/null
sudo rm -f /etc/systemd/system/muxd.service
sudo rm -f /etc/systemd/system/muxd-update.path /etc/systemd/system/muxd-update.service /etc/systemd/system/muxd-clock-wait.service
sudo rm -f /etc/systemd/system/muxd-netapply.path /etc/systemd/system/muxd-netapply.service /etc/systemd/system/muxd-netapply-revert.timer /etc/systemd/system/muxd-netapply-revert.service /etc/sudoers.d/muxd-netapply
sudo rm -rf /etc/systemd/system/muxd.service.d
sudo systemctl daemon-reload
sudo systemctl reset-failed muxd.service muxd-update.service muxd-update.path muxd-clock-wait.service muxd-netapply.path muxd-netapply.service muxd-netapply-revert.service muxd-netapply-revert.timer 2>/dev/null
sudo rm -rf /usr/local/bin/muxd /usr/local/bin/muxd.prev /usr/local/sbin/muxd-self-update /usr/local/sbin/muxd-netapply
sudo rm -rf /var/lib/muxtraffic /var/lib/muxd-netapply /run/muxd-netapply
sudo find /root/backups -maxdepth 1 -type f \( -name 'config-preupdate-*.json' -o -name 'config-preupgrade*.json' \) -delete 2>/dev/null
sudo find /root -maxdepth 1 -type d -name '.muxd-selfupd.*' -exec rm -rf {} + 2>/dev/null
sudo rmdir /root/backups 2>/dev/null
sudo userdel muxtraffic 2>/dev/null
sudo groupdel muxtraffic 2>/dev/null
This does not free the licence on our side — tell us when you retire a server and we release its licence so you can use it on another.
Release notes
SIGNEDWhat each published MuxTraffic version brings.
The release notes appear here once a release is published.
Invoices
| Number | Date | Product | For | Total | Status | Open |
|---|
Open an invoice to read or print it. Download saves it as one file.
Your account
Profile
READ ONLYTo change these, ask us. We change them after a call-back.
Change password
Your current password, then the new one twice. Every other browser is signed out.
Two-step sign-in
After your password, a 6-digit code from an app on your phone. You choose.
Turn two-step on. Scan the code with your authenticator app (it shows as MoJ Ocean), then type your password and the first code.
You get 10 backup codes when it is on.
Turn two-step off? Sign-in will need only your password. Type your password and a code from your app to confirm.
New backup codes. Type a code from your app. Your old backup codes stop working.
They are shown only now. Each one works once, in place of a code from the app.