Quick Start

You don't necessarily need to carry out all the configuration tasks described in this chapter in order to get the Video plug-in running. The following list describes the fastest route to a working media production line.

  1. Copy example configuration files to your common configuration layer as described in Common Configuration Layer Set-up.

  2. Edit /com/escenic/storage/filesystems/VideoFileSystemConfiguration.properties as described in VideoFileSystemConfiguration.properties.

  3. Edit /com/escenic/storage/filesystems/KeyframeFileSystemConfiguration.properties as described in KeyframeFileSystemConfiguration.properties.

  4. Edit /com/escenic/storage/Storage.properties as described in Storage.properties.

  5. Edit /etc/escenic/engine/common/com/escenic/media/aws/DefaultTranscoderConfig.properties as described in DefaultTranscoderConfig.properties.

  6. Edit /etc/escenic/engine/common/com/escenic/media/services/AWSClient.properties as described in AWSClientConfig.properties.

  7. If you will be producing HLS video (see Using HLS Video Presets), then you may also want to edit /etc/escenic/engine/common/com/escenic/media/services/AWSClientService.properties as described in AWSClientService.properties.

  8. Edit /etc/escenic/engine/common/com/escenic/media/aws/transcode-config.xml as described in Transcoder Configuration Files.

  9. Edit /etc/escenic/engine/common/com/escenic/media/aws/preview/PreviewTranscoderConfig.properties as described in PreviewTranscoderConfig.properties.

  10. Add media content types to your publication content-type resources as described in Defining an AWS (Internal) Video Content Type and Defining an Internal Audio Content Type. You only need to create content types for the media you are interested in (that is, if you are not interested in audio content, then you don't need to create an audio content type).

  11. If you will be using CUE to work with video or audio content instead of or alongside Content Studio, then you need to configure your SSE Proxy as described in SSE Proxy Set-up.

This quick-start configuration will give you an installation that:

  • Uses the same transcoder configuration for all publications

  • Uses S3 for storing transcoded media files, not Amazon CloudFront

If this does not meet all your requirements, then you will need to edit some additional configuration files, as described in the following sections.