Pipelines Resource

The Pipelines resource allows to set up templates that define the exact path that data belonging to a job will take when being processed by the Xvid MediaHub service. This includes the flow from the input location (from where should the input files be taken from?), to the transcoding process (what queue type or notifications should be used during the conversions?) to the output location (where shall the converted output files be put up?).

A pipeline is comprised of a related internal storage folder (which serves as input and output queue to the transcoder) and the processing pipeline (which is the module transcoding the input data and producing the actual converted output files). The pipeline can be visualized as follows:

The pipeline resource allows to define remote locations from where to download input files first or where to upload the converted output files to. It also allows setting the time for how long converted ouput files should be stored on the internal MediaHub storage (so should the files be stored just temporarily? Or be permanently archived to be suitable for hosting and streaming via the MediaHub built-in CDN capability?). Pipelines further allow configuring to where notifications should be sent upon different stages of the media transcoding process.

Currently, we support just one queue type for the pipelines: "default", which is a best-effort pipeline without special SLAs.

New input files uploaded to the store or converted output files remain stored for 7 days on the store by default, then they'll get automatically pruned. Copies in the pipeline store of the input and output files that got fetched from a remote location and/or are uploaded to a remote location as part of the conversion will get pruned immediately upon successful completion of a job. 


Available Methods

  • No labels