SmoothFlow Deployment
•
waiting for an encoder—Waiting for encoding.com to assign an encoder from the cloud
compute.
•
encoding in progress—Encoding is underway.
•
saving—Transferring the encoded files back into user's FTP account.
After the requested bitrate profiles and metadata files appear in the output folder, you are
ready to request SmoothFlow publishing of the encoded assets.
Prepare Media Flow Controller for Assets Created Using an SaaS
The SFSegment.py script works with one XML file, segment_config.xml. You use this script
to tell Media Flow Controller where the encoded multi-bitrate file chunks are located.
Preparing Media Flow Controller requires these steps:
1. Create the segment_config.xml file describing the multi-bitrate assets for Media Flow
Controller including the IP address of the Media Flow Controller, where the assets are
located, access credentials for obtaining the assets, and a temporary directory in the
system for SmoothFlow processing.
2. Run the SFSegment.py script to initiate SmoothFlow processing and publishing to Media
Flow Controller, and render the assets ready for delivery.
Usage Options for SFSegment.py Script
Use the SFSegment.py python script by running the python command at the command line
and using the following tags.
•
-s—segment_config.xml
•
-i—jobid.xml
•
-of—output video format
•
-af—Assured Flow Rate (AFR) threshold (should be set at a value greater than one half
the bitrate of the highest bitrate profile in the asset)
Example:
python SFSegment.py -s segment_config.xml
-i <jobid_xml_file_generated_by_SFAssetGen>
[-of <output_video_format>] [-af <AFR_threshold>]
segment_config.xml file
The configurable parameters for segment_config.xml are described in
an example file.
Table 25
segment_config.xml Parameters
Parameters
<mfd-ip>
<origin-path>
260
Creating Assets Using an SaaS
Note!
The <mfd-ip> tag = Media Flow Controller IP address.
IP address of the Media Flow Controller which hosts the video content. This is needed to
publish the HTML files containing the SmoothFlow player
Path to which the segmented data needs to be copied. Needs to be the origin server's
doc root (www/var/html) directory. This script can be run either on the origin server, or on
another system where the doc root of the origin server is mounted as an NFS mount
Media Flow Controller Administrator's Guide
Table
25, followed by
Tags and Descriptions
Copyright © 2010, Juniper Networks, Inc.
Need help?
Do you have a question about the MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI and is the answer not in the manual?
Questions and answers