All Products
Document Center

FAQs in on-demand scenario

Last Updated: Jul 04, 2020

What audio input formats does MPS support? And what output formats does MPS support?

Input formats MPS supports

  • Container format

    3GP, AVI, FLV, MP4, M3U8, MPG, ASF, WMV, MKV, MOV, TS, and WebM

  • Video encoding formats

    H.264/AVC, H.263, H.263+, MPEG-1, MPEG-2, MPEG-4, MJPEG, VP8, VP9, Quicktime, RealVideo, and Windows Media Video

  • Audio encoding formats

    AAC, AC-3, ADPCM, AMR, DSD, MP1, MP2, MP3, PCM, RealAudio, and Windows Media Audio

Output formats MPS supports

  • Container formats

    Video transcoding: FLV, MP4, TS, M3U8, and GIF

    Audio transcoding: MP3, MP4, OGG, and FLAC

  • Video encodng formats

    H.264/AVC and H.265/HEVC

  • Audio encoding formats

    MP3, AAC, VORBIS, and FLAC

How to upload media files?

You can log on to the MPS console or use the upload SDKs for Web, iOS, and Android to upload media files. Multipart upload, upload resuming and batch upload are supported. You can also directly use OSS client tool.

Does the system run the transcoding operation automatically after the audio files are uploaded?

The workflow is automatically triggered to run the workflow if the file under the workflow has a suffix in the specified range.

When you create a workflow, you must specify the input location of files under this workflow. When audio or video files with the following suffixes are uploaded to the input location, MPS automatically triggers the workflow, and performs operations on the input files set in the workflow.

Files with a suffix in the following range support automatic triggering of workflow execution:

  • Video

    3gp, asf, avi, dat, dv, flv, f4v, gif, m2t, m3u8, m4v, mj2, mjpeg, mkv, mov, mp4, mpe, mpg, mpeg, mts, ogg, qt, rm, rmvb, swf, ts, vob, wmv, and webm

  • Audio

    aac, ac3, acm, amr, ape, caf, flac, m4a, mp3, ra, wav, wma, and aiff

Matching rules when workflow execution is triggered:

The location of the uploaded media files includes the input location set in this workflow, and the workflow is triggered. For example,

The input location of workflow A is AA/BB directory of BucketA, and both the AA/BB/a.mp4 and the AA/BB/CC/b.flv uploaded to BucketA are triggered to run workflow A.

When the workflow is disabled , it is not automatically triggered to run.

Can videos be triggered to transcode when I use the OSS uploading tools to upload videos to the input location of the workflow?

Yes. MPS automatically triggers workflow execution according to the OSS input location of the specified workflow to which you upload video files. The uploading manner are not restricted, and you can use the MPS console, API, SDK, or OSS client tools to upload files. But when the workflow is in disabled status, the system does not automatically trigger workflow execution. For more information about uploading methods and tools, see FAQs in on-demand scenarios - How to upload media files?

What operations does workflow support?

Workflow currently supports screenshot, transcoding, template analysis, publishing management, and other operations.

How to name output files in the transcoding module of the workflow?

Workflow brings easy access to batch files processing, it also brings the problem of naming output files. For your convenience, the system offers the following variables for your selection:

  • {RunId}: Workflow execution ID.

  • {ObjectPrefix}: Original location, not including Bucket information.

  • {FileName}: Original file name, not including extension.

  • {ExtName}: Extension of the original file.

For example, when the input file is, three variables related to the original file are:

  • {ObjectPrefix}: news/video/

  • {FileName}: foooo

  • {ExtName}: .mp4

You can set output Object as vod/{ObjectPrefix}{FileName}_HD.flv, then the output Object after the input file is transcoded is vod/news/video/foooo_HD.flv

What information formats does workflow support?

Workflow supports MNS Queue and Notification of MNS, which you can set in the Transcode module. When the workflow is triggered, it sends message according to set MNS Queue or Notification when it is triggered and when it completes execution.

How to get the playback URL after the transcoding operation is completed?

You can manage the video in MPS concole > Media Fies. Click Manage at the right side of the video to go to the video details page, where you can see the OSS URL of the output file and the CDN URL. Besides, you can use the MSPS SDK coding to get the playback URL. For more information, see Media details.

Does the MNS Queue and Notification binded on MPS queues take effect simultaneously when the workflow is triggered to run tasks?

Currently execution tasks triggered by workflow neglect MNS Queue binded on MPS Queues.

Why the CDN address of the output file after transcoding cannot be previewed on the MPS console?

This is because your vod CDN domain name is not binded to the corresponding CNAME. Your can use the following command to query the CNAME setting of your vod domain name:

  1. nslookup -type=cname [Your vod domain name]

For more information about CNAME setting, see Domain name management.

Why the output M3U8 file cannot be previewed on the MPS console?

First, the Access Control List (ACL) of the Output Media Bucket must be set as Public Read.

Then, the MPS console uses the Flash player of Alibaba Cloud, you must place crossdomain.xml file in the root directory of the Bucket where the M3U8 file is located. And the crossdomain.xml must include the domain name where the player is located, or the M3U8 file cannot be played.

We recommend that you place the crossdomain.xml file with the following content in the root directory of the Bucket where the M3U8 file is located in order that your M3U8 file can be normally previewed in the MPS console:

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <cross-domain-policy xmlns:xsi="" xsi:noNamespaceSchemaLocation="">
  3. <allow-access-from domain="*"/>
  4. </cross-domain-policy>

Wherein,* is the domain name where the console player is located. If you use other Flash player, add a new allow-access-from domain record to the domain name where the player is located.