edit-icon download-icon

Workflows and media

Last Updated: Apr 16, 2018

The following describes several basic concepts and relationships for MPS to help developers better understand and use media processing service.

  • Media

    Media includes one input video/audio media file and all the relevant output file, such as transcoding/screenshots/media info/AI tags. Input files and media have a one-to-one relationship and are uniquely identified by the Media ID.

    • Media Files

      The Media Files is a collection of all media, with media being the smallest unit for media files.

  • Workflow

    Workflow is a like a factory that automates the production of media, it is uniquely identified by a MediaWorkflowId.

    Note: Media Workflow also refers to the workflow.

    • Extension matching rules

      The automatic triggering mechanism during uploading checks the file extension to avoid generating ineffective data (such as pdf, word files and other files).

      Note: API manual triggering mechaism does not check the extension.

      The files does not have the extension (file does not include extension separator “.”), or the extension conforms to the following rules:

      • 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, webm

      • Audio

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

    • Workflow running

      Each time you upload a matching multi-media file, it is triggered once. If the same multi-media file is uploaded for multiple times, multiple runnings are triggered. Each running has a unique RunId identifier.

      In addition to the automatic triggering mechanism when uploading, the workflow targets stored multi-media files in storage and also provides a manual API triggering mechanism. Each call to the API triggers a running.

    • User data

      You can enter custom user data parameters (for example, commodity IDs) each time you run. The custom user data parameters are then returned in the message notification without the need to record the absolute path of the media ID or multi-media file in the business system. Meanwhile, you can use custom user data, such as commodity IDs, to associate the business system.

Thank you! We've received your feedback.