Production Expert

View Original

Dolby Atmos Renderer V3.7 Released

Dolby has released the latest version of their Dolby Atmos Renderer software for the Dolby Atmos Production Suite and the Dolby Atmos Master Suite. V3.7 brings a number of improvements with the headlines being macOS Big Sur support on both Intel Macs and M1 Macs via Rosetta 2 and the Dolby Audio Bridge now able automatically clocks to output hardware eliminating the need to use an Aggregate Device to ensure proper clocking.

macOS Big Sur 11.5 Support

Dolby Atmos Renderer v3.7 supports Intel-based Macs running macOS Big Sur 11.5. with Renderer v3.7 now compatible with macOS Big Sur 11.5 on M1-based Macs (with Rosetta 2).

Please be aware that you may experience performance issues as Rosetta 2 is a translation layer between the application and the ARM processor.

Before upgrading to Renderer v3.7 on an M1-based Mac, ensure that all required drivers for audio I/O and license authentication (iLok) are M1 compatible.

Dolby Audio Bridge v2.0

The new version of the Dolby Audio Bridge now automatically clocks to output hardware. This eliminates the workaround of using an aggregate device to ensure proper clocking.

This new version of the Dolby Audio Bridge virtual driver is included in the Renderer installer package and should be selected when doing the installation.

Please be aware that v2.0 overwrites the version of the bridge included with earlier versions of the Renderer and that Aggregate Devices created with Dolby Audio Bridge v1.0 will no longer be active.

Dolby Atmos Binaural Settings plug-in v1.1

Dolby Atmos Binaural Settings plug-in v1.1 for Mac is now included in the installer as an optional install, for AAX, AU and VST 3.

The Binaural Settings plug-in now indicates unassigned objects, via a yellow outline.

Please be aware that for workflows that use the Dolby Atmos Binaural Settings plug-in, Renderer v3.7 requires Dolby Atmos Binaural Settings plug-in v1.1. Renderer v3.7 does not support Dolby Atmos Binaural Settings plug-in v1.0.0 and earlier.

MTC Support Removed

Renderer v3.7 no longer supports MTC (MIDI Time Code). Dolby recommends using linear timecode (LTC) over audio for all workflows that require synchronisation.

There are also a number of other changes…

  • In the Driver preferences, the External sync option no longer includes MTC as an option.

  • The Audio to timecode alignment window no longer includes MTC offset options. Support for Dolby LTC Generator v2.0 in multiple plug-in formats

  • Dolby LTC Generator plug-in v2.0 is required for synchronizing the Renderer to LTC over audio from a DAW on a system using the Dolby Audio Bridge.

  • Dolby LTC Generator v2.0 for Mac is now included in the installer as an optional install, in AAX, AU and VST 3 formats

  • The AAX version of Dolby LTC Generator plug-in v2.0 is contained in Pro Tools templates included with this installer.

Nuendo and Resolve have timecode generators. The Nuendo templates provided by Dolby include a track with a Steinberg SMPTEGenerator plug-in inserted on it. Depending on the DAW or plug-in format, the plug-in displays synchronisation information or provides controls for synchronisation settings.

  • For DAWs such as Pro Tools and Nuendo, which have a configurable frame rate and start time, the plug-in window provides synchronisation information.

  • For DAWs such as Ableton Live and Logic, which do not have a configurable frame rate and start time, the plug-in window provides synchronisation controls.

Important: Older Pro Tools templates containing Dolby LTC Generator plug-in v1.0 must be manually updated to use v2.0 of the plug-in.

New DAW Templates And Presets In Renderer V3.7

The Renderer v3.7 installer includes new or updated DAW templates and presets.

  • New templates: Nuendo 10.3, and Nuendo 11

  • New presets: Resolve Studio 17 Fairlight

  • Updated templates: Pro Tools and Nuendo 10

Please be aware that Pro Tools session templates using the Dolby Audio Bridge now include one track with a Dolby LTC Generator plug-in inserted on it (whether or not LTC is used from the plug-in or from external hardware.). The input/ output (I/O) settings file is configured to route the LTC over audio signal to the Renderer for synchronisation on channel 129.

Frame Rate Improvements

  • The default frame rate for the Renderer has changed to 24 fps.

  • The Renderer frame rate is displayed in the frame rate readout in the Renderer main window header, and is set in the Driver preferences.

  • A frame rate mismatch error message displays when your digital audio workstation (DAW) and the Renderer frame rates do not match. This alerts you to change either the DAW or Renderer frame rate.

Multiplexing Audio And Video When Exporting A Master To MP4

When exporting a master to MP4, you can now add a custom video file, so that you can include black video or create an MP4 file without any video. To facilitate this the Export master to .mp4 window now includes a Video section, with these options:

  • Black video - This option creates black video to match the length of the audio encode. This is the behaviour of Renderer v3.5 and earlier.

  • No video - This option creates an audio-only mp4. Use this option for audio-only playback devices that do not require black video.

  • Custom video - Use this option to embed a custom video stream in the output .mp4. The custom video input must be an mp4 with an h264 video elementary stream.

