QuickTime MOV files with two MOOV atoms at Premiere Digital Services
Loudness compliance to a wide range of standards was required for a mixture of international and online delivery platforms at Premiere Digital Services. Premiere had QuickTime (QT) MOV files that had two MOOV atoms – these define different durations. Such files cannot be correctly processed by many existing tools so it was necessary to modify the files to have only a single MOOV atom.
Files containing 8 channels of audio, structured as 5.1 + stereo, were sometimes rendered as six mono streams and one stereo stream. However this format was not compatible with other tools, and so the audio had to be converted to be eight mono streams.
In this screen shot, we have selected to force a Mono stream structure for the new MOV file that will be created. This stream structure will be used regardless of the stream structure on the original source file. So in this way, you can take any mixed up file and flatten to a totally consistent structure.
Audio data in the files was either unlabelled or was incorrectly labelled for channel position. It was a requirement to stamp new position metadata in to the files. For international deliveries, there was also a requirement to stamp language metadata on to the audio tracks. Engine has the ability to insert channel layout information in to both MOV and MXF files, although the exact form of what is possible varies with metadata specifications. Here is a MOV example.
Premiere needed around 30 workflows, all of which had to be assignable to separate watch folders, so as to provide an instant automation solution. Engine watch folders are fully supported on any folders across your internal network. Watch folders containing shortcuts (alias’s, links) are also supported.
As an alternative to using watch folders, Engine has a comprehensive REST API so custom integrations can be written, or you can use existing ones, such as with Telestream Vantage or Aspera Orchestrator.