Offline Orchestration

Last updated: 2025-11-03 17:33:15Download PDF

Operation Scenarios
Media processing supports orchestration functionality, offering users an intuitive visual canvas to seamlessly connect multiple media processing templates. These templates can be executed sequentially or based on specific conditions. By flexibly combining orchestration elements, users can achieve diverse media processing effects. Once Offline orchestration is configured, videos uploaded to the designated Bucket directory will automatically trigger the orchestration workflow, with output files written to the specified Bucket directory. Within the orchestration process, tasks such as audio and video transcoding, audio and video enhancement, screenshot generation, media AI, and media quality inspection can be configured.
﻿
Creating Offline Orchestration
Go to the Creation Page
1. Log in to the MPS Console, and click Orchestrations > Offline Orchestration > Create Offline Service Orchestration.
2. On the page that appears, create the orchestration based on the business scenario requirements and configure relevant information.
﻿
Configure Orchestration
Configuration Item
Required
Configuration Description
 Trigger type
-
By default, "Tencent Cloud COS" is selected, indicating that the bucket that triggers the orchestration belongs to Tencent COS.
When "AWS" is selected, the trigger bucket belongs to AWS S3. This option can be selected if the bucket is configured on AWS services. Refer to Using Amazon S3 Buckets with MPS for detailed information.
Orchestration name
Yes
You can enter a combination of letters, digits, underscores, and hyphens (_). The length cannot exceed 128 characters. Example: "MPS".
Trigger bucket
Yes
You can select a bucket created under this APPID as the trigger bucket. Once the orchestration is enabled, video file upload to this bucket will automatically trigger the orchestration execution.
Trigger directory
No
The directory should end with a forward slash (/). If left unspecified, all directories of the trigger bucket can trigger the orchestration execution.
Trigger formats
-
For newly uploaded files in the trigger directory, the orchestration task will only be triggered if they match the specified file extensions, thereby preventing unintended activations.  
By default, the Preset option is selected. For details on supported trigger formats under presets, please refer to the Preset Trigger Formats section below. 
Alternatively, you may switch to Custom to define your own list of extensions. 
If No Extension Restrictions is selected, all newly uploaded files in the trigger directory—regardless of their extensions or even the absence thereof—will trigger the orchestration task.
Output bucket
Yes
By default, the output bucket is the same as the trigger bucket. You can also select another bucket in the same region corresponding to the specified APPID as the output bucket. Newly generated video files will be stored in the selected bucket once the service orchestration is completed.
Output directory
No
The directory should end with a forward slash (/). If left unspecified, the trigger directory will be taken as the output directory.
Enable event notifications
-
Refer to the Configure Event Notification section below for details.
Once enabled, the transcoding process and result data will be sent through the selected notification method.
Actions
-
Refer to the Configure Actions section below for details.
You can quickly build a process by defining process nodes and templates of the service orchestration.
Associate Resource
No
This configuration option will only appear if cost allocation has been enabled in the General Management > General Settings.
After resources are associated, cost allocation can be performed for the bill related to this orchestration based on the resource-bound tags. If you need to modify resources, go to Cost Allocation Management.
Preset Trigger Formats  
When "Trigger Format" is set to Preset, the system will automatically initiate processing for newly uploaded files (including video, audio, or subtitle files) in the specified directory, provided their extensions fall within the list below:
Category
File Extensions
Video File Extensions
.mp4, .avi, .mov, .wmv, .flv, .mkv, .mpg, .mpeg, .rm, .rmvb, .asf, .3gp, .webm, .ts, .m4v
Audio File Extensions
.mp3, .wav, .aac, .flac, .ogg, .m4a, .amr
Subtitle File Extensions
.vtt, .srt
Note:
Only file formats supported by MPS functionality can be processed successfully; otherwise, the orchestration task will fail.
Example: If an orchestration is configured with an audio/video transcoding node and a .vtt subtitle file is uploaded to the trigger directory, the orchestration will be triggered. However, since the audio/video transcoding feature only supports processing audio and video files, the orchestration task will fail and no charges will be incurred.
Configure Event Notification
This feature can provide real-time updates on the progress and status during task execution. You can enable and configure this feature to receive notifications. Currently, Tencent Cloud provides two event notification mechanisms: TDMQ-CMQ callbacks, HTTP callbacks, and SCF callbacks. Detailed information is as follows:
Callback Type
Configuration Description
TDMQ-CMQ callbacks
To enable TDMQ-CMQ callback, go to the TDMQ console to activate the CMQ service and create a model. Once enabled, the specified CMQ service will receive event notifications from MPS. You need to fill in the following information:
TDMQ-CMQ model: Queue model is selected by default.
TDMQ-CMQ region: You can select Guangzhou, Shanghai, Beijing, Shanghai Finance, Shenzhen Finance, Hong Kong (China), Chengdu, North America, or West US.
Queue name: Custom.
HTTP callbacks
When calling the event notification configuration API TaskNotifyConfig, specify the NotifyType parameter to URL and fill in the HTTP callback address in the NotifyUrl parameter.
Configure Actions
You can define the entire service process, add various service nodes (such as audio and video transcoding, audio and video enhancement, media AI, media quality inspection, and screenshot processing, encompassing logical nodes.), and apply different templates to each node. The detailed configuration is described as follows:
1. Click the +  button to select the required action from the drop-down list and add it. 
﻿
2. After the action is added, the action node is displayed. You can then configure detailed information on the node. 
Note:
The configuration pages vary for different actions. The following figure shows the page of the audio/video transcoding action.
﻿
Execution Conditions
In the orchestration process, first add a media quality inspection node. Subsequently, you can include an "IF condition" node, which serves as a logical node. This node does not create any media processing subtasks but determines whether to execute subsequent nodes based on whether the media asset meets the conditions set within the node.
﻿
Note：
The node evaluates whether the conditions are met; if so, it executes the corresponding workflow branch. Otherwise, it proceeds with the Else if workflow branch.
Each branch condition supports the addition of multiple evaluation criteria (AND/OR) and allows for the configuration of multiple conditional branches. The priority of branch conditions can be set by dragging and adjusting the branch condition configuration panel.
﻿
Enabling an Orchestration to Activate Automatic Task Triggering
Once an orchestration is created, it is disabled by default.
After the orchestration is enabled, automatic task triggering is activated. When files are uploaded to the trigger bucket configured for the orchestration, the system automatically initiates processing tasks, without the need to manually create tasks in the console.
If the orchestration is disabled, MPS tasks will not be executed for video files uploaded to the trigger bucket.
Note:
Once the orchestration is enabled, it only takes effect in video files newly uploaded to the trigger bucket. Files previously stored in the trigger bucket will not be automatically processed. 
﻿
You can find the trigger bucket  &  output bucket configured for the orchestration in the menu  Orchestration > COS Bucket  page, to conveniently carry out operations such as file upload, preview, download, etc.
﻿
Editing and Deleting an Orchestration
Editing an Offline Orchestration
Click Edit in the operation column of the target orchestration to enter the Orchestration Editing page. Then, you can modify the orchestration name, trigger bucket, trigger directory, output bucket, output directory, event notification, and configuration items.
Deleting an Offline Orchestration
Click Delete in the operation column of the target orchestration to delete it.
After the orchestration is deleted, MPS tasks will not be executed for video files uploaded to the trigger bucket.
Note:
When the orchestration is enabled, it cannot be edited or deleted.

