Verify That Encoding Has Completed; Table 24 Jobid.xml File Parameters - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide
jobid.xml
The SFAssetGenerator.py script run with the setup.xml and asset.xml files, outputs this file,
jobid.xml, listing IDs provided by encoding.com and used as input to SFSegment.py. It also
provides the number of profiles (equals number of job IDs) and the bitrates of each profile. The
parameters for jobid.xml are described in
Table 24 jobid.xml File Parameters
Parameters
<video_list>
<?xml version="1.0"?>
<!-- video list
<video_list>
<!-- video name -->
<video_details video_name="sf-enc.mp4">
<profile_count>2
</profile_count>
<!-- profile info -->
<profile_list>
<profile_info p="1" audiobit="64" videobit="128"></profile_info>
<profile_info p="2" audiobit="64" videobit="256"></profile_info>
</profile_list>
</video_details>
</video_list>

Verify that Encoding has Completed

In order to verify that the requested encoding has completed, you can look at your account
with encoding.com; use the Job ID given in the output of the python command to verify a
particular set of encoding requests.
Or, by setting the <status_polling_duration> element in the setup.xml file, the
SFAssetGenerator script can provide real time status updates about the encoding progress.
You will see status messages being displayed:
profile id: 1 status: downloading
profile id: 1 status: waiting for encoder
profile id: 1 status: processing
profile id: 1 status: saving
The status messages signify the following:
•
downloading—Transferring the original source files into encoding.com local storage.
Table
<video_details – Video name.
<profile_count> – Number of multi bitrate files that were generated.
<profile_list> — Information regarding the output profiles.
<profile_info> — Information regarding the output profiles with following
attributes.
•
p – profile number
•
audiobit – audio bitrate for profile
•
videobit – video bitrate for profile
-->
24, followed by an example file.
Tags and Descriptions
Creating Assets Using an SaaS
SmoothFlow Deployment
259