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.
To prepare the automated process, there are several things to configure.
- 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.
- Setup media workflow profiles.
Set up a workflow profile for each different content type and output option set, and assign a transcoding preset for each workflow profile. You will definitely need a separate profile for each transcoding preset, perhaps even several profiles per preset. Check all media workflow 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.
- Setup media categories.
Edit category list in the left column of the Media section, then assign a workflow profile to each category. There is one workflow profile per category possible. Also, the transcoding priority level can be set.
To transcode the content in the automated process, you have to ingest the content into the Video Cloud FTP server or use the Upload manager in the browser. 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 dialogue box. Alternatively, you can use the media ingest API function for automated ingest.
When ingested via an FTP server or Web upload manager, 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 Files packages tab, Source package of the media asset edit page. You can add, for example, new text-based subtitles to the transcoded asset without re-transcoding by clicking Actions → Update subtitles from source or choose the re-transcode option in Workflow profiles for automatization.
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. Set transcoding queue priority to the media category to maintain different transcoding queues, e.g., prioritizing the fresh content over a large back-catalogue library. The transcoding queue is listed in the Media section when the Transcoding Queue selector is clicked. In this list, you can prioritize transcoding order for one asset and see the progress. The transcoded files are listed in the File packages tab, in base or other user packages of the media asset edit page. See the full report of the transcoding workflow by opening it under Reports or also in the Media section under Transcode Queue and Upload Queue.
Upload to external
If the upload configuration to any destination is set in the media workflow 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.