
Click AudioWorks Studios (Click audioworks studios) asked a question.
Metadata Access Conflict - Dolby Atmos Panner and Renderer
Dear all,
We have been facing new problems with Dolby Atmos Renderer and a message that says "Metadata Access Conflict".
Upon investigating this issue we found that: on the "remote clients" page there is an apparent conflict between the Dolby Enabled Workstation (Pro Tools) and the Dolby Atmos Panner Plugin. Attached are images from the problem, and our system configurations. Is there a workaround for this issue?
Hardware Overview:
Model Name: Mac mini
Model Identifier: Mac16,11
Model Number: Z1JV000KFLL/A
Chip: Apple M4 Pro
Total Number of Cores: 14 (10 performance and 4 efficiency)
Memory: 64 GB
System Firmware Version: 13822.61.10
OS Loader Version: 13822.61.10
System Serial Number: PJ760H02L1
Dolby Renderer Version: 5.5.0_3872-b53763b9
Pro Tools Version: 2025.12
Obs: Our patch is done by Omnibus, Pro Tool's playback engine is set to Dolby Audio Bridge, which sends it to renderer. The outputs of Dolby Renderer are set to Dolby Omnibus - and patched to our speakers.
If anyone could shed some light onto this we would be very glad!
Sincerely,
ClickAudioWorks
We have been facing new problems with Dolby Atmos Renderer and a message that says "Metadata Access Conflict".
Upon investigating this issue we found that: on the "remote clients" page there is an apparent conflict between the Dolby Enabled Workstation (Pro Tools) and the Dolby Atmos Panner Plugin. Attached are images from the problem, and our system configurations. Is there a workaround for this issue?
Hardware Overview:
Model Name: Mac mini
Model Identifier: Mac16,11
Model Number: Z1JV000KFLL/A
Chip: Apple M4 Pro
Total Number of Cores: 14 (10 performance and 4 efficiency)
Memory: 64 GB
System Firmware Version: 13822.61.10
OS Loader Version: 13822.61.10
System Serial Number: PJ760H02L1
Dolby Renderer Version: 5.5.0_3872-b53763b9
Pro Tools Version: 2025.12
Obs: Our patch is done by Omnibus, Pro Tool's playback engine is set to Dolby Audio Bridge, which sends it to renderer. The outputs of Dolby Renderer are set to Dolby Omnibus - and patched to our speakers.
If anyone could shed some light onto this we would be very glad!
Sincerely,
ClickAudioWorks

-Delete Object 15-16 from the Renderer tab
-Create a bus in the Bus tab and assign it to the physical output
-On the track for Object 15-16, set the output of the track to the new bus created (don't use the bed/object panel).
This process should be repeated for any objects that use the Music Panner.
-B