Automatically adjust all clips' volume to the same perceived level

FunkyB wrote on 2/28/2019, 2:51 AM

I've tried searching on this topic, but didn't find a definitive answer. Apologies in a advance if I missed it.

I'm trying to come up with a method to automatically adjust or flatten the volume level of all video clips on the timeline, or at least on the same track. Ideally, I'd incorporate the appropriate settings or filters into a template project. The video clips are just short clips of kids taken with smartphones and consumer grade camcorders. The source audio itself isn't bad, but the volume varies a lot depending on the situation it was taken in, and the device that recorded it. I want the final video to be consistent in volume so I don't have to reach for the remote to turn it up for quieter clips just to be blasted when someone runs up to the camera screaming in the next clip. I'm not concerned with the finer points of preserving audio dynamics and if I add music, it will be separate so that's not an issue. I have a few years worth of clips that need to be made into compilations (usually one or two for each month), so I'm looking for a "plug and chug" approach that requires a minimum of manual tweaking.

There are so many audio options in MEP that I'm not sure where to start. Normalizing alone doesn't take into account volume changes within the same clip. I tried "Adjust loudness of all selected objects", but it gives the message "The current loudness target level is causing several objects to clip. Would you like to correct the clipping automatically? (The loudness of objects in relation to one another will not be affected.)" That sounded good until the last part, because I don't mind if the relative loudness is affected.

I think I need is to use a Compressor or Limiter, but there are at least three different compressors and I don't which I should be focusing on: the one in the Audio Effects > Audio Cleaning dialog, the one Audio Effects > Audioeffects (green hexagon icon -- I'm guessing this one is more for spot emphasis than mastering), or the one in the Mixer which looks more advanced.

Sorry for the long post. Greatly appreciate any advice about how to deal with this.

 

Comments

emmrecs wrote on 2/28/2019, 6:36 AM

@FunkyB

You wrote:

Normalizing alone doesn't take into account volume changes within the same clip

Err, yes it does exactly what you say it doesn't do, unless I'm misunderstanding what you mean!! "Normalising" is the process by which ALL the audio within a clip is raised, or lowered, such that the "loudest" peaks will meet and not exceed the pre-determined threshold as set in the Normalise settings. IOW, if current loudest peak is, e.g. -6dB and the Normalise peak level is set to -1dB, all the audio within the clip will be increased by 5dB. The full dynamic range of the original will be preserved, but the perception of overall level is that it will be "louder". (One precaution: raising the level of a very quiet clip can result in a considerable rise in unwanted "noise", hiss etc. This then needs to be separately removed, not always an easy task!)

OTOH, it may be that what you actually want to do is both raise the overall level of your audio and reduce the dynamic range. In which case I would use a Compressor first and then Normalise (to bring your peak level back to what you want it to be, since compression will, almost inevitably, result in a lower peak). The former "compresses" (reduces) the overall dynamic range of the original but the settings to use depend very much on the source material; it is not possible to give precise settings without being able to hear the original. IOW, your own ears are the best guide as to which settings "work" for any particular clip. One warning: over-use of compression can lead to noise-pumping, where the background noise seems to rise and fall, potentially very unpleasantly!

HTH

Jeff

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, NVidia GTX 1660TI and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

FunkyB wrote on 3/3/2019, 2:53 AM

Thanks. Yes, that's exactly what I want to do: raise the overall level (if it doesn't already peak out at -1dB), and also also reduce the dynamic range, especially where there are big differences.. It looks like I should use both a Compressor and Normalize. I was trying to Normalize first, but I can see why it's better to apply the Compressor first, and then let Normalize set the final maximum peak level. I'll try using the Compressor in the Audio Cleaning dialog since the one in the Mixer FX would only kick in after everything else (if I understand how the Mixer works).

CubeAce wrote on 3/3/2019, 4:30 AM

@FunkyB

As Jeff tried tactfully to point out, it is not a good idea to try to do what you are doing. Batch processing, which is essentially what you are trying to do with your audio, (or video) only works well within a project when all the parameters of the recordings are the same. Mixing of takes from either different recorded sources or different times and places will mean possible fluctuating audio levels and tonal variations as all the clips will be subject to the same processing. In reality, each clip should ideally get it's own track and be individually processed through the mixer with the appropriate effects, leveling, and frequency curves applied before the final mixdown. Your ears are the best tool for the job if you know how to process each clip to get the audio to sound roughly the same as the surrounding clips. Beware of audio cleaners, they often take out just as much of what you want as they remove.

Last changed by CubeAce on 3/3/2019, 4:33 AM, changed a total of 1 times.

 

Windows 10 Enterprise. Version 22H2 OS build 19045.5011

