Unexpected behaviour with v16 loudness meters

Get answers to your questions about color grading, editing and finishing with DaVinci Resolve.
  • Author
  • Message
Offline

lucyve

  • Posts: 16
  • Joined: Mon Jul 30, 2018 10:03 pm
  • Location: USA
  • Real Name: Lucy Ventura

Unexpected behaviour with v16 loudness meters

PostThu Mar 25, 2021 6:22 pm

Hi. I do not have a broadcast background, so I might be missing something here.

Project is set to target -18 LUFS
Sequence is edited, played back, and shows Integrated of -1.0
If I nest that sequence, reset, playback Integrated shows +5.5

The dbs registering in the M1 are the same.. as is the peak in the Control Room. Why would the LU differ?

Thanks in advance.

OrigSeqCapture.PNG
Original sequence
OrigSeqCapture.PNG (166.01 KiB) Viewed 404 times

NestedCapture.PNG
Nested sequence
NestedCapture.PNG (140.34 KiB) Viewed 404 times

-- DVR 18.0.1 Studio
-- Win 10
-- Intel Core i7-11700F 2.5 GHz 8-Core
-- 32GB
-- 1TB SSD for storage/apps
-- NVIDIA GeForce RTX 3080
-- 466.77 Gameready Driver
Offline

lucyve

  • Posts: 16
  • Joined: Mon Jul 30, 2018 10:03 pm
  • Location: USA
  • Real Name: Lucy Ventura

Re: Unexpected behaviour with v16 loudness meters

PostThu Mar 25, 2021 8:28 pm

Ok, I have fixed this by cutting and pasting into a new sequence, and now the nested version behaves as I'd expect. The only thing I can think that might have caused it was that I started the project with a different target loudness level.. so perhaps the old timeline remembered the old value?

Not sure. Anyway, it's working now!

-- DVR 18.0.1 Studio
-- Win 10
-- Intel Core i7-11700F 2.5 GHz 8-Core
-- 32GB
-- 1TB SSD for storage/apps
-- NVIDIA GeForce RTX 3080
-- 466.77 Gameready Driver

Return to DaVinci Resolve

Who is online

Users browsing this forum: caleboak, dsmith1966, Google [Bot], MagicMind, panos_mts and 250 guests