Hey,
it has been discussed over at gearslutz a lot. As we (should) all now we must level match when comparing compression. Usually it's done manually, but I want something automatic to save time.
https://www.gearslutz.com/board/product ... ing-5.html
Therefore mCompare seems perfect at first glance. But it takes the processed signal and matches the unprocessed in loudness.
a) That's great when you have mixed something and want to compare it uncompressed. Certainly, I don't want to miss this feature.
b) But it fails when you want the loudnes compensation while adjusting a compressor or EQ. In this situation I want to know if the compression sounds better at the same RMS level as the source. I need that the loudness doesn't change.
This is the option I miss in mCompare and that's the reason I can't buy it even when I love the other features. Both use cases a) and b) makes completely sense. Feature b) has been requested a lot since 2015 I hope melda will think again about this? Or will this feature definitely not happen? It would be great when you could clarify it.
All the best!
level matching in mCompare is only half baked
-
midi_transmission midi_transmission https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=298730
- KVRian
- 1045 posts since 13 Feb, 2013
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Hi,
I'm a little lost here, is this the ancient request asking for changing loudness of the main input instead of the comparison?
I'm a little lost here, is this the ancient request asking for changing loudness of the main input instead of the comparison?
-
- KVRAF
- 10376 posts since 2 Sep, 2003 from Surrey, UK
<< misunderstood the request - so removed >>
Last edited by DarkStar on Sat Mar 25, 2017 6:23 pm, edited 2 times in total.
-
- KVRAF
- 10376 posts since 2 Sep, 2003 from Surrey, UK
<< misunderstood the request - so removed >>
Last edited by DarkStar on Sat Mar 25, 2017 6:24 pm, edited 1 time in total.
-
midi_transmission midi_transmission https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=298730
- KVRian
- Topic Starter
- 1045 posts since 13 Feb, 2013
@DarkStar: I'm not sure if I get it right, sorry. 
I tried to explain it again here.
I think so yes, let me clarify again.
recording - > mCompare source -> compressor - mCompare Autolevel
a) I processed the audio a lot and mixed the track. Now I want to know if it really is better then unprocessed. So mCompare takes the RMS loudness at the "mCompare Autolevel" and adjust the "mCompare source" to it. For this scenario it's great! THIS IS THE WAY IT WORKS NOW.
recording - > mCompare source -> compressor - mCompare Autolevel (mCompare source is adjusted to mCompare Autolevel)
b) But when I have a recording and am adjusting the compressor, in this moment I want that the RMS from the recording to stay. So the "mCompare source" should be the reference for the "mCompare Autolevel". So the RMS level at the "mCompare Autolevel" is equal to the RMS level at the "mCompare source". When you change the volume from the compressor, the output after "mCompare Autolevel" is not louder.
I think this scenario is the what you mean with ancient request, right?
Because otherwise I need to adjust the output from the compressor every time I do a change at the ratio or something. I need a solution where I can forget about this while tweaking the settings. After that one would of course transfer the automatic adjusted level to the output from the compressor, but that's no problem.
recording - > mCompare source -> compressor - mCompare Autolevel (mCompare Autolevel is adjusted to mCompare source)
I tried to explain it again here.?MeldaProduction wrote:
Hi,
I'm a little lost here, is this the ancient request asking for changing loudness of the main input instead of the comparison
I think so yes, let me clarify again.
recording - > mCompare source -> compressor - mCompare Autolevel
a) I processed the audio a lot and mixed the track. Now I want to know if it really is better then unprocessed. So mCompare takes the RMS loudness at the "mCompare Autolevel" and adjust the "mCompare source" to it. For this scenario it's great! THIS IS THE WAY IT WORKS NOW.
recording - > mCompare source -> compressor - mCompare Autolevel (mCompare source is adjusted to mCompare Autolevel)
b) But when I have a recording and am adjusting the compressor, in this moment I want that the RMS from the recording to stay. So the "mCompare source" should be the reference for the "mCompare Autolevel". So the RMS level at the "mCompare Autolevel" is equal to the RMS level at the "mCompare source". When you change the volume from the compressor, the output after "mCompare Autolevel" is not louder.
I think this scenario is the what you mean with ancient request, right?
Because otherwise I need to adjust the output from the compressor every time I do a change at the ratio or something. I need a solution where I can forget about this while tweaking the settings. After that one would of course transfer the automatic adjusted level to the output from the compressor, but that's no problem.
recording - > mCompare source -> compressor - mCompare Autolevel (mCompare Autolevel is adjusted to mCompare source)
-
- KVRist
- 354 posts since 27 Jan, 2015
I'm reading the OP to say he wants to have an option to have MautoVolume-processed track volumes match the original/unprocessed track volumes.
Example: add a comp, boost some frequencies. Apply MautoVolume to see if it sounds better with the changes or just louder. Great! But, have an option to have the listening take place at the unprocessed track's level, not the louder processed track's.
So if one is mixing to a set volume (using the K system for example), using MautoVolume would not result in a volume change.
I favor such an option!
Mr Dark Star, I apologize, I couldn't understand your post, does it make mine redundant
? Thanks -
Example: add a comp, boost some frequencies. Apply MautoVolume to see if it sounds better with the changes or just louder. Great! But, have an option to have the listening take place at the unprocessed track's level, not the louder processed track's.
So if one is mixing to a set volume (using the K system for example), using MautoVolume would not result in a volume change.
I favor such an option!
Mr Dark Star, I apologize, I couldn't understand your post, does it make mine redundant
? Thanks --
- KVRAF
- 10376 posts since 2 Sep, 2003 from Surrey, UK
No, not at all. I missed the point, so have removed it
-
midi_transmission midi_transmission https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=298730
- KVRian
- Topic Starter
- 1045 posts since 13 Feb, 2013
yes
-
- KVRAF
- 2702 posts since 9 Jul, 2015 from UK
Ha ha, i nutshelled it.
Ok so i asked for this feature already and it got refused. Maybe Vojtech will look again?
AGC in the plugins match the output to the input, i prefer it this way and wish it was this way in MCompare too, or maybe have both options?
Commonly MCompare is used for mastering, where compression/limiting is normal. If we are reducing some peaks but then raise the volume of the source, those peaks will just distort, as there is no headroom on the master. It makes more sense to me to raise the volume of the output, like make up gain. Then there is no distortion.
Ok so i asked for this feature already and it got refused. Maybe Vojtech will look again?
AGC in the plugins match the output to the input, i prefer it this way and wish it was this way in MCompare too, or maybe have both options?
Commonly MCompare is used for mastering, where compression/limiting is normal. If we are reducing some peaks but then raise the volume of the source, those peaks will just distort, as there is no headroom on the master. It makes more sense to me to raise the volume of the output, like make up gain. Then there is no distortion.
Jason @ Melda Production
-
midi_transmission midi_transmission https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=298730
- KVRian
- Topic Starter
- 1045 posts since 13 Feb, 2013
totalyHa ha, i nutshelled it.
I think both ways have their use cases.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Well, there's one main problem - the plugin cannot really know which source are you switching with until you switch it. So it basically doesn't know which source should drive it. But it can just wait for the first switch.
I avoided it before, because for mastering it's just a total nonsense and it was always designed for mastering. But for your case it seems logical indeed.
I avoided it before, because for mastering it's just a total nonsense and it was always designed for mastering. But for your case it seems logical indeed.
-
- KVRist
- 243 posts since 17 Sep, 2006
Couldn't you add a manual choice which should be the reference loudness?
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Well, that would be even more problematic. But I solved it the proposed way - it will be directed by the last source used for comparison.