Radio automation without a Liquidsoap scripting layer

What “without” means

The FlowCast control plane does not generate a Liquidsoap program for another runtime to interpret. Its scheduler supplies the next-track decision, and the dedicated Rust playout engine handles queues, transitions, encoding and Icecast output from explicit settings.

Operational benefits

• No Liquidsoap syntax or generated script is required for standard FlowCast operation.
• Scheduler and playout state share FlowCast’s configuration and diagnostics.
• Docker Icecast automation has fewer conceptual layers to trace.

The trade-offs

Liquidsoap is a mature, independent and flexible streaming language. FlowCast does not claim to reproduce its full scripting surface, integrations or ecosystem. A specialised engine means operators work within the capabilities FlowCast explicitly exposes.

Current boundaries

FlowCast remains a Preview with incomplete endurance, rootless Docker, large-library and disaster-recovery qualification. Service-image availability can vary by tag and architecture. Read documented features, install safely, and check the repository’s live limitations.