Forum Post

Dolby Atmos Renderer 5.4.1 crashes immediately on start with macOS Tahoe
Exactly as the topic tole says, Dolby Atmos Renderer 5.4.1 crashes immediately on launch with macOS Tahoe 26.5.2. Won't load at all, no error code presented. Any ideas on a fix?

  • Heesuk S (Dolby Laboratories)

    Sorry you are encountering the issue.

    Can you provide a bit more information?:

    - Mac model and hardware specifications
    - DAR crash logs (Navigate to Help > Export Logs, and attach the exported log file if possible)
    - Audio hardware/interfaces in use
    - Any plug-ins being used
    - Any specific behavior that consistently causes DAR crash
    - The macOS crash logs associated with the Renderer crash
    - A list of your Core Audio devices. (Open Terminal and run: system_profiler SPAudioDataType)

    One thing worth noting is that macOS Tahoe introduced some Core Audio changes that can affect sample rate handling, and the Dolby Atmos Renderer is particularly sensitive to sample rate changes. If a device being used by DAR unexpectedly changes sample rate or reports an incorrect rate, it can sometimes cause the Renderer to crash during launch.

    Best,
    Heesuk
    Expand Post
      • Heesuk S (Dolby Laboratories)

        Hi,

        Thanks for following up. I checked on my side and I don't see any email. Could you clarify where you sent the information? Also, I'd appreciate it if you could post the requested information and attachments directly here in this thread. My apologies if my earlier message wasn't clear. Thank you!

        Best,
        Heesuk
  • yes it says "view answer or reply to this mail" so I replied to the email.

    Here's the information requested:


    Model - MacBook Pro M2 Max / 32gb

    DAR crash logs - I can’t open the app, so I can’t open the help menu, but log attached

    Interface is any attached, currently UAD Apollo

    Crashes without any plugins being used or DAW even open

    Behavior causing crash is to try to launch the renderer

    MacOs crash log - attached



    ------------
    Core Audio Devices:

    Audio:

    Devices:

    MacBook Pro Microphone:

    Default Input Device: Yes
    Input Channels: 1
    Manufacturer: Apple Inc.
    Current SampleRate: 44100
    Transport: Built-in
    Input Source: MacBook Pro Microphone

    MacBook Pro Speakers:

    Default System Output Device: Yes
    Manufacturer: Apple Inc.
    Output Channels: 2
    Current SampleRate: 44100
    Transport: Built-in
    Output Source: MacBook Pro Speakers

    Dolby Audio Bridge:

    Input Channels: 130
    Manufacturer: Dolby
    Output Channels: 130
    Current SampleRate: 48000
    Transport: Virtual
    Input Source: Default
    Output Source: Default

    iPhiz Microphone:

    Input Channels: 1
    Manufacturer: Apple Inc.
    Current SampleRate: 48000
    Transport: Unknown
    Input Source: Default

    Immerse Audio Bridge:

    Input Channels: 32
    Manufacturer: Embody
    Output Channels: 32
    Current SampleRate: 48000
    Transport: Virtual
    Input Source: Default
    Output Source: Default

    Pro Tools Audio Bridge 16:

    Input Channels: 16
    Manufacturer: Avid
    Output Channels: 16
    Current SampleRate: 48000
    Transport: Virtual
    Input Source: Default
    Output Source: Default

    Pro Tools Audio Bridge 2-A:

    Input Channels: 2
    Manufacturer: Avid
    Output Channels: 2
    Current SampleRate: 48000
    Transport: Virtual
    Input Source: Default
    Output Source: Default

    Pro Tools Audio Bridge 2-B:

    Input Channels: 2
    Manufacturer: Avid
    Output Channels: 2
    Current SampleRate: 48000
    Transport: Virtual
    Input Source: Default
    Output Source: Default

    Pro Tools Audio Bridge 32:

    Input Channels: 32
    Manufacturer: Avid
    Output Channels: 32
    Current SampleRate: 48000
    Transport: Virtual
    Input Source: Default
    Output Source: Default

    Pro Tools Audio Bridge 64:

    Input Channels: 64
    Manufacturer: Avid
    Output Channels: 64
    Current SampleRate: 48000
    Transport: Virtual
    Input Source: Default
    Output Source: Default

    Pro Tools Audio Bridge 6:

    Input Channels: 6
    Manufacturer: Avid
    Output Channels: 6
    Current SampleRate: 48000
    Transport: Virtual
    Input Source: Default
    Output Source: Default

    Realphones System-Wide:

    Input Channels: 2
    Manufacturer: dSONIQ
    Output Channels: 2
    Current SampleRate: 48000
    Transport: Virtual

    Universal Audio Thunderbolt:

    Default Output Device: Yes
    Input Channels: 34
    Manufacturer: Universal Audio
    Output Channels: 46
    Current SampleRate: 44100
    Transport: Thunderbolt
    Input Source: Default
    Output Source: Default

    Pro Tools Aggregate I/O:

    Input Channels: 1
    Manufacturer: Apple Inc.
    Output Channels: 2
    Current SampleRate: 44100
    Transport: Unknown
    Input Source: Default
    Output Source: Default

    LoomAudioDevice:

    Input Channels: 2
    Manufacturer: Loom
    Output Channels: 2
    Current SampleRate: 48000
    Transport: Virtual
    Input Source: Default
    Output Source: Default

    PT Loopback:

    Input Channels: 2
    Manufacturer: Rogue Amoeba Software, Inc.
    Current SampleRate: 48000
    Transport: Virtual
    Input Source: Default
    Expand Post
    • macOS Crash Log
    • Heesuk S (Dolby Laboratories)

      Thanks for providing details.

      Could you please make sure you’re running the latest UAD software? If not, please follow the instructions here:
      https://help.uaudio.com/hc/en-us/articles/41351505627028-UAD-Software-Compatibility-with-macOS-Tahoe-26

      Also, I would recommend to update iLok components: Install the latest iLok License Manager -> Reboot the Mac ->Test DAR again.

      If the issue persists, please try disconnecting the Apollo and testing DAR using only the built-in macOS audio devices. You can also temporarily disable your virtual audio devices (especially, Realphones System-Wide, LoomAudioDevice, PT Loopback, and Immerse Audio Bridge) by moving them out of:
      /Library/Audio/Plug-Ins/HAL

      Then add the drivers back one at a time and test after each one to determine whether a specific virtual audio device is contributing to the issue.

      I'd also ensure that all active audio devices are set to 48 kHz.

      Please let me know the results by replying to this thread.

      Best,
      Heesuk
      Expand Post