Melda Audio AGC
-
- KVRian
- 915 posts since 2 May, 2015
..."make up gain" and "gain riding" are really different issues for me...I use the "ACG/set" frequently...did i miss something in the op?...~/s
mba m2 15" | 16gig.ram | 1tb ssd | macOS 26.1 Tahoe
logic 11.2.2 | reaper 7.75 | cubase 14.0.4
focusrite.2i2 | A&H CQ18t
logic 11.2.2 | reaper 7.75 | cubase 14.0.4
focusrite.2i2 | A&H CQ18t
- KVRian
- Topic Starter
- 1339 posts since 25 Sep, 2011 from New York
Steve, the problem with ACG on Melda is (which is not a problem) that it works only internally.
To make my question simpler so people can better understand:
I asked for something like Ians Perception, where you Compress or EQ a Track (for example) and then
you have another plugin where you switch ByPass On and Off to hear the differences BUT...
The plugin compensates for the Volume change automatically. I found a solution which works
perfect, maybe in future will buy Perception...so in reality, in my understanding in this situation
Gain Riding or Make Up Volume is the same thing, the Fader jumping up and down, not compressing.
Thanks
To make my question simpler so people can better understand:
I asked for something like Ians Perception, where you Compress or EQ a Track (for example) and then
you have another plugin where you switch ByPass On and Off to hear the differences BUT...
The plugin compensates for the Volume change automatically. I found a solution which works
perfect, maybe in future will buy Perception...so in reality, in my understanding in this situation
Gain Riding or Make Up Volume is the same thing, the Fader jumping up and down, not compressing.
Thanks
Reality is a Condition due to Lack of Weed!
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Aaaaaha, then it is definitely MCompare! It's far more versatile than Perception and can do everything it does. There was a long debate about that after the release
.
- KVRAF
- 2700 posts since 9 Jul, 2015 from UK
The ALC on MCompare changes the input (source generate) level to match the output (source monitor) level.
So therefore it can't be used as a make up gain.
We need a switch to reverse this behaviour.
We want it to behave the same as AGC in all other plugins where the output is changed to match the input.
Please.
So therefore it can't be used as a make up gain.
We need a switch to reverse this behaviour.
We want it to behave the same as AGC in all other plugins where the output is changed to match the input.
Please.
Jason @ Melda Production
- KVRian
- Topic Starter
- 1339 posts since 25 Sep, 2011 from New York
Thanks Vojchek, we know You can do it! I tried MC Compared but it works different, as JMG said,
the ALC changes the Input, it has to be the opposite, maybe something can be added to it?
Thanks
the ALC changes the Input, it has to be the opposite, maybe something can be added to it?
Thanks
Reality is a Condition due to Lack of Weed!
-
- KVRist
- 354 posts since 27 Jan, 2015
Can you explain what you are trying to do re: makeup gain?jmg8 wrote:The ALC on MCompare changes the input (source generate) level to match the output (source monitor) level.
So therefore it can't be used as a make up gain.
We need a switch to reverse this behaviour.
We want it to behave the same as AGC in all other plugins where the output is changed to match the input.
Please.
Having a hard time seeing what the problem would be, which one gets louder, as long as both are at the same volume (re: MCompare), understanding may have to lower the output to keep from clipping.
Thanks -
- KVRAF
- 2700 posts since 9 Jul, 2015 from UK
Ok 2 examples:
1. If your mastering a track.
If your pre mastered track is for example peaking at close to 0db. Then you limit the track to make it louder. So let's call pre limiter = input and post limiter = output.
Use ALC to match the loudness of the two.
If it turns up the input to match the output then you will be listening to a distorted signal as the peaks will go above 0db.
If the output is lowered to match the input this is better as you can compare what you have done in the mastering chain without being fooled.
2. Compressor make up gain.
A very common use for compression is to make things sound louder. By reducing the dynamic range you have room to turn up the level without it peaking.
If we call pre compressor = input and post compressor = output.
Use ALC to match the two in loudness.
If the ALC turns up the output to match the input this works like a make up gain to restore the loudness that was taken away when reducing the peaks.
Now all Melda plugins have AGC which works in exactly the way I want and describe above. It changes the output to match the input. However in MCompare it's the other way round. Not sure why? Maybe I'm missing the reason.
So why is this a problem? If the AGC works fine just use that right?
Well we were discussing how to get a AGC that can be used on 3rd party FX and MCompare can do it by using 2 instances. One before the FX and the other after. If only the matching was the other way round.
Hope that explains it better.
1. If your mastering a track.
If your pre mastered track is for example peaking at close to 0db. Then you limit the track to make it louder. So let's call pre limiter = input and post limiter = output.
Use ALC to match the loudness of the two.
If it turns up the input to match the output then you will be listening to a distorted signal as the peaks will go above 0db.
If the output is lowered to match the input this is better as you can compare what you have done in the mastering chain without being fooled.
2. Compressor make up gain.
A very common use for compression is to make things sound louder. By reducing the dynamic range you have room to turn up the level without it peaking.
If we call pre compressor = input and post compressor = output.
Use ALC to match the two in loudness.
If the ALC turns up the output to match the input this works like a make up gain to restore the loudness that was taken away when reducing the peaks.
Now all Melda plugins have AGC which works in exactly the way I want and describe above. It changes the output to match the input. However in MCompare it's the other way round. Not sure why? Maybe I'm missing the reason.
So why is this a problem? If the AGC works fine just use that right?
Well we were discussing how to get a AGC that can be used on 3rd party FX and MCompare can do it by using 2 instances. One before the FX and the other after. If only the matching was the other way round.
Hope that explains it better.
Jason @ Melda Production
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Aaaaha, I get it now, well, there's nothing we can do about probably. It's the only way - just check the docs, all the use cases require altering the input's loudness, otherwise it would just be plain wrong... It was never really meant for compensating other plugins, after all we have AGC on all plugins
. So yo ujust have to use Melda plugins 
- KVRian
- Topic Starter
- 1339 posts since 25 Sep, 2011 from New York
That's what i said to my self...and it works perfectly!MeldaProduction wrote:So yo ujust have to use Melda plugins
Reality is a Condition due to Lack of Weed!
