00SERVERStreaming server and channel headend

GodwinMix as your streaming server and channel headend.

The same app that mixes a show also takes streams in and sends them out. Encoders push to channels over RTMP, RTMPS, SRT or WHIP. Feeds can be pulled from SRT, RTSP, HLS or a multicast group. Out of it come HLS and DASH for your own players, restreams to the platforms, UDP multicast for a cable or IPTV system, and a recording of each channel. It runs on a server, in Docker or on the laptop you already have.

Watch the films Moving from Livebox

01FLOWHow it fits

Encoders in, one channel engine, every screen out.

02JOBSWhat it does

The jobs a streaming server does, in the same app.

Channels

Encoders push in

A channel is one live stream with its own address. OBS, a phone or a hardware encoder publishes to it over RTMP on 1935, SRT on 9000 with the key as passphrase, WHIP, or RTMPS on a port you choose. Several streams can share one channel, so an encoder's own ladder comes in untouched.

Pull

Feeds that wait to be fetched

A channel can pull an RTMP, RTMPS, SRT, RTSP or HLS address and retries by itself when it drops. The mixer also takes SRT callers and listeners, RIST, multicast MPEG-TS with program selection, NDI and DeckLink capture.

Your players

HLS, DASH and WebRTC

A watch link gives HLS with a QR code and an embed code. The programme can serve HLS with a ladder of sizes, low latency HLS, DASH from the same segments, RTSP on 8554 and WebRTC for small audiences.

Restream

Every platform at once

Send a channel on to YouTube, Facebook, Twitch, Kick, Instagram Live, LinkedIn Live, X, TikTok LIVE, any RTMP server or SRT. By default the stream is copied, nothing decoded. A destination that drops keeps reconnecting while the others carry on.

Formats

Several renditions at once

Each destination picks a format. Same as the source is free. For the rest GodwinMix decodes once, scales once per size and shares one encoder per rendition, on the GPU when there is one, and refuses a format that would make what is on air drop frames.

IPTV

Multicast for cable systems

Direct shows pass a feed straight to UDP multicast, SRT or RIST outputs, with a backup input that takes over when the main one stalls. A list of feeds in a CSV adds dozens at once.

Record and air

Recording, ad breaks, radio

Record keeps a copied file of each channel, a new one each time it goes live. Ad breaks roll a clip and rejoin live, by hand, by timer or by API. Icecast sends the sound as MP3 or Opus radio.

Watch it

Monitoring wall and flow map

Every channel on one screen with its picture, rates and alarms for black, frozen, silent, stalled and lost input. The flow map follows each signal from input to output. Watch the monitoring film.

Where it runs

Server, Docker, laptop

Headless on Linux with systemd, in Docker as ghcr.io/psmux/godwinmix, on Windows or a Mac. A Raspberry Pi runs it too, encoding in software, so plan for 720p30.

03PROTOCOLSWhat goes where

Protocols, by direction.

From the 0.3.17 documentation. Partial means the docs name a limit, given in the cell.

Protocol	Encoders push in	Pull a feed	Push out	Serve to players
RTMP	Yes	Yes	Yes	No
RTMPS	Yes, own port	Yes	Yes	No
SRT	Yes, with a passphrase	Caller and listener	Yes	A channel, on request
WHIP (browsers, phones)	Yes	No	No	No
RIST	No	Simple Profile	Simple Profile	No
UDP and multicast MPEG-TS	No	Yes, with program and SSM	Yes, not on Windows	No
RTSP	No	Yes	No	Programme only
HLS and LL-HLS	No	Yes	No	Yes
DASH	No	Headend inputs	No	Yes
WebRTC (WHEP)	No	No	No	Small audiences
NDI	No	Yes	No	No
SDI and HDMI (DeckLink)	No	Yes	No	No
Icecast radio	No	Audio	MP3 or Opus	No

Sources: the GodwinMix docs at version 0.3.17, under how-to and reference. WHIP and WHEP need the GStreamer libnice plugin. HLS needs AAC sound.

04FILMSSee it working

Recorded on GodwinMix 0.3.17.

How to1:27

Channels: be your own streaming server

WHAT YOU WILL LEARNMake a channel for an encoder with the password it already uses, pull an SRT feed, play the channel over HLS in a browser, send it on to a platform, record it, and send it to IPTV as multicast.

Read the steps

Open the Channels tab and press Add Channel. Name it and choose An encoder (OBS, a phone, a camera).
Under More options, keep the Address and Password your encoder already uses, then press Create channel. Copy the Server and Stream Key into the encoder.
For a feed that waits to be fetched, choose Pull from a URL and paste its srt://, rtmp://, rtsp:// or HLS address.
Press Watch link, then Make the link, for an HLS link, a QR code and an embed code. Watch here plays it in the page.
Under Send on to, pick a platform or More, paste the key, choose a format and press Start sending. Record keeps a copy.
For IPTV, add a direct show from the channel with channel:<name>/main as input and a udp:// multicast output.
Today: make one channel and point a single encoder at it.

How to0:50

Moving from Livebox

WHAT YOU WILL LEARNBring Livebox channels in by pasting the addresses your encoders already use, so names and passwords stay the same and only the host changes.

Read the steps

Open the command palette with Ctrl+K (or ⋯ beside Add Channel) and choose Bring channels from Livebox.
Paste one address a line, such as rtmp://203.0.113.10:1935/Stadium/main?psk=matchday-77. The Stream URL and Stream key from a Livebox dashboard also work, one under the other.
Press Bring them in. Each line says made, or already the channel, or what is wrong with it.
Point the encoders, or the name they use, at this machine. They connect with their old settings.
Push destinations are not carried over. Add them again under Send on to, or paste several at once from Bulk actions.
Today: move one channel, then bring the rest.

Recorded in a test setup: encoders and feeds are stock clips sent from the same computer, the platform is a local test server, and the addresses and passwords are made up. The monitoring film shows the wall and the flow map.

05MOVINGMoving from Livebox

Moving from Livebox keeps every encoder as it is.

Each channel keeps its name as the address and its password as a key on port 1935, so the encoder settings stay the same and only the host changes. Paste many at once, check the result line by line, and add push destinations again under Send on to.

rtmp://203.0.113.10:1935/CityCouncil/main?psk=council-2025
rtmp://203.0.113.10:1935/Stadium/main?psk=matchday-77
rtmp://203.0.113.10:1935/Studio1/main?psk=studio-one-9

Example addresses and passwords. Command line users can do the same with gmx ctl rpc channel.add.

We can move your channels with you.

Ripeflow LLC plans the move, sets up the server and stays on call while your encoders switch over.

Book a demo