Playout
Getting a channel onto a TV. Loomarr’s own streaming engine stitches a channel into one continuous stream and burns in the channel’s logo; Tunarr is the other backend that can play a channel. The Live TV wiring and the backend transition publish channels to the media server, LAN discovery lets TV apps find Loomarr, and the bench measures the pipeline on real hardware.
One area of the package map.
Imports from other areas
- platform · 8 imports — the diagnostics process manager that runs every encoder, the store behind a backend transition, start-up configuration, Tunarr’s HTTP client and metrics, the address check that keeps LAN discovery answering only the household’s network, and the language codes an audio track is chosen by
- media · 6 imports — the encoder choice, loudness, media facts and process-tree control the stream is built from
- channels · 5 imports — the
channels/scheduleprogramming a backend plays - library · 2 imports — the media server’s Live TV API that channels are published to, and
library/provisionkeys naming what a slot plays
Packages
playout· 13 importers · →channels/schedule,library/provision,media/encode,media/measure,media/proctree,platform/diagnostics,platform/langcode,playout/packagerLoomarr’s own streaming engine (design §9.1): it turns a channel’s computed lineup into a continuous MPEG-TS a media server can tune, without Tunarr.playout/backendtransition· 1 importer · →channels/schedule,platform/storeOwns the durable workflow that separates preparing a playout backend from publishing it to the media server.playout/bench· →media/encode,playout,playout/packagerCross-hardware playout bench (#1512 G8): a redistributable corpus run through Loomarr’s real playout pipeline builder (playout.Build), one standard report, judged against the beta.8 thresholds and diffed against the last accepted report per hardware family.playout/channelbug· 1 importer · →channels/schedule,media/encode,platform/diagnostics,platform/store/channelstore,playout,playout/watermarkTurns a channel’s watermark policy into the bug its programmes air with: it picks the look, colour and holiday version, renders through playout/watermark, caches the files, and runs the per-encoder GPU overlay self-check that gates the bug.playout/landiscovery· →platform/httpxAdvertises a running Loomarr HTTP listener to unpaired local TV clients.playout/livetvpublish· 1 importer · →library/mediaserver,playout/tunarrPublishes Loomarr’s channels to the media server’s Live TV (§6, §9.1): it registers, verifies, refreshes and retires the one tuner + guide pair Loomarr owns, and wires the media server as Tunarr’s media source.playout/packager· 2 importers Channel packager (#1512 phase 2): one long-lived, in-process stitcher per (channel, output format) that turns a sequence of per-item fMP4 encodes into one gapless channel timeline.playout/subtitles· 3 importers · →media/bgexecServes a channel’s soft subtitles beside its stream (#2088 decision 5): the text subtitle tracks the programme on air carries, and the chosen track’s cues on the channel’s wall clock.playout/tunarr· 5 importers · →channels/schedule,platform/httpx,platform/metricsProgrammer boundary (design §6/§9): the port the scheduler drives to make a Loomarr channel real, plus its only v1 implementation, a thin hand-written Tunarr client (§6: “hand-write a thin client against only the endpoints we use” — not codegen against Tunarr’s churny pre-1.0 spec).playout/tunarr/tunarrtest· →channels/schedule,playout/tunarrThe shared Tunarr test double and HTTP fixture server (AGENTS.md testing rules: unit tests never touch the network; extend this package rather than inventing a private mock).playout/watermark· 1 importer Renders a channel’s bug (#1512): the small mark burned into a channel’s programmes by the GPU overlay (internal/playout, watermark.go).