User16843053553316314926 (Customer) asked a question.
How to Uninstall - Reinstall The Dolby Atmos Renderer 5.0 in Mac OS Ventura
Pro Tools 2023.3 and the Renderer are having a problem syncing when I boot my system. As a troubleshooting step I'd like to completely uninstall the Dolby renderer and do a clean install. Is there a list of what files I should delete before doing the clean install? I'm on a Mac running MacBook Pro Max running OS Ventura.
Thanks,
Joe
Thanks,
Joe
See the list below. However, before going that route can you explain the sync issue you are seeing and also describe what is set as the playback engine or if you are using Aux I/O etc.
Thanks,
Adam
Renderer folder and Plug-ins docs
• /Applications/Dolby/
Application
/Applications/Dolby/Dolby Atmos Renderer
• Dolby Atmos Renderer.app
• Dolby Atmos Renderer Remote.app
Documentation
/Applications/Dolby/
• Documentation
• Dolby LTC Generator
• Dolby Atmos Music Panner
• Dolby Atmos Binaural Settings
Supporting Folders
Backups, Binaural Configurations, HeadphoneEQs, headtracking, enablements file, persistence.db and persistence_r.db databases
• /Users/xxx/Library/Application Support/Dolby/Dolby Atmos Renderer
Plug-ins and Renderer Log files
• /Users/xxx/Library/Logs/Dolby/Dolby Atmos Renderer
sh and dylib files
• /Library/Application Support/Dolby/Dolby Atmos Renderer
Renderer.plist and Remote.plist files
• /Users/xxx/Library/Preferences/
o com.dolby.atmos.remote.plist
o com.dolby.atmos.renderer.plist
o com.dolby.Dolby Atmos Renderer Remote.plist
o com.dolby.Dolby Atmos Renderer.plist
DAB ASP 2.0
/Library/Audio/Plug-Ins/HAL/dab-asp.driver
Plugins
Components
/Library/Audio/Plug-Ins/Components
• Dolby Atmos Binaural Settings.component
• Dolby Atmos Music Panner.component
• Dolby LTC Generator.component
VST3
/Library/Audio/Plug-Ins/VST3
• Dolby Atmos Binaural Settings.vst3
• Dolby Atmos Music Panner.vst3
• Dolby LTC Generator.vst3
AAX
/Library/Application Support/Avid/Audio/Plug-Ins
• Dolby Atmos Binaural Settings.aaxplugin
• Dolby Atmos Music Panner.aaxplugin
• Dolby LTC Generator.aaxplugin
Plugin Presets
AAX DABS Preset
/Users/xxx/Documents/Pro Tools/Plug-In Settings/Dolby Atmos Bina
• Default 7.1.2 configuration.tfx
VST and AU Default DABS presets
/Users/xxx/Library/Audio/Presets/Dolby Laboratories/Dolby Atmos Binaural Settings
• Default 7.1.2 configuration.aupreset
• Default 7.1.2 configuration.vstpreset
Pro Tools
DAMP Templates
/Users/xxx/Documents/Pro Tools/Session Templates/Dolby Atmos Music
• Dolby Atmos Music Panner 64 Channel.ptxt
• Dolby Atmos Music Panner 128 Channel.ptxt
.pio IO Settings
/Users/xxx/Documents/Pro Tools/IO Settings
• Dolby Atmos Music Panner.pio
Thanks for getting back to me. I’m having a problem where it can be difficult to get Sync to lock up between Pro Tools and the Dolby Renderer.
On rare occasions it I get sync lock right away but other times I need to wake it up by changing some settings in the renderer and it will then lock.
The one that seem the most effective for me is to go into the Renderer’s Advanced settings and change the LTC offset by a sample. This will sometimes “wake up” the sync.I then can go back in and set
Th offset to zero and all is good. It seems that anything that causes the render to update can sometimes get things working.
Once the sync locks it stays locked until the next reboot or shutdown. I can quit either or both Protools and the renderer and open them again and everything works as expected.
One of my production partner’s in LA has a very similar setup to mine and he is having the same problem but with him the only thing that works is to open Pro Tools and the renderer and wait about 15 minutes and then everything work, again until a reboot or shut down.
We are both running the latest versions of Protools and the renderer I’m on a MacBook Pro Max and he is on A Mac Studio Max.
We both are using UAD Apollos for playback only using AUX I/O for the Dolby Audio Bridge.
Here are some screen shots for you to look at.
Thanks again for your time!
Joe



We've been going around this issue for a while with a number of studios and Avid.
Aux I/O is a great solution for some use cases including simple Atmos monitoring in a single machine setup. However, with Aux I/O there is inherent latency and indeterminacy. If this presents a problem to the required workflow, then the Renderer should be clocked to external hardware.
The most stable scenario for using the Aux I/O with the Renderer is set the playback engine to HDX. Create an Aux I/O output using the Dolby Audio Bridge, set the input to the Renderer as the Dolby Audio Bridge and the output as the Pro Tools Audio Bridge with the minimum number of channels needed for monitoring and re-renders. In this scenario both virtual audio devices sync from Pro Tools. My understanding is that the latency may change between launch but should be consistent once running.
For an more stable option that locks the Renderer to the hardware output devices, set the playback engine to the Dolby Audio Bridges, set the input to the Renderer as the Dolby Audio Bridge and output as the Apollo.
Tweaking the LTC offset amount to wake things up is more a symptom than a solution. If monitoring through the Renderer with the Apollo as the output device isn't a signal flow you can work with I'd suggest getting in touch with Avid support as the behavior of the Aux I/O is outside our purview.
Hope this helps.
Best,
Adam
Both of us are running Pro Tools natively without any HDX cards.
Is there a similar setup that can be done without an HDX in the chain?
I really appreciate your help,
Joe
Yeah. HDX doesn't need to be part of the picture. I'd still suggest trying to use the Dolby Audio Bridge as the playback engine and the Apollo as the output device for monitoring directly via the Renderer to see if that addresses the issues you are seeing.
Best,
Adam