Table of Contents
Content must be accessible to both Remix and Unified Origins on the same path
Content encoding profiles should match (which it will as Capture extracts the content from the publishing point, which does not change).
Redundant setup for the ingest to prevent gaps caused by:
- encoder failures
- upstream distribution failures, e.g. satellite outage, playout issue
To ensure a continuous media timeline on which gaps in audio, video and subtitles are minimized as much as possible, Remix will insert empty subtitle cues and silent audio where necessary. However, do note that support for insertion of silent audio is limited to AAC-LC, Dolby's AC-3 and EC-3, and DTS and DTS:X (e.g., AAC-HC is not supported).
Also, when Remix decides where in the source media's timeline it should make a cut, it treats video as leading. And to make sure audio and video end at the exact same time, it may lengthen the last video sample slightly.
The order in which Remix puts tracks in a remixed MP4 is considered an implementation detail that should not be relied upon for selection of tracks from a remixed MP4.
Having said that the general order of tracks in a remixed MP4 will be as follows:
- Audio tracks first sorted by bitrate ascending
- Video tracks sorted by bitrate ascending
- Data tracks (closed captions)
However, note that other track properties like language and track kind will play a role as well.
When using a remixed MP4 as source, Unified Origin automatically signals
DASH AVC content with a codec ID of
avc3 (i.e., using in-band parameter
If this does not meet your requirements the
--no_inband_parameter_sets option can be used to switch the
codec ID to
avc1 (i.e., using out-of-band parameter sets).
This is often a requirement for SSAI workflows or legacy playback devices where the handing of or creation of media with in-band codec parameters is not fully supported.
Overall, storing remixed MP4s on remote storage should provide sufficient performance, although caching them might be worth considering: Cloud Storage Reducing Latency. However, when playlists from which remixed MP4s are generated are very long (several hours), resulting remixed MP4s become too large for Origin to perform well when fetching them from remote storage (as Origin needs to read the index from the remixed MP4 for each request it serves out). In such cases, store remixed MP4s locally or on NFS.