Direct X 12.1 latest hardware updates for Western Digital hard drives.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1 Bios version 1401

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version Graphics Driver 31.0.101.2130 for 7th-10th Gen Intel® with 64GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB Evo 970 NVMe: drive for C: drive backup 1 x 1TB Sabrent NVMe drive for Operating System / Programs only. 1X WD BLACK 1TB internal SATA 7,200rpm hard drives.1 for internal projects, 1 for Library clips/sounds/music/stills./backup of working projects. 1x500GB SSD current project only drive, 2x WD RED 2TB drives for latest footage storage. Total 21TB of 8 external WD drives for backup.

ASUS NVIDIA GeForce RTX 3060 12GB. nVidia Studio driver version 560.81 - 3584xCUDA cores Direct X 12.1. Memory interface 192bit Memory bandwidth 360.05GB/s 12GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x8 Gen3. Two Samsung 27" LED SA350 monitors with 5000000:1 contrast ratios at 60Hz.

Running MMS 2024 Suite v 23.0.1.182 (UDP3) and VPX 14 - v20.0.3.180 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

VXP 14, MMS 2024 Suite, Vegas Studio 16, Vegas Pro 18, Cubase 4. CS6, NX Studio, Mixcraft 9 Recording Studio. Mixcraft Pro 10 Studio.

Audio System 5 x matched bi-wired 150 watt Tannoy Reveal speakers plus one Tannoy 15" 250 watt sub with 5.1 class A amplifier. Tuned to room with Tannoy audio application.

Ram Acoustic Studio speakers amplified by NAD amplifier.

Rogers LS7 speakers run from Cambridge Audio P50 amplifier

Schrodinger's Backup. "The condition of any backup is unknown until a restore is attempted."

browj2 wrote on 3/3/2019, 12:16 PM

Hi,

Ditto what Jeff and CubeAce said.

Audio, like video, is a science, but adjusting it is a black art. There is no automatic adjustment that will do it right. I am definitely not an expert on this, so the others may jump in here.

I use VPX, so in addition to Normalize (maximum level), we have Normalize (EBU R128) which 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.

Both are quite different, as you'll see in my example below.

Example 1:

I have 3 consecutive video clips taken with my cell phone during a walk in the woods in winter. In the first clip, there is only the sound of my footsteps and breathing, but with far away noise of traffic on the highway. In second clip, there is the same but I call the dog and talk a bit. In the third clip, same, but I call the dog more loudly. There is some clipping in the second and third clips when I call the dog.

Normalize:

Whether I select all 3 clips and normalize at once or individually, I get +3.5 db, 0 and 0. This raises the first clip so now I hear my footsteps, breathing and background noise much louder in the first clip than the other two. This is not what I want.

Compression:

If I remove the normalization and then compress clips 2 and 3 to "Speech largely compressed," the background and some of the louder parts sound a bit tinny. If I now normalize all 3 together, the amount is the same as before. The main difference is that the fainter parts of my voice are now louder, closer to the loudest part.

The compressor in the cleaning interface is very rudimentary. A reasonable compressor would allow adjusting the compression ratio, compression threshold, attack time, release time, and makeup gain. You can see these in the compressor for a track in the mixer.

The compression threshold is when the compressor kicks in, that is, above this level, the lowest sounds will be closer to the loudest sounds, depending on the ratio. A higher ratio means more compression. What the compressor actually does, is reduce the output volume of the louder parts. See the compression image in this article. This is why makeup gain is needed, the higher the ratio, the more makeup gain required. Normalizing after applying the compressor will also bring the volume back up.

What to do:

I suggest putting the audio of all of the similar clips on the same track, nothing else on that track. Then do a mixdown to get a wave file; the single clip will be red. Right-click and open the External editor, likely Music Editor 3 unless you changed it in the Program Settings folders.

Now you can operate on everything together. You can split this object into pieces, but unfortunately, ME3 does not allow more than normalizing individual objects. As far as I know, any of the other tools affect the entire track. If you have Audio & Music Lab Premium or its updated version Sound Forge Audio Cleaning Lab (or ACL or VSCL), you can apply effects to individual (split) objects and/or to the project.

I suggest first normalizing, turning on the Limiter, and then applying other effects. The main compressor is under Mastering, Dynamics, and you now have good control to work with. Try to find the threshold point and try various compression ratios. Listen, adjust, listen, adjust, repeat... Apply any other effects.

Now listen to the track. There may be parts that are too loud, parts too soft, someone said something in the background that you want to bring up or get rid of, etc. You can do this part now or back in MEP. Turn on the volume curve, add points and raise or lower the volume where required. Exit and the red wave file will be updated. As I said, you can adjust the volume curve either in ME3 or in MEP. If you have background music on another track, you may want to adjust the volume curve in MEP to suit.

Alternatively, you can use the track tools from FX in the Mixer.

There is a lot more that you can do, of course, but a lot is iterative and you need to use your ears.

Difference with EBU normalization:

