26 October 2023

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
    }
}
ParameterDescriptionValue Format
idMedia IDPositive integer number
useridUser IDPositive integer number
versionPlatform version. It represents current platform version when media was createdSemantic 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
        }
    }
}
ParameterDescriptionAllowed ValuesDefault Value
single_segment_templateUse Single SegmentTemplate per AdaptationSet to create a compacted manifest.yes, no, autono

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
            ]
        }
    }
}
ParameterDescriptionAllowed ValuesDefault Value
startSpecify where the video clip should start.Non-negative float or timecodenone
endSpecify where the video clip should end.Non-negative float or timecodenone

👍

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