Skip to content

How Loomarr works

For: anyone who wants the mental model before (or after) making a channel. You’ll get: who does what, and how a sentence becomes a channel that’s always on.

Who does what

Your media server (Emby or Jellyfin) owns the library. Loomarr only reads it.

Loomarr decides what plays and in what order, and by default it also plays it: it encodes the stream and serves a tuner your media server picks up as Live TV.

Tunarr is the alternative, chosen in the wizard. Pick it if your hardware can’t transcode, or if you already run it. Loomarr still decides what plays, and hands the schedule to Tunarr.

The practical difference: on the default backend, Loomarr must be running for channels to play. On Tunarr, they keep playing without it. One trade-off: when the schedule turns over to its next window (at midnight, in the guide’s time zone), the default backend lets the programme on air finish first. Tunarr can’t, so a programme airing at that midnight on a Tunarr channel may be cut off.

Playing a channel

Nothing is encoded ahead of time. When someone tunes a channel, Loomarr looks up what’s on and starts one encoder for that item, reading your media file. Each item joins one continuous timeline, and everyone watching that channel shares it. If an item isn’t ready in time, a slate fills the gap. Browsers and the TV app get HLS; your media server gets MPEG-TS.

Someone tunes a channel: the schedule picks the item, one encoder reads your media file, a slate covers any gap, and one timeline serves browsers and the TV app over HLS and your media server over MPEG-TS

Intent → proposal → channel

You describe a channel; the suggester returns a proposal:

  • a lineup of titles you already have, and
  • an acquisition list of titles you don’t.

Every pick is a real title from your library or TMDB. The model can’t invent one. If nothing matches, the run fails clearly instead of making something up.

Approval — the one gate

A proposal does nothing until an admin approves it. Approval is the only place resources get spent: it starts the downloads and creates the channel. Members can suggest and review; only admins approve.

Filling in

A missing title is requested from Seerr or the *arrs, then downloading, then available. If the request can’t be sent, the title waits as wanted and is retried. A title that doesn’t arrive by its deadline becomes unavailable. A channel is built from what’s available now; anything missing becomes a pending slot filled with commercials, and swaps to the real program the moment it lands.

A missing title moves from requested to downloading to available; a request that can't be sent waits as wanted and is retried, and a title that misses its deadline becomes unavailable

Series

A movie is one program. A series expands into one program per episode you actually have, in the channel’s order. New episodes join on the next refresh.

Filler and pods

Between programs, Loomarr inserts pods — short runs of bumpers and commercials from your filler folder, matched to the channel. No filler just means no commercials.

Policy

A channel carries a policy: which content, a rating cap, no repeats, ordering. The model suggests it from your intent (“for the kids” → a TV-Y7 cap); the scheduler enforces it the same way every time. See the curation page.

What stays home

Your library, channels and quality measurements stay in your database. Privacy lists every outside service Loomarr can contact, what it sends, and how to turn it off.