Hi all,
in MDynamicEQ, and MAutoDynamicEq, when you right click on a band to open up the band editor, in the Dynamics section of the editor, there's an "advanced" tab. In there is a level transformation grid. I'm having trouble figuring out how the percentages on that grid (which are its units) correspond to dB. In other words, if I create a breakpoint at a specific percentage value on the X axis (the input level), how do I know what actual input level in dB will that correspond to?
Any help would be appreciated!
Dynamic EQ level transformation
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
I quite don't follow - this is the value produced by the level detector, which is not a peak value.
-
- KVRer
- Topic Starter
- 5 posts since 13 Feb, 2021
I guess I don't fully understand what the level transformation grid does. I was trying to use it to create a gain change curve simialr to a "range" in a compressor. And, in fact, I've been able to draw something in that grid that acts just like a "range" setting, where, once the input level passes a certain threshold, no additional dynamic boost/cut is applied. But I have to use trial and error to find the right point on the grid that will correspond to my chosen loudness threshold, and I was hoping to figure out a logical way to find those thresholds.
This is a fantastic EQ! I love using it.
This is a fantastic EQ! I love using it.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Thank you!
And yes, it needs to be a trial and error thingy. Of course, there could be an analyzer, but you know how it is - someone has to implement it (and in such a way that it doesn't consume CPU when not used) and sadly time is limited to say the least
And yes, it needs to be a trial and error thingy. Of course, there could be an analyzer, but you know how it is - someone has to implement it (and in such a way that it doesn't consume CPU when not used) and sadly time is limited to say the least