Configuration Item	Required	Configuration Description
Trigger type	-	By default, "Tencent Cloud COS" is selected, indicating that the bucket that triggers the orchestration belongs to Tencent COS. When "AWS" is selected, the trigger bucket belongs to AWS S3. This option can be selected if the bucket is configured on AWS services. Refer to Using Amazon S3 Buckets with MPS for detailed information.
Orchestration name	Yes	You can enter a combination of letters, digits, underscores, and hyphens (_). The length cannot exceed 128 characters. Example: "MPS".
Trigger bucket	Yes	You can select a bucket created under this `APPID` as the trigger bucket. Once the orchestration is enabled, video file upload to this bucket will automatically trigger the orchestration execution.
Trigger directory	No	The directory should end with a forward slash (/). If left unspecified, all directories of the trigger bucket can trigger the orchestration execution.
Trigger formats	-	For newly uploaded files in the trigger directory, the orchestration task will only be triggered if they match the specified file extensions, thereby preventing unintended activations. By default, the Preset option is selected. For details on supported trigger formats under presets, please refer to the Preset Trigger Formats section below. Alternatively, you may switch to Custom to define your own list of extensions. If No Extension Restrictions is selected, all newly uploaded files in the trigger directory—regardless of their extensions or even the absence thereof—will trigger the orchestration task.
Output bucket	Yes	By default, the output bucket is the same as the trigger bucket. You can also select another bucket in the same region corresponding to the specified `APPID` as the output bucket. Newly generated video files will be stored in the selected bucket once the service orchestration is completed.
Output directory	No	The directory should end with a forward slash (/). If left unspecified, the trigger directory will be taken as the output directory.
Enable event notifications	-	Refer to the Configure Event Notification section below for details. Once enabled, the transcoding process and result data will be sent through the selected notification method.
Actions	-	Refer to the Configure Actions section below for details. You can quickly build a process by defining process nodes and templates of the service orchestration.
Associate Resource	No	This configuration option will only appear if cost allocation has been enabled in the General Management > General Settings. After resources are associated, cost allocation can be performed for the bill related to this orchestration based on the resource-bound tags. If you need to modify resources, go to Cost Allocation Management.

Category	File Extensions
Video File Extensions	.mp4, .avi, .mov, .wmv, .flv, .mkv, .mpg, .mpeg, .rm, .rmvb, .asf, .3gp, .webm, .ts, .m4v
Audio File Extensions	.mp3, .wav, .aac, .flac, .ogg, .m4a, .amr
Subtitle File Extensions	.vtt, .srt

Callback Type	Configuration Description
TDMQ-CMQ callbacks	To enable TDMQ-CMQ callback, go to the TDMQ console to activate the CMQ service and create a model. Once enabled, the specified CMQ service will receive event notifications from MPS. You need to fill in the following information: TDMQ-CMQ model: Queue model is selected by default. TDMQ-CMQ region: You can select Guangzhou, Shanghai, Beijing, Shanghai Finance, Shenzhen Finance, Hong Kong (China), Chengdu, North America, or West US. Queue name: Custom.
HTTP callbacks	When calling the event notification configuration API TaskNotifyConfig, specify the NotifyType parameter to URL and fill in the HTTP callback address in the NotifyUrl parameter.