Improved Transcoding Control

You can achieve more detailed control over the transcoding process by making use of the information stored in an audio or video item's VDF payload document. In order to enable this functionality:

Copy /opt/escenic/engine/plugins/video/config/engine/com/escenic/video/adactus/VMEOnlineIngestXMLGenerator.properties to your common configuration layer. For example:

$ mkdir -p /etc/escenic/engine/com/escenic/video/adactus/
$ cp  /opt/escenic/engine/plugins/video/config/engine/com/escenic/video/adactus/VMEOnlineIngestXMLGenerator.properties  \
     /etc/escenic/engine/com/escenic/video/adactus/VMEOnlineIngestXMLGenerator.properties

Open your configuration file for editing.
Add the following property:
```
addContentEntry=true
```

Media files are submitted to VME Online for transcoding by sending an XML input file that contains the URL of the media file to be transcoded plus information about the required output formats. If you set this addContentEntry property to true, then the content item's VDF payload document in is included in the XML input file that is submitted to VME Online.

This option is most commonly used together with an XSL transformation specified with the adactusXslFile property in the TranscodingConfiguration.properties file (see TranscodingConfiguration.properties). The transformation you specify with the adactusXslFile property is used to modify the XML input file before it is sent to VME Online. The idea is that this transformation can use information it finds in the embedded VDF payload to modify other parts of the XML file that affect the transcoding process.