< Previous | Contents | Next >
Predetermined Dolby Atmos Master Rules
The first ten tracks in every Dolby Atmos Master are assigned as a bed by default. From there the default bed is a 7.1.2 bed, however, it can be designated to a 2.0 up to the 7.1.2 bed. There is no option to add objects to these first ten tracks. Starting at track eleven, the tracks that follow can then be made into various beds or objects as needed.
A simple way to think of this is that buses routed to the Atmos Master are treated as beds, carrying predefined multiple sources. An Atmos bed is a fixed surround format that can contain height channels. Objects, are generally mono but can send any format track that DaVinci Resolve supports and follow the metadata as a single object element. Objects routed to the Atmos Master are treated as tracks, carrying dynamic audio content and positional metadata. LFE will need to be sent to a bed, since objects are positional metadata. If the object is 5.1 for example, the LFE channel will need to be routed to a Bed bus in order to be rendered in the Atmos master.
The Dolby Renderer will render the file if it is dragged from the Media Pool into a track in the Timeline. In this case it will render the media with the embedded metadata to the master’s output format. This is a simple way to monitor pre-mastered content and to perform simple actions, such as trimming or syncing for new packaging and deliverables.
When importing a Dolby Master file from the Fairlight menu, Fairlight > Immersive Audio > Import Master File, the resulting import will extract all of the audio and metadata for further content creation. This type of importing into Fairlight maps all of the metadata, tracks, beds, and objects from the master file into the Timeline, allowing you to adjust, process, and manipulate further, to rewrite panning, punch-in and add new media, and create a new Atmos Master.
Dolby Atmos files are a package of items. Simply linking files will not create an Atmos Master file. It is not possible, for instance, to take a rendered set of twelve tracks, link them, and then configure their outputs to a 7.1.4 Atmos bed. Note that 7.1.4 is not a Atmos bed type. Although this is the way typical PCM audio is linked and routed, it is not the case for Atmos content, which is far more than just a collection of tracks.
NOTE: As mentioned above, the LFE can only be rendered in an Atmos master when routed as part of a bed due to the Dolby Atmos specification.
NOTE: As mentioned above, the LFE can only be rendered in an Atmos master when routed as part of a bed due to the Dolby Atmos specification.
NOTE: As mentioned above, the LFE can only be rendered in an Atmos master when routed as part of a bed due to the Dolby Atmos specification.
The renderer takes the 128 channels consisting of the beds and objects and renders it. Those channels are either internal sources or contained within the master file. A simple linked file will not play back through the Renderer. It must be played back as all linked files in Fairlight do, through the native monitor. The Dolby Atmos Renderer plays, renders, and extracts Atmos Master files. Fairlight allows for .atmos, ADM, and IMF file types to be imported and played through the Renderer.
Dolby Atmos Integration
There is native Mac M1 and Linux support for the internal Dolby Atmos workflow including:
— Input
— Content creation
— Internal renderer
— Export of Dolby Atmos Master Files