VP13 loudness log questions

DeadRadioStar wrote on 6/18/2014, 4:46 PM
Is there an option to just get the header and the last 3 lines?
Log updated: 	06/18/2014 21:47:08

Media: 		H:\Video\Test\Untitled.veg

Log file: 	H:\Video\Test\Untitled_loud.txt



Stream: 	Audio Stream:Master

Format: 	16-bit PCM data, 2 channels @ 48000 Hz

Algorithm: 	Surround processing turned: OFF



Mom. (max): 	-14.87 (LUFS) at 00:30:53.611

Short (max): 	-18.20 (LUFS) at 00:01:36.939

Integrated: 	-24.74 (LUFS)
I have no interest in the thousands of other lines.

Also, in the above example, should I be raising the audio level a bit to get as close to -23 LUFS as possible?

Comments

musicvid10 wrote on 6/18/2014, 11:43 PM
You are using the EU standard?
Raising it 1dB is not a big difference.
DeadRadioStar wrote on 6/19/2014, 11:16 AM
Yes, EBU R128, and 1dB is hardly audible, but I'm just wondering if anyone has had something rejected because the integrated value was, say, -22dB?

My main issue though is that I'd like to see an option for thinning out the volume of data generated in the loudness log.
musicvid10 wrote on 6/19/2014, 11:36 AM
Probably not. Don't know what the EBU tolerance is, but the US NAB Best Practices say +2dB over is OK (referenced to -24LKFS).. If you stay slightly conservative, your audio will conform to both EBU and ATSC. Be sure to keep an eye on true peak levels (does Vegas have that?).

"
Dunno. MS Word Macro, maybe?
DeadRadioStar wrote on 6/19/2014, 12:32 PM
The EBU tolerance is +/-1dB LU, so my example in the first post is actually non-compliant. The maximum true peak can't exceed -1dB. This is over the entire length of the project.

What I'm also wondering is, in the example above, in order to bring it within +/- 1dB LU, is there any more efficient workflow than just bumping the output bus "a bit" and re-running the log? I'll answer that myself: probably not in VP13 as it stands, but the ability to generate the log itself (and therefore not have to play the project in realtime) is already a huge time-saver.

I suppose I'm thinking, in the old days you could just drop a peak normaliser or a brick-wall limiter in there, and know that your peaks would not exceed the set level, but there's no equivalent "EBU R128 normaliser", at least none that I'm aware of, yet.
musicvid10 wrote on 6/19/2014, 12:49 PM
I would be surprised if the lower number is enforced. But yes, just bump the master gain a bit. Play the program twice and use the average.