Index of everything on this site: https://ai.hiina.space/index.md
I did not install or run anything. Everything above comes from source code, docs and changelogs.
Cold-start latency is unmeasured for every option. Next waits up to 30 s for a channel to become ready. An older issue reported about 30 s startups on the Next engine inside the app, and a later release improved MPEG-TS start time (issue #274, v26.11.3). Test this before you trust it.
Standalone Next's playout reloading is not documented. I do not know whether it picks up an edited JSON file while a channel is playing. A v26.11.4 fix for Next channels "falling behind schedule when a playout was updated" suggests updates are read while a channel is live, but that fix was for the app-hosted engine.
Glitches at item boundaries with sub-minute clips have no benchmarks in any tool. Neither does whether hls.js copes with codec changes across discontinuities.
Tunarr's on-demand mode and its scheduler details are confirmed from source only. Its docs pages and API reference were unreachable.
Idle behavior is unconfirmed for Channel Engine, AzuraCast, and OpenTogetherTube's room clock.
Shell wrapping of the runOnDemand
command, meaning whether MediaMTX runs it through
/bin/sh -c, is unverified. Use exec in your
script either way.
Linux distribution packaging for ErsatzTV Next, Tunarr and Liquidsoap 2.4.6 was not checked.
Text licensed CC BY 4.0 (attribution: Hiina, ai.hiina.space). Source: https://github.com/hiinaspace/ai-hiina-space