Normalizing audio in VPX(8) and MEP, EBU R128 transceiver standard

browj2 wrote on 2/15/2017, 2:18 PM

A while back there was a thread about the problem of getting decent audio volume output for television in an older version of Movie Edit Pro (MEP).

The best way is to first normalize all of the audio, but I have had problems with some audio, in particular that recorded by me in VPX to dub into my project. Normalizing does not always give me the same overall level. For example, I select "Normalize after recording" in the parameters and record 30 seconds of speech. Then I record 5 seconds, still with Normalize set. The latter comes out much louder than the former, and I often end up having to adjust the volume of individual clips downwards. So, I am looking for a solution to this. Maybe using EBU instead is the answer.

The VPX manual defines Normalize (maximum level) as:

The function "Normalize" raises the level of an audio object to the maximum possible level without clipping the material. This searches for the largest signal peak in the audio material and raises the level of the object so that this position matches exactly 0 dB (maximum overdrive).

This is usually too loud and should be reduced overall at the mastering stage. But the problem for me is the difference between recordings even after normalizing.

VPX has a new normalize feature called "Normalize (EBU R128)" defined as:

EBU R128 is a transceiver standard that normalizes the audio signal to -23 LUFS (loudness units relative to the digital full level). Unlike normalizing to the maximum level, this provides enough upward space for temporarily loud signals. This is used, for example, by cinema productions and classical recordings.

I tried this on a loud video clip. First I used Normalize and there was no change, presumably because it was already peaking. Undo. Then I used Normalize EBU R128 and this reduced the level quite a bit as expected.

Then I did a couple of recordings, with and without checking Normalize after recording. Without using Normalize after recording, the volume was low and checking the volume level line with the mouse shows 0 db. If I now Normalize (Alt+N), the level line goes way up and I can see this visually. Recording after selecting the Normalize after recording checkbox, the level is boosted to have the loudest part output at 0 db, but checking the level of the object with the mouse shows 0 db not the same as it does if you normalize manually afterwards.

1. Is this what others get?

2. Is this really the way it is supposed to work, or is there a error in the program such that the normalize level is not shown in the latter case?

On to EBU R128. For objects that have parts that go up to (or get clipped) 0 db, this gives me a lower level. I noticed that it can be used on normalized object to get a lower level.

However, the message below popped up after selecting only one object and applying EBU:

  

I'm not sure exactly what this means. I have not checked this carefully, but it lowered the volume of the selected clip but I didn't notice if it stopped other objects from clipping.

3. Can someone please check this? And maybe describe better what the message means and what happens by accepting Yes.

4. I noticed that there is a minimum length for properly using EBU. Any idea what that minimum length is?

I thought that the level of the object after recording would show up somewhere on the screen other than clicking the mouse button on the level indicator. I looked under effects, general and saw nothing.

5. Is there some other way to see (easily) the overall level of an object? 

6. Is the best way to take care of the recording levels issue to not use "Normalize after recording" and instead apply EBU everywhere?

7. Out of curiosity, is this feature also available in MEP2017 Plus/Premium?

Thanks,

Last changed by browj2 on 2/15/2017, 2:19 PM, changed a total of 1 times.

John C.B.

VideoPro X(16); Movie Studio 2024 Platinum; MM2025 Premium Edition; Samplitude Pro X8 Suite; see About me for more.

Desktop System - Windows 10 Pro 22H2; MB ROG STRIX B560-A Gaming WiFi; Graphics Card Zotac Gaming NVIDIA GeForce RTX-3060, PS; Power supply EVGA 750W; Intel Core i7-10700K @ 3.80GHz (UHD Graphics 630); RAM 32 GB; OS on Kingston SSD 1TB; secondary WD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB, 8TB; three monitors - HP 25" main, LG 4K 27" second, HP 27" third; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer.

Notebook - Microsoft Surface Pro 4, i5-6300U, 8 GB RAM, 256 SSD, W10 Pro 20H2.

YouTube Channel: @JCBrownVideos

Comments

johnebaker wrote on 2/15/2017, 4:22 PM

Hi John CB

Did you see this article published by the EBU ?

AFAICS the issue with the mouse level showing 0dB is because using the 'Normalise after recording' option adjusts the levels before the audio is added to the track - therefore the object normalisation knows nothing about what has been applied.

Object normalisation is an independent function from the recording one.

. . . . is this feature also available in MEP2017 Plus/Premium? . . . .

AFAICS it is not available yet.

In point 2 . . . . I didn't notice if it stopped other objects from clipping . . . .

It does not - both types of normalisation apply to the selected object(s) only, treating them independently of one another.

. . . . Is the best way to take care of the recording levels issue to not use "Normalize after recording" and instead apply EBU everywhere? . . . .

After 'Normalize after recording' you would still have to apply the EBU R128 method to ensure consistency of all the sound levels of audio objects and audio from the video.

. . . . I noticed that there is a minimum length for properly using EBU. Any idea what that minimum length is? . . . .

5 seconds.

One thing that I think is missing is global EBU R128 normalisation which ought be a seperate tab in Effects, Movie Effects or in the Mixer, Master effects

HTH

John EB

Last changed by johnebaker on 2/15/2017, 4:24 PM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.