In detail
Adding an M3U playlist and XMLTV guide
Setup is two addresses. In the source settings you paste the URL of your
M3U playlist and the URL of your XMLTV guide, and Mimir fetches and
indexes both. From that point the guide grid is populated and every
channel is one click from playing or recording.
If your playlist and guide are files already sitting on the machine
rather than URLs, that works too; a built-in path browser lets you pick
them without typing a full path or copying files around. On Docker,
mount the folder that holds them first (the download page shows the
one-line mount) and it appears in the picker like any other folder.
Recording internet streams from an M3U playlist
An M3U playlist tells Mimir where to find each channel's stream. Attach an XMLTV guide and schedule a program with padding before and after its listed times. Recordings are saved as ordinary video files in a folder you choose, and you can start watching while capture is still in progress.
If the stream disconnects or stalls, Mimir retries until the scheduled end. When the source returns, capture continues. Recording finalisation checks the captured segments for timing discontinuities and repairs their joins for playback. This cannot recover video that the source never delivered. Read about stream recovery and recording repair.
Schedule and watch recordings from Apple TV, Android TV and NVIDIA SHIELD, or the iPhone, iPad and Android mobile apps. The server does the recording, so your viewing device can sleep while it continues.
Set the source's connection limit to match what it allows. Mimir checks scheduling conflicts and gives recording priority when capacity is tight.
Guide matching, and fixing it when it's wrong
Channels in an M3U carry an identifier that's supposed to match a channel
in the XMLTV file. In practice sources are inconsistent: identifiers go
missing, change without warning, or don't match the guide at all. When
that happens the channel appears with no listings.
Mimir lets you set a channel's guide mapping by hand. Point the channel
at the correct guide entry, and it stays pointed there, through every
subsequent refresh, because your mapping is stored separately from the
source data rather than written back into it.
Customisations survive refreshes
This is the design decision that matters most day to day. Source data and
your changes are kept apart. Playlists and guides update on their own
schedules; your names, numbers, groups, logos, stream overrides and guide
mappings are layered back over the fresh data every time. You set the
lineup up once.
You can also export the entire configuration, every selection and every
customisation, to a single versioned, checksum-verified file, and import
it later. That's your backup before experimenting, and the way to move a
finished setup to another machine.
One-off channels
A stream that isn't in any playlist can be added on its own, with a
channel number, group, logo and guide mapping of your choosing. It sits
in the lineup alongside everything else and records the same way.
Where hardware tuners fit
These two formats are also how most networked TV hardware publishes
itself. A SiliconDust HDHomeRun or VBox TV
Gateway puts an aerial, cable or satellite feed onto your network and
exposes it as a channel playlist, with VBox publishing a full XMLTV
guide alongside it. To Mimir that's simply another source, which means
hardware tuners and file-based sources can run side by side in the same
lineup, with one guide covering both.
What Mimir doesn't do
It supplies no channels, no playlists, no guide data and no content of
any kind. You bring your own source, and you're responsible for holding
the rights to whatever you stream or record. Mimir is the software half
of a system whose other half is entirely your choice.