27 July 2023
over 1 year ago by Encoding.com Product Team #2
FMP4 explicit output files naming convention
Added support of <init_extension /> parameter for advanced_dash and advanced_fmp4 output formats.
Added new <init_sub_path /> and <init_base_name /> parameters for fmp4_hls, advanced_dash, and 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>[fmp4_hls|advanced_dash|advanced_fmp4]</output>
<destination>[DestFile]</destination> <!-- required-->
<stream>
<init_extension>[Extension]</init_extension>
<init_sub_path>[SubPath]</init_sub_path>
<init_base_name>[BaseName]</init_base_name>
<!-- stream params -->
</stream>
<!-- format params -->
</format>
</query>
{
"query": {
"userid": "<<id>>", // required
"userkey": "<<key>>", // required
"action": "[Action]", // required
"source": "[SourceFile]", // required
"format": {
"output": "[fmp4_hls|advanced_dash|advanced_fmp4]", // required
"destination": "[DestFile]", // required
"stream": [
{
"init_extension": "[Extension]",
"init_sub_path": "[SubPath]",
"init_base_name": "[BaseName]"
// stream params
},
{
// stream params
}
],
// format params
}
}
}
| Parameter | Description | Available Values | Default Value |
|---|---|---|---|
| init_extension | Initialization file's extension | string (max length: 4 characters) | mp4 |
| init_sub_path | Initialization file's relative path | Valid path | none |
| init_base_name | Initialization file's name | Valid filename (without extension) | none |
For init_extension, init_sub_path, and init_base_name
The <init_extension />, <init_sub_path />, and <init_base_name /> parameters are only available for advanced_dash, fmp4_hls, and advanced_fmp4 output formats.