In VPX, applying EBU normalization to the 3 clips gives me volume levels of +10.8 db, -6.3, and -7.9, respectively. Now the background in the first clip is way too loud, so I have to adjust it down. It would be better to do a mixdown and then apply EBU normalization, I think.

Example 2:

When I do a lot of voiceovers or narration, my voice sometimes changes from take to take and day to day, and the dog barked. Some takes are quite short, others long. As a result, when I normalize, the normalizer has a problem with short takes and they come out much louder than longer takes. I have to adjust the volume manually, or I do a mixdown, then normalize, then adjust the volume with the curve either in VPX or in the external editor. I try to remove breathes by reducing the volume locally using the curve or by other means. I also use an equalizer or dynamic equalizer. There is much more, of course. The danger is always in making the sound worse.

There is no set answer, no automatic control that does it all; it's a black art.

John CB

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

FunkyB wrote on 3/8/2019, 8:15 AM

Wow. Thanks for the detailed examples and advice. The situations described by browj2 are very similar to what I am dealing with.

I can see why there is no magic shortcut to fix all audio. I'll have to play around with it more, obviously, but I have a better idea of how the different tools fit together now. I've had pretty good results using the compressor setting "Speech Largely Compressed" for clips that need compression, so I'll probably start with that and then either normalize or adjust each clip volume manually. If there are a few points that are way too loud, I'll adjust the envelope to bring them down. You mention turning on the Limiter. Is that the Limiter in the Mastering Suite (simply On or Off)? That's the only one I could find mentioned in the manual.

 

browj2 wrote on 3/8/2019, 9:48 AM

@FunkyB

You mention turning on the Limiter. Is that the Limiter in the Mastering Suite (simply On or Off)? That's the only one I could find mentioned in the manual.

No, the Limiter that I mentioned is under the part about using Music Editor 3. However, I usually turn on the Limiter in MEP/VPX as there may be something that I missed and I don't want it to exceed the limit.

Here is what the SF Audio Cleaning Lab manual says about the Limiter, which is probably the same text as for ME3, " The limiter prevents clipping and the auto function enables the volume to be automatically optimized.  "

Here is the text about the limiter in the Mastering Suite of VPX, "The limiter prevents clipping by automatically lowering the level if it is too high. Quiet parts remain unaffected. In contrast to the compressor it tries to leave the basic sound as unaffected as possible. "

Here is an image from the book "Working with Audio" by Stanley R. Alton (highly recommended) showing what both the compressor and limiter do:

You can see that for the compressor, the higher sounds are lowered and the lower sounds are raised, starting from the threshold. I don't know what threshold the compressor in Audio Cleaning uses, which is why I suggest using the compressor in Music Editor (ME3) and adjusting the threshold so that fainter background noise does not get compressed. If you are satisfied with the results of the Compressor under Audio Cleaning, great. But you may want to do some tests to compare it with the Compressor in ME3.

In the lower image, you can see that a limiter cuts off everything that is above 0db, which may not be what you want. If the original is clipped, loud sounds distorted, then there is no information available (all bits are 1) and lowering the volume will not help. Thus, it's best to be careful to avoid clipping during recording.

Magix mentions that turning on the Limiter automatically lowers the level rather than cutting it off like that shown in the lower image. Thus, if there is distortion, it will probably still be there. But if there is no distortion and the sound level is just too high, using the Limiter will bring the volume down so that it doesn't distort, if I understand correctly.

John CB

Last changed by browj2 on 3/8/2019, 9:49 AM, 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

johnebaker wrote on 3/8/2019, 10:32 AM

@FunkyB

Hi

Have you tested a program called The Levelator (free) - it does work with Windows 10.

I have tested this on some seascape scenes I have with different volume levels and it has done a reasonable job on levelling out the differences in the audio levels.

From MEP I exported the movie as WAV file and dropped this on to Levellator - it returned a levelled and normalised file which can the be used to replace the audio in the project.

HTH

John EB

 

Last changed by johnebaker on 3/8/2019, 10:33 AM, 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.

browj2 wrote on 3/8/2019, 11:09 AM

@johnebaker

Interesting. Thanks. I'll try it out.

@FunkyB

Just playing around with an animation in Xara. Here is what I think the Limiter in MEP probably does:

Do others agree?

John CB

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

johnebaker wrote on 3/8/2019, 11:23 AM

@browj2

Hi John

That is close to the normal function of a limiter as I understand it - on a good limiter, there should be 2 settings to control the limiting action which should come in gradually once the signal reaches a threshold and then progressively limit to the set maximum value.

John EB

 

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.

emmrecs wrote on 3/9/2019, 3:34 AM

@johnebaker

Hi John.

Thanks for the reminder about The Levelator; I had it installed on an old computer, still had the installation file, but had completely forgotten about it! I'm not entirely sure I would use it for music tracks but otherwise it can be very useful.

Jeff

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, NVidia GTX 1660TI and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam