Professional playout no longer has to depend exclusively on dedicated hardware boxes. With software-defined media infrastructure, a standard x64 server can take scheduled file-based content, mix it with live sources, process the result as a continuous live stream, and deliver it into a broadcast SDI chain.
Nimble Streamer fits this model as a software-defined playout server through Nimble Playout. Nimble Playout turns local VOD assets and live input streams into a continuous live output, including default streams for failover cases. SDI output support allows that stream to be sent to connected SDI hardware (Blackmagic or AJA) for downstream routing, production, monitoring, or distribution. This brings a number of benefits that we describe below.
What Nimble Playout does
Nimble Playout lets engineers organize files and live streams into a controlled playout sequence. Instead of manually starting clips or switching sources outside the media server, Nimble Streamer reads a playlist definition and generates a live output from VOD files, live inputs, or a mix of both.
A playlist can include one or multiple blocks, scheduled start times, playback durations, file offsets, looped blocks, live stream references, and selected audio/video tracks when files contain multiple tracks. It also allows defining the default stream for cases when the initial content is unavailable. This makes it suitable for repeatable playout workflows such as TV channels, internal channels, signage feeds, event loops, training channels, live-program inserts, and 24/7 linear-style programming.
For SDI workflows, the key point is simple: files and live sources become a Nimble Playout live stream first, then Live Transcoder converts that stream into SDI output.
Requirements
This workflow requires:
- WMSPanel account for cloud-based management.
- Nimble Streamer installed on Ubuntu version 22.04 or later.
- Latest Live Transcoder package installed on the same server.
- Active Live Transcoder license registered for the Nimble instance.
- Supported SDI hardware, such as Blackmagic DeckLink or AJA devices, installed and visible to the operating system.
- VOD files and live input streams prepared with consistent technical parameters, as described in Playout spec.
Step 1: Prepare Playout stream
Nimble Playout uses a playlist configuration to describe the output live streams and the sequence of sources to play for each of them. This includes linear playout of files (both local and from AWS storage) and live streams, setting up failover default streams and more.
The playlist configuration is as JSON file which you can create manually, and also use the Playout Wizard or our ask our AI assistant to generate the playlist structure.
Read full specification to learn more what you can use for your scenario.
Once the Playout is set, make sure it’s generating a live stream.
Step 2: Create SDI output in Live Transcoder
Now you need to create the SDI output in the Live Transcoder UI. In this stage, the Nimble Playout stream becomes the input for a Live Transcoder scenario, and Live Transcoder forms the SDI output for the connected device.
The general pipeline is:
Nimble Playout output -> Live Transcoder scenario -> SDI video/audio encoders -> SDI deviceAll the setup is done on-the-fly without streaming interruption, which reduces maintenance windows in live broadcast environments.
The SDI output setup is described in SDI Decklink output setup article and in AJA SDI setup article in full details. Please refer to them for full details and all the nuances of setting up the SDI output.
Economic and technical benefits
The economic case is straightforward. Instead of purchasing a dedicated hardware playout server for every channel or workflow for SDI output, facilities can use standard x64 servers running Ubuntu and Nimble Streamer. This reduces capital cost, simplifies scaling, and gives engineers a flexible platform that can support playout, transcoding, re-packaging, SDI, streaming protocols, and hybrid production workflows from the same software-defined environment.
The default stream for any input allows setting an easy failover for cases when the original input content is unavailable – whether it’s a VOD file not accessible at AWS, or live stream being out.
Having the JSON file as a configuration method, our customers make all kinds of automations around Playout. Like, automatically create playouts with live streams, each having their own failover media files to show up as a stub.
For broadcasters and Pro-AV teams, this creates a practical migration path: keep professional SDI infrastructure where it is needed, while replacing fixed-purpose playout hardware with a more flexible software media server.
FAQ
Can I loop a playlist for 24/7 SDI broadcast?
Yes. Nimble Playout supports looped blocks through its Server Playlist configuration, so a prepared set of local files can run continuously as a 24/7 linear-style channel. For broadcast use, normalize all files first and monitor the output stream for timing, audio consistency, and file availability.
What video codecs are supported for local files in Nimble Playout?
For VOD input, supported video codecs include H.264/AVC, H.265/HEVC, VP8, VP9, and AV1. Supported audio codecs include AAC, MP3, Opus, FLAC, MP2, and AC-3/E-AC-3. MP4 and MP3 containers are supported for file-based playlist input. Nimble Playout can also reference live streams that are already available in Nimble Streamer.
Do I need Live Transcoder for playlist-to-SDI output?
Yes. SDI output is created through Live Transcoder. The workflow requires the Live Transcoder package and an active Live Transcoder license on the Nimble Streamer instance.
Can I update the playlist without stopping the stream?
Yes. Nimble Streamer checks the playlist according to the configured sync interval. Supported WMSPanel settings are applied on-the-fly without streaming interruption.
Can Nimble Playout use both files and live streams?
Yes. Nimble Playout can use VOD files (both local and from AWS storage) and live streams as input sources through Server Playlist configuration. This allows hybrid playout, for example a loop of local programs with scheduled live inserts, a live feed followed by local fallback content, or a 24/7 channel that mixes prerecorded segments with real-time contribution streams.
Can I automate my setup for Playout?
Yes. You can generate JSON configuration with your own software to create Playout streams, and have Nimble to pick it up easily with no need for any UI and command line.
Is this a replacement for traditional playout hardware?
For many workflows, yes. Nimble Streamer can operate as a software-defined playout server, using standard server hardware and SDI I/O devices instead of dedicated proprietary playout appliances.
Install Nimble Streamer today and try the workflow above in action.