26 October 2023
about 1 year ago by Encoding.com Product Team #2
Platform Version in GetStatus response
Added platform version to the GetStatus response.
Response
<?xml version="1.0"?>
<response>
<id>[MediaID]</id>
<userid><<id>></userid>
<version>[PlatformVersion]</version>
<!-- status fields -->
</response>
{
"response": {
"id": "[MediaID]",
"userid": "<<id>>",
"version": "[PlatformVersion]"
// status fields
}
}
Parameter | Description | Value Format |
---|---|---|
id | Media ID | Positive integer number |
userid | User ID | Positive integer number |
version | Platform version. It represents current platform version when media was created | Semantic version |
Combining Streams in a Single Adaptation Set
Added option to allow combining streams in a Single Adaptation Set for advanced_dash and DASH manifests of advanced_fmp4 output formats.
<?xml version="1.0"?>
<query>
<userid><<id>></userid> <!-- required-->
<userkey><<key>></userkey> <!-- required-->
<action>[Action]</action> <!-- required-->
<source>[SourceFile]</source> <!-- required-->
<format>
<output>advanced_fmp4</output> <!-- required-->
<destination>[DestinationURL]</destination> <!-- required-->
<!-- Manifests fields -->
<manifest>
<single_segment_template>auto</single_segment_template>
<!-- manifest params -->
</manifest>
<!-- Multiple manifests may be included -->
<manifest>
<!-- manifest params -->
</manifest>
<!-- format params -->
</format>
</query>
{
"query": {
"userid": "<<id>>", // required
"userkey": "<<key>>", // required
"action": "[Action]", // required
"source": "[SourceFile]", // required
"format": {
"output": "advanced_fmp4", // required
"destination": "[DestinationURL]", // required
"manifest": [
{
"single_segment_template": "auto"
// manifest params
},
{
// manifest params
}
// Multiple manifests may be included
]
// format params
// Nielsen metadata settings
}
}
}
Parameter | Description | Allowed Values | Default Value |
---|---|---|---|
single_segment_template | Use Single SegmentTemplate per AdaptationSet to create a compacted manifest. | yes, no, auto | no |
Multiple clipping
Added multiple clipping feature for output formats
<?xml version="1.0"?>
<query>
<userid><<id>></userid> <!-- required-->
<userkey><<key>></userkey> <!-- required-->
<action>[Action]</action> <!-- required-->
<source>[SourceFile]</source> <!-- required-->
<format>
<output>[OutputFormat]</output> <!-- required-->
<trim>
<start>[StartTimecode]</start>
<end>[EndTimecode]</end>
</trim>
<trim>
<!-- trim parameters -->
</trim>
<!-- Multiple trim blocks may be included -->
<!-- format params -->
</format>
</query>
{
"query": {
"userid": "<<id>>", // required
"userkey": "<<key>>", // required
"action": "[Action]", // required
"source": "[SourceFile]", // required
"format": {
"output": "[OutputFormat]", // required
"trim": [
{
"start": "[StartTimecode]",
"end": "[EndTimecode]"
},
{
// trim parameters
}
// Multiple trim blocks may be included
]
}
}
}
Parameter | Description | Allowed Values | Default Value |
---|---|---|---|
start | Specify where the video clip should start. | Non-negative float or timecode | none |
end | Specify where the video clip should end. | Non-negative float or timecode | none |
For start and finish parameters
Timecode should have following format HH:MM:SS[:;]FF, where:
- HH – hours
- MM – minutes
- SS – seconds
- [:;] – : – non drop-frame, ; – drop-frame;
- FF – frames