I’m exporting some ADM masters with Nuendo 14 and there’s a significant difference in terms of LUFS between those detected by Nuendo’s internal render and those detected by the Dolby render. What is this due to? Is it a bug needed to fix?
Can you give more info on how you are measuring, what it is, which settings? Some screenshots are helpful.
How significant? Also what version of the Dolby renderer are you using? I know that around v5.3 there were changes in the Dolby renderer in how loudness was measured.
Dolby source with table for change/versions/hosts:
This is a known thing. I’ve done over 50 Atmos mixes lately and only 2 did not measure the same between N14 and the stand alone Dolby renderer.
So is it better to mix with the external renderer? I assume the major labels will use the official Dolby one for their checks.
In the last album I mixed, there was about a 1 LUFS difference — that’s not a small amount!
1LU is not that much though in terms of perception. If you’re mixing music and it’s being streamed the platforms will probably normalize it anyway so I wonder if it really makes a difference. Heck, even for broadcast some markets have +/-2 units of acceptable variation.
Whether or not you consider it a big difference it is just strange because LUFS are statistical numbers and have specific weighting’s for specific sounds.
I’m not too familiar with Atmos delivery lufs specs , but I wonder: is this is a fixed offset for every mix? Or is it different everytime?
I have an issue with the external DAR reporting overs in the meters when it is well under -1 in Nuendo (no evidence). What’s up with the DAR metering??
Last update. I updated Dolby Renderer to the latest version 5.3.1, and now everything is consistent. The internal render values in Nuendo match those of the Dolby Renderer.
I can therefore close the thread
So was it the external renderer causing issues or is there an update to 14 I do not know about?