Bass Management Object Mode Removed From Speaker Preferences

The Renderer now provides one bass management mode (speaker). In Speaker preferences, the Bass management section has been renamed to Speaker bass management and the Object mode option has been removed. The Frequency setting is for speaker bass management only.

New Shortcuts For Muting Speakers In The Room Configuration Display

The Renderer main window now supports more shortcut options for muting (and unmuting) the monitor output level of one or more speakers in the room.

  • To mute one speaker only, click on a speaker icon.

  • To unmute a speaker and mute all other speakers, Cmd-click on a speaker icon.

  • To mute multiple speakers in a selected area, click-drag over one or more speaker icons.

  • To mute all speakers, Cmd-click an empty area in the room configuration.

  • To unmute all speakers in a selected area (drag rectangle), and mute all other speakers, Cmd + click-drag over one or more speaker icons.

  • To unmute all speakers, click an empty area in the room configuration.

  • To toggle the mute state of a speaker, Cmd+shift-click on a speaker.

  • To toggle the mute state of all speakers in a selected area (drag rectangle), Cmd+shift-drag over one or more speaker icons.

Status Section And Input/Master Mode Settings

In the bottom left of the main window, the Renderer provides status information when settings in the Input and Master do not match. The section provides status information for these settings: input configuration, Binaural Render mode, and trim and downmix controls.

When settings in the input differ from the settings in the currently loaded master, the settings name and an orange light display in the bottom left of the main window. When the settings match, no status is provided.

Updates For Working With Input And Master Mode Settings

The Input configuration, Binaural Render mode, and Trim and Downmix Controls windows have been updated to support displaying input and master settings, manually changing the settings, or copying settings from the master to the input, or vice versa.

With these changes, it is now possible to play a master that has a different input configuration than what you are monitoring live. The master no longer controls the input configuration, and will no longer mute objects that are being monitored but are not defined or are defined differently, in the master.

Downmix 5.1 And 5.1.x Label

The 5.1 downmix label in the Trim and downmix window has been updated to 5.1 and 5.1.x downmix to better clarify that the settings also apply to 5.1.x.

Override Master Downmix Control For Monitoring And Re-renders

By default, the settings shown in the Input page of the Trim and downmix controls window are used when monitoring the live input, and the settings in the Master page are used when playing back a currently loaded master.

You can monitor a master and produce re-renders with downmix settings that differ from the settings in the master by using the Override master downmix option (which is in the Trim and downmix controls window, Master page).

After you enable the option, you can select the 5.1 and 5.1.x downmix and 5.1 to 2.0 downmix settings that you want to use for monitoring and re-renders.

Custom Group And Re-render Names No Longer Case Sensitive

Custom group and re-render names are no longer case sensitive. This means that you cannot have two groups (or re-renders) named with the same characters, but different capitalization. For example, you cannot have SYNTHPADS and SynthPads at the same time.

System Requirements For Dolby Atmos Production Suite

The Dolby Atmos Renderer with a Dolby Atmos Production Suite license has been tested in multiple configurations. Tested CPUs, operating systems, and DAWs represent the minimum hardware and software system requirements for a Dolby Atmos Production Suite system running Renderer v3.7.

Tested CPUs

  • MacBook Pro 16,1; Intel Core i9 2.4 GHz, 32 GB random-access memory (RAM)

  • MacBook Pro 15,1; Intel Core i7 2.6 GHz, 16 GB RAM

  • Mac Pro 7,1; 8-Core Intel Xeon, 3.5 GHz, 32 GB RAM

  • Mac Pro 6,1; 6-Core Intel Xeon E5, 3.5 GHz, 32 GB RAM

  • Mac mini 8,1; Intel Core i7 3.2 GHz, 16 GB RAM

  • Mac mini 9,1; Apple M1, 16 GB RAM (with Rosetta 2)

Tested operating systems

  • macOS Big Sur (version 11.4, 11.5)

  • macOS Catalina (version 10.15.7)

Tested DAWs

  • Ableton Live - Requires the Dolby Atmos Music Panner

    • Live 10.1.9

    • Live 10.1.35

  • Apple Logic Pro - Requires the Dolby Atmos Music Panner

    • Logic Pro 10.6.2

    • Logic Pro 10.4.8

  • Avid Pro Tools Ultimate

    • Pro Tools Ultimate 2021.6

    • Pro Tools Ultimate 2021.3.1

    • Pro Tools Ultimate 2020.12

  • Resolve Studio 17

  • Steinberg Nuendo

    • Nuendo 10.3.10

    • Nuendo 11.0.20

See this content in the original post