MAutoVolume - Or how to normalize loudness best?

[Tagirijus]

Hi there,

since version 10 the MAutoVolume plugin does not have an atuomation read/write function anymore. I thought about an offline solution for that. Would this be an idea?

The reason: either I am not using this plugin correctly, or I use it in a wrong situation. My situation: I have imagefilms for example. In these imagefilms I have to mix the voice overs to be equally loud. I do it by hand automation of the volume slide, while I think it sounds best. But in the end I am just doing rather static stuff here - no magic, since I also check with MLoudnessAnalyzer. Now I thougth: "is there no better solution for normalizing loudness of a track?" and I tried MAutoVolume with different settings. Unfortunately this tool either seems to really pump, or in slower modes it seems that the gain automation in the tool has some kind of latency. That means: the sound gets louder too early for exmaple. I am not talking about the plugin latency itself.

Nevertheless: I thought it might be good to have some automation to work with rather than live performing (when mixing post pro stuff anyway) - also good against the latency introduced, when using slower modes. Is this a good idea or does there even exists a better solution?

Thanks for your help, people!

[MeldaProduction]

Hi there ,

here's what I don't understand - you want a static gain for each of these clips, or you want some dynamic solution? For the first one you can just use the MLoudnessAnalyzer's batch processing. And for the latter MAutoVolume is the only option (appart from compressors). The thing is, any dynamic processing will pump if used extremely enough and extreme stuff is sometimes needed if the audio is extreme enough .

[alexis1]

Multiple "smaller bite" passes?

[Tagirijus]

here's what I don't understand - you want a static gain for each of these clips, or you want some dynamic solution?

Sorry for the misunderstanding: I want a dynamic loudness normalization, of course. With static I just meant that my working process is rather static and simple: looking at the LU, correcting the dB, looking, correcting, ... sentence per sentence. I also tried a compressor with max in attack and release and 1000 ms look-ahead. Interesting results as well, but not usable with the 1 sec latency. That's why I came up with the idea: why not having the gain the plugin manipulates as an automation.

[MeldaProduction]

Because automation sucks . There were numerous problems with that, each host reacting differently, changing the curves, not saving then properly etc... It's just unusable imho... Anyways you need rather quick response, but play with the depth and range.

[alexis1]

Because automation sucks . There were numerous problems with that, each host reacting differently, changing the curves, not saving then properly etc... It's just unusable imho... Anyways you need rather quick response, but play with the depth and range.

I looked long and hard into the Quiet Arts Wave Rider, and Waves Vocal Rider before buying MAuotoVolume a few years ago. I never read anything about people saying their automation sucks. Did you think they did when you evaluated those plugs back then, or is it just that automation is hard to implement in MAuotoVolume?

I'd sure like to see that feature one day if possible!

[Tagirijus]

Because automation sucks . There were numerous problems with that, each host reacting differently, changing the curves, not saving then properly etc... It's just unusable imho... Anyways you need rather quick response, but play with the depth and range.

I remember that I once used it in FL Studio and there it worked.

I already testing every single parameter to make it sound usable. Unfortunately I cannot achieve an natural sounding auto-"levelation". I get better results with MDynamics though.

Nevertheless. In the end it was just an idea to have automation involved again. I did not want to start a new war regarding which company makes better plugins, people!! So please do not post, if you like other companies more!

[Chandlerhimself]

Sometimes it is better the use MAutovolume and then use a compressor afterwards. Have MAV take care of the large volume differences and then use a compressor to catch small peaks.