Transcoder Configuration Files

A transcoder configuration file is an XML file containing details of the Amazon Elastic Transcoder pipelines and presets available for use with a particular publication or set of publications. A pipeline is a queue for holding transcoding jobs, and a preset is a set of parameters defining how to transcode between two specified formats. Neither pipelines nor presets are defined in a transcoder configuration file: they must be defined using Elastic Transcoder, and are then simply referenced from transcoder configuration files. For further information, see the Elastic Transcoder documentation.

You should have already defined the pipelines and presets you are going to need in Elastic Transcoder. You use the transcoder configuration files to specify which pipelines and presets are going to be used by your publications. If all your publications are going to use the same pipelines and presets, then you only need one transcoder configuration file, and you can use the default /etc/escenic/engine/common/com/escenic/media/aws/transcode-config.xml:

1. Log in to your Content Store host as the escenic user.

2. Open /etc/escenic/engine/common/com/escenic/media/aws/transcode-config.xml for editing.

3. Edit the file to make use of the Elastic Transcoder pipelines and presets you have defined. For further information see Example Transcoder Configuration File and transcoder-service.

If, on the other hand, your publications have different transcoding requirements, you may need to create several different files. Copy the supplied transcode-config.xml as many times as required, for example:

1. Log in to your Content Store host as the escenic user.

2. Copy the supplied transcode-config.xml as many times as required, for example:

   $ cd /etc/escenic/engine/common/com/escenic/media/aws/transcode-config.xml
   $ cp transcode-config.xml transcode-config-dailynews.xml
   $ cp transcode-config.xml transcode-config-entertainment.xml

3. Edit all the files to make use of the Elastic Transcoder pipelines and presets you have defined. For further information see Example Transcoder Configuration File and transcoder-service.

4. Make sure that the files you create are correctly referenced by the transcoder configurations in your common configuration (see DefaultTranscoderConfig.properties). Check the serviceDefinition property in your DefaultTranscoderConfig.properties file and make sure it correctly references your default transcoder configuration file (transcode-config.xml). Similarly, check any copies that you have made of DefaultTranscoderConfig.properties and make sure that their serviceDefinition properties point to the correct transcoder configuration files (transcode-config-dailynews.xml or transcode-config-entertainment.xml, for example).