ersatztv-schedule

You generate a 24-hour playout JSON schedule by planning deterministic start and finish windows with absolute paths from your local media library, then validating the output with the playout validator to ensure continuous daily pipelines.

The three-tier configuration structure for ErsatzTV channel provisioning consists of lineup.json, channel.json, and individual playout items, which together manage daypart-based scheduling and per-item start and finish logic.

You maintain continuous ErsatzTV playouts by using lavfi sources to generate filler content, ensuring 24-hour pipelines remain unbroken when local or http media sources run out or encounter gaps.

Yes, you can use marathon and date gate scheduling when building ErsatzTV playout files, applying these configurations alongside standard daypart scheduling to control media library playback patterns.

Your ErsatzTV playout JSON fails validation when timestamps are not formatted as RFC 3339 strings or media paths are not absolute, both of which are required by the playout validator to confirm schedule integrity.

Yes, you need absolute paths and RFC 3339 timestamps for ErsatzTV playout files because the playout validator checks these strict formatting requirements to guarantee deterministic scheduling and proper media resolution.