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.
-
Copy example configuration files to your common configuration layer as described in Common Configuration Layer Set-up.
-
Edit
/com/escenic/storage/filesystems/VideoFileSystemConfiguration.properties
as described in VideoFileSystemConfiguration.properties. -
Edit
/com/escenic/storage/filesystems/KeyframeFileSystemConfiguration.properties
as described in KeyframeFileSystemConfiguration.properties. -
Edit
/com/escenic/storage/Storage.properties
as described in Storage.properties. -
Edit
/etc/escenic/engine/common/com/escenic/media/aws/DefaultTranscoderConfig.properties
as described in DefaultTranscoderConfig.properties. -
Edit
/etc/escenic/engine/common/com/escenic/media/services/AWSClientConfig.properties
as described in AWSClientConfig.properties. -
Edit
/etc/escenic/engine/common/com/escenic/media/aws/transcode-config.xml
as described in Transcoder Configuration Files. -
Edit
/etc/escenic/engine/common/com/escenic/media/aws/preview/PreviewTranscoderConfig.properties
as described in PreviewTranscoderConfig.properties. -
Add media content types to your publication content-type resources as described in Defining an Internal Video Content Type.
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.