Live-to-AutoDJ handover
Control how automated playback returns when a presenter or relay disconnects.
Build specialist Liquidsoap scripts and automation around scheduled content, live presenters, relays, metadata handling and complex AutoDJ workflows.
Control how automated playback returns when a presenter or relay disconnects.
Insert long-form programmes, idents and specialist blocks at defined times.
Route compatible external streams into the station according to schedule or fallback logic.
Normalise, rewrite or forward compatible track and source information.
Define safer behaviour when a source, relay or media item is unavailable.
Implement specialist rules that standard panel settings cannot express cleanly.
Liquidsoap is a powerful scripting language and audio engine used in many internet radio automation systems. It can select media, schedule playlists, receive live sources, relay remote streams, process metadata and send the resulting audio to streaming servers. Platforms such as AzuraCast use Liquidsoap behind the scenes for AutoDJ and live-source behaviour.
Many stations can use the normal control-panel settings without custom code. Bespoke Liquidsoap becomes useful when the playout rules are more complicated: scheduled relay takeovers, multiple fallback sources, dynamic metadata, conditional programming, custom jingles or precise live-to-automation handover.
A station may carry a syndicated show or partner stream at a fixed time. Custom logic can switch to a compatible remote source and return to local automation when the programme ends or the relay fails. This kind of workflow should be tested carefully because external stream reliability is outside the local server's control.
Good automation considers failure states. If a file is missing, a live source disappears or a relay stops responding, the station should have a defined fallback rather than dead air. Liquidsoap can be used to create layered source priorities and recovery behaviour suited to the station.
Bespoke scripts should be matched to the hosting environment and maintained when platform versions change. Complex Liquidsoap work may therefore be offered with compatible managed radio hosting or as a scoped development project after reviewing the current configuration.
Build advanced automation around an integrated Liquidsoap-based platform.
Explore AzuraCast →Choose the listener and storage package behind the automation.
Explore hosting →Expose processed station data to websites and apps.
Explore metadata →Review encoder and station setup guidance.
Open guides →No. Standard panel scheduling is enough for many broadcasters. Custom scripting is for workflows that cannot be expressed cleanly through normal settings.
Yes. It can be used to build relay and fallback logic when the hosting environment and remote source support the required workflow.
Yes. Source priority and fallback behaviour are common Liquidsoap use cases.
Liquidsoap can process metadata in advanced workflows, subject to the input source and desired output.
They should be maintained and retested when the radio platform, Liquidsoap version or surrounding infrastructure changes.
Share the current panel, sources, schedules, relays and failure behaviour so the automation can be scoped properly.