Fairlight Loudness Scan

Those 8-10 films are just stems you need to sum and measure or they're including the stereo mix files?

These are complete films: Video + Audio, 5.1, 2.0 matrix, 2.0, language versions. That's different.

Movies are delivered to different countries with different sound standards on different platforms: Cinema (not all cinemas want DCP), television, VOD platforms. It's different too.

The work on the film does not end with the export of the cut work. He still has to get to the viewer. This is the purpose of film distribution, which sells, repairs, censoring for non-democratic countries, changes distribution logos, adds language versions, subtitles, captions, archives, etc. etc.

My personal record is 14 movies delivered per day.

Yes, I'm aware of how the film industry works.

I was asking if you need to sum stems together or if you're rendering out to the various platforms based on already created mixed files. In the latter case you would have one 5.1 file as opposed to several 5.1 files comprising dialog, music and effects (and possibly more).

If the summing hasn't been done and you're summing stems then the potential workload is massive if you get any loudness deviations on several of them. I mean, I assume you're the one remixing within Fairlight to get to spec in that case, right?

I was asking if you need to sum stems together or if you're rendering out to the various platforms based on already created mixed files. In the latter case you would have one 5.1 file as opposed to several 5.1 files comprising dialog, music and effects (and possibly more).

If the summing hasn't been done and you're summing stems then the potential workload is massive if you get any loudness deviations on several of them. I mean, I assume you're the one remixing within Fairlight to get to spec in that case, right?

We don't like working with stems (dialogue, M&E, etc.), but sometimes it's necessary. If the producer does not have a complete mix or if we are repairing the corrupted sound, the stems are very useful.

I like using Fairlight for repair of sound, but I use a lot of third-party (mainly) mastering plugins - Nugen, Waves, iZotope, etc.

PS: Sorry about my English. Sometimes I don't understand well.

Version 18 was just released. Not all Feature Requests can be done at once, and this one didn't make the cut.

So here it is for continued voting.

Please Blackmagic do it

+1 Great idea Jim.

Fairlight already has the ability to analyze Loudness of an audio file at faster than real-time, the ability to bounce your mix to a new track at faster than real-time, and a "Loudness History" graph on the Master bus that charts your levels along the timeline. So I can't imagine there are serious technical limitations in asking Resolve to do this as a single process in the background, and then give you the graph of that loudness analysis in your timeline.

As a test, I just timed how long this takes to do manually on a 30 minute timeline. On my M1 Mac Studio Ultra It took 1 minute and 30 seconds. Here's my process:
1. On the Fairlight page, I selected: Timeline > Bounce Mix to Track: Main Bus > New Track
2. Once that's finished, I right clicked on the new audio file and selected Analyze Audio Levels
3. This gave me my Loudness, but didn't graph anything for me in the Loudness History

Having a button that lets you do all of this in the background, using your in / out points, and then graph it for you in the Loudness History would be amazing!

I don't even need it done in the background, as the process should be very quick. I just want it doable without a Bounce, giving me a readout of the values.

Adobe Audition has had this feature for years. It's an invaluable time saver.

This would be incredibly helpful, and a huge time saver

On longer edits I currently start playback with loudness history turned on and then leave it overnight to finish playing through the whole thing in real time. I then go in and see where the loudness is too loud and make adjustments

If at all possible to have it generate the loudness history graph (integrated + short term) faster than real time, that would be amazing

Short of that, one really annoying thing with the current graph is that it disappears after some time (not sure when). So if I play my edit in real time overnight, and then start editing another timeline the next day, when I come back to the really long one, sometimes the loudness history graph is gone for that timeline.

+1

Version 18.1 was recently released. Not all Feature Requests can be done at once, and this one didn't make the cut.

So here it is for continued voting.

+1

Since they added Audio Normalization on the Deliver page, I forgot about this.
I don’t know why they didn't take the opportunity to add the same scan on the Fairlight page. They updated the different standards in the menu.

We should be able to do a loudness scan on a single track and on an entire timeline, just like we can do on a single clip with "analyze audio levels" (under a right-click).

I would go even further with the scan result and add an option to highlight the areas that could be too loud if they don't match a specific target. And this can help people to have a better understanding of the audio levels during their edit in the future too, on top of being able to "fix" these parts manually.

The "audio normalization" option on the Deliver page can already identify the parts of the audio that should be normalized. It works pretty well, EXCEPT for this : viewtopic.php?f=21&t=211913
But we don't know what was part of the audio was normalized. So we can only trust Resolve to do a good job. And not introduce artifacts or problems.

I too find our current loudness tools inadequate.

Shutter Encoder will give you a clip's loudness in seconds. But seems like all the tools we have today in Resolve are realtime?