?: MAutoVolume (MAV)

[steve2KVR]

...in the docs the phrase "Normally the plugin stabilizes the input volume to a predefined level" occurs in several places, but was never defined/specified. What does "predefined level" mean? And how is it determined? What is it related to?....../s~

[DarkStar]

As I understand it the "predefined level" is set by the combination of the General and Advance parameters applied to the detection signal. Perhaps it would be clearer if the phrase should be "towards the predetermined level" rather than "to the predefined level".

When [Side-chain] is enabled, the signal on the side-chain input, rather than the main input signal, is used for level detection.

But, let us wait for clarification from the Mmaster.

[ronaldsifontes]

Hi..
Another question about MAutovolume: Where is the "WRITE AUTOMATION" button in version 10.xx ?

[DarkStar]

This is v9.22


The buttons are not there in v10.xx; I did see this:

Note: Automation of the dynamic gain in MAutoVolume has been removed. This feature is by definition degrading audio quality and causes numerous problems with different hosts and has been added just because the Waves' plugin has that. But in order to minimize problems and deliver the top audio quality we want, the feature has been removed. It's recommended to automate output gain instead for example.

[alexis1]

This is v9.22


The buttons are not there in v10.xx; I did see this:

Note: Automation of the dynamic gain in MAutoVolume has been removed. This feature is by definition degrading audio quality and causes numerous problems with different hosts and has been added just because the Waves' plugin has that. But in order to minimize problems and deliver the top audio quality we want, the feature has been removed. It's recommended to automate output gain instead for example.

I never understood - is he saying everyone using the Waves plug-in is being duped because "their audio quality is being degraded and numerous other problems", or instead is he saying that Melda is not able to write the code to perform that automation function without those problems?

I did try that automation feature in the earlier versions of MautoVolume, and indeed there were problems. But if it could work it would be so sweet!

[steve2KVR]

...no one is being duped...the plugs did/do what they did/do...and there was/is no "quality degradation," just changes in gain...easily undid/done...but, imho, neither of them did/do a very usable job...I ended up spending just as much time "cleaning things up" as I would have doing the job "old school" in the first place...hth.../s~

[MeldaProduction]

The target level is really "PREDEFINED", meaning there is some hardwired value. You can then use the Output gain the offset it to any level you want. The tool is really an autogain - just put it onto a track and it will set and keep the level.

As for automation removed - it was indeed added in the beginning because of the Waves plugin, which is very slow and far less versatile than MAutoVolume. Maybe with such low speeds it can be tolerated the low automation resolution, but with MAutoVolume it just isn't. Basically automation is for people - YOU move the knobs and the host records your movements. But when a computer is moving the knobs, it can be moving them so fast, that no automation engine can record that. Some hosts were choking, others were fine... but at the end the accuracy has been always lost. Just trust me here, it's better without it .