Steps For Creating On-Demand Assets; Requirements And Files For Creating On-Demand Assets; Bitrate Profiles Naming Conventions For On-Demand Assets - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide
Step 4 –
request.
Figure 68 On-Demand Workflow, Typical Steps

Steps for Creating On-Demand Assets

1. Encode multi-bitrate profiles for each video using the method of your choice and following
the Bitrate Profiles Naming Conventions for On-Demand
2. For each set of multi-bitrate profiles,
Assets
assured flow rate and threshold.
3. Pre-Stage On-Demand Assets
AssetDescription.dat file) for each video on the Media Flow Controller or your origin-
server.
4. Initiate SmoothFlow Processing for On-Demand Assets
demand SmoothFlow delivery.

Requirements and Files for Creating On-Demand Assets

Juniper Networks uses the multi-bitrate profiles, one file that you create, the
AssetDescription.dat text file, and commands that you issue at the command line to create
SmoothFlow assets on-demand. You must follow the bitrate profile naming conventions
described.

Bitrate Profiles Naming Conventions for On-Demand Assets

When naming the bitrate profiles after encoding, Media Flow Controller SmoothFlow requires
this convention:
<name>_p<NN>.flv
Where name is the name of the video, followed by an underscore, the lower-case letter "p"
and two digits, NN, representing the bitrate profile number (01 - 99 with 01 being the lowest
bitrate profile and increasing numbers denoting higher encoding bitrates). For example,
Initiate SmoothFlow Processing for On-Demand Assets
describing the multi-bitrate profiles including frame rate, keyframe interval, and
Create AssetDescription.dat File for On-Demand
by placing the assets (the set of multi-bitrate profiles and
SmoothFlow Deployment
via a processing "trigger"
Assets.
to prepare the assets for on-
Creating On-Demand Assets 263