Blackmagic Forum

Version: DaVinci Resolve 17.1

Hello there, I was able to display the loudness history

In the Fairlight page highlight the Automation icon and the Loudness History for the Main 1 or Bus 1, depending which sort of routing you are using, will appear.

Charles Bennett wrote:In the Fairlight page highlight the Automation icon and the Loudness History for the Main 1 or Bus 1, depending which sort of routing you are using, will appear.

Thank you, very much for your answer!

Unfortunately when following your steps I only get a green bar to view. (View screenshot in new tab)

You have to play through the timeline to get a 'history'.

The green bar shows how much of the timeline has been analyzed. This is what I see with the Loudness History in Windows. I have brightened up the Loudness History section to make it more visible. Maybe there is a bug in the Mac version.

You've only got integrated selected, that will take a few seconds to show up as it needs a minimum time window to average across. You might not be playing enough to get a reading. If you want an idea of general loudness of certain areas, check the short term box as well.

I played as a new test over 3 minutes - no history.
I checked Momentary and Short Term - no history.

Now, I will install the new 17.2 version and see, if the error persists.

Unfortunately, yes.

DaVinci 17.2 build 11, and bug persists. How to file this bug correctly?

Best, Gabriel

Hi there!

Last week I sent an email to Blackmagic via the support form, but got no answer yet. How to further progress in filing the bug?

Greetings from Berlin, Gabriel

Given this and other errors Gabriel, might be time to look at your setup.

Wanted to add, I have exactly the same behaviour, which should be reproducible with any stock M1 Mac Mini and using the DaVinci Resolve training course project: "Age of Airplanes" -> "05 Fairlight Rough Cut"

No matter what I try, I cannot get Integrated levels to appear on the graph. Momentary and Short Term are fine.

Got here after a forum search and after referring to this video (what should happen in DRv16):

I'd say this is a bug.

I had contact with Blackmagic support. The error could be reproduced, and is logged: It's 96khz.

Who else is using 96kHz? (See the SMPTE-DCP possibilities!)
You can reproduce the error by importing any 96khz audio, and then try to get a loudness history)

Report to BM and we have better chances the bug to be fixed soon!

Thank you.
Best, Gabriel