Page tree
Skip to end of metadata
Go to start of metadata

The fully automated media asset transcoding process gives the customer the tools to ingest, process and transcode a large number of media assets and, if necessary, upload them into external storage for use in other media platforms like IPTV.

Setup

In order to prepare the automated process, there are several things to configure.

  1. Setup transcoding presets.

    Set up a transcoding preset for each different content type depending on input parameters and output renditions. Check all transcoding preset settings to determine which different variations of these you have in your source content and what output variations you need.

  2. Setup media ingest profiles.

    Set up an ingest profile for each different content type and output option set, and assign transcoding preset for each ingest profile. You will definitely need a separate profile for each transcoding preset, perhaps even several profiles per preset. Check all media ingest profile settings to determine which different variations of these you have in your source content and what output variations you need.  You will need to set how the transcoding process is triggered. Also, you may want to set up file naming patterns if they differ from the system defaults. To upload the resulting files into an external system, set up the destination storage parameters. You can also set up the retention policy to delete the files after they are transcoded and uploaded to the external system.

  3. Setup media categories.

    Edit category list in the right column of the Media section and assign an ingest profile to each category. There is one ingest profile per category possible.

Workflow

In order to transcode the content in the automated process, you have to ingest the content into the Video Cloud FTP server. Your FTP user name is slightly different from the web portal user name which is typically an e-mail. You can see the FTP username in the password change dialog box. Alternatively, you can use media ingest API function for automated ingest.

When ingested via FTP server, the files are grouped into media assets according to the assetID field in the media asset file name. All video, audio, subtitles and data files with identical assetID ingested into a particular category are grouped into the same media asset. You can find them in the Source Files tab of media asset edit page.

During the transcoding process, media assets are processed one by one in the order set when the criteria for automated transcoding are met. Either it is the timed delay or XML manifest validation, the first asset ready for transcoding goes first into the processing. The transcoding queue is listed in the Media section when Transcoding Queue selector is clicked. The transcoded files are listed in the Transcoded Files tab of media asset edit page.

If the upload configuration is set in the media ingest profile, the uploadable files are put into the upload queue and processed in the first come, first serve order. Uploads with errors are retried several times.