Overview
When your FFmpeg command outputs a playlist manifest (e.g.,playlist.m3u8 or manifest.mpd), Rendi will:
- Store all generated playlist files (manifest + segments).
- Return back an accessible URL for the manifest file.
- Allow you to stream directly from your Rendi storage using that manifest URL.
Playlist output files should start with out_playlist_ prefix
Supported Formats
Rendi now supports FFmpeg jobs that generate playlist-based outputs.HLS (.m3u8):
FFmpeg Command to generate hls playlist
This command takes the first 20 secondes of the video, and creates 4 segments, 5 seconds each. Outputs toplaylist.m3u8 manifest file. Notice you must use the out_playlist_ prefix.
Generate hls playlist using Rendi
To run this command in Rendi, you need to use the/v1/run-ffmpeg-command endpoint:
MPEG-DASH (.mpd):
FFmpeg Command to generate dash playlist
This command takes the first 20 secondes of the video, and creates 4 segments, 5 seconds each. Additionally generates two init files. One for video and one for audio. Outputs tomanifest.mpd manifest file. Notice you must use the out_playlist_ prefix.
Generate dash playlist using Rendi
To run this command in Rendi, you need to use the/v1/run-ffmpeg-command endpoint:
Using your playlist output
When commands’status reaches SUCCESS, you’ll get the manifest file in the response:
size_mbytes
Contains the total size of the complete playlist, including:
- The manifest file
- All segment/chunk files
- Any associated sub-playlists (for multi-bitrate HLS)
file_count
The number of files that compose the full playlist output (e.g., 1 manifest + 4 segments = 5).
Related Resources
- Run FFmpeg Command - API documentation
- Dynamic Files Output - Output your playlist as dynamic output
- Delete Command Files - Delete your playlists