When workflows can not meet user requirements, users need to judge their business logic and use the API to submit transcoding tasks. For example, not all videos require transcoding; and different videos need different transcoding configurations.
Customizes business logic and flexibly submit transcoding tasks.
Supports powerful functions such as transcoding, encapsulation, watermarking, supports HLS-AES128 standard encryption, editing and other functions.
Supports sending execution information to the specified message queue or message notification upon completion of the transcoding task.
Supports URL playback.
A transcoding task generates an output file that allows tasks to be submitted in batch.
API transcoding supports HLS-AES128 standard encryption. Currently, Alibaba Cloud private encryption is not supported.
API transcoding supports URL playback, but does not support media ID playback. Users need to associate multiple output of multiple definition in multiple formats to achieve the logic of automatic switching between different definition and supporting multiple formats.
Custom transcoding template (as needed), log on to the Media Processing cosole for configuration.
Custom watermark template (as needed), log on to the Media Processing cosole for configuration.
Upload input files to OSS (Multiple upload options: OSS console, OSS related uploading tools and upload SDK).
After getting the message, call the “QueryTranscodingJob” interface to query the task execution result and get the output file URL.
Download JAVA source code.