The settings for the storage of the videos have been overhauled dramatically. The settings have been made more generic, possibly allowing the module to work with all kinds of stream wrappers without changes.
Both FFmpeg and Zencoder are affected.
The new settings are located at the field settings form. Previously, there was just one Upload destination field, which was used for the original file, the converted file and thumbnails. However, for FFmpeg this did not work at all, because FFmpeg can't work with remote files. For Zencoder, there was an additional site-wide setting at the Transcoder settings page which also played a role in determining the destination of files.
The changes
- The Zencoder generated thumbnails are all downloaded when the postback arrives and saved to the selected destination.
- No output directory is sent to Zencoder. The converted videos and thumbnails are stored temporarily on an S3 location provided by Zencoder and moved to the desired location by the postback handler.
- The site-wide Zencoder base URL and "use full path" settings are gone.
What you need to do
Revisit all your video fields and configure the three new settings:
- Upload destination of original file
- Upload destination of converted files
- Upload destination of thumbnails
Setting #1 is initialized to the old "Upload destination" setting, but #2 and #3 are initialized to Public. Change this if you want to use, for instance, S3.
Advice for FFmpeg users
FFmpeg needs a local copy of your video to transcode it. Storing the original file remotely is kindly discouraged. Every time FFmpeg is invoked to generate thumbnails or transcode files, the whole video is copied to the temporary directory before it is transcoded. This is wasteful and does not happen when the original files are available locally.
