Hi Henrik,
Wondering why the loudness filter doesn't include the ramp_time parameter (and if it could)? I'm thinking it should behave just like a volume filter with the addition of fader controlled low and/or high frequency boost and associated parameters. For instance, with high_boost and low_boost set to 0 the loudness filter should be functionally equivalent to the volume filter (if perhaps in a less efficient manner) - yes?
I'm also confused about some of the language in the readme - not sure what you mean?:
"By setting fader to one of the Aux faders it can instead work with a Volume filter reacting to the same fader. When used like this, there should only be a single Volume filter assigned to the chosed fader."
Most confused about "work with" and why "the single Volume filter" in the second sentence.
Cheers, Louis
Wondering why the loudness filter doesn't include the ramp_time parameter (and if it could)? I'm thinking it should behave just like a volume filter with the addition of fader controlled low and/or high frequency boost and associated parameters. For instance, with high_boost and low_boost set to 0 the loudness filter should be functionally equivalent to the volume filter (if perhaps in a less efficient manner) - yes?
I'm also confused about some of the language in the readme - not sure what you mean?:
"By setting fader to one of the Aux faders it can instead work with a Volume filter reacting to the same fader. When used like this, there should only be a single Volume filter assigned to the chosed fader."
Most confused about "work with" and why "the single Volume filter" in the second sentence.
Cheers, Louis
Last edited:
The answer is in the readme just above the quoted text. In short, a loudness filter only does loudness compensation. It must be combined with a volume control (like a Volume filter or the default volume control) to make a complete loudness compensated volume control. It then gets slaved to that volume control. That's why it doesn't have it's own ramp_time.
A loudness filter with boosts set to 0 does nothing.
A loudness filter with boosts set to 0 does nothing.
So the curves shown in the loudness filter section of the readme are at the output of a series combination of a loudness filter and a volume filter controlled by the same fader? That wasn't clear to me but now makes sense.
Sorry to perhaps be dense but I still don't understand the part about "When used like this, there should only be a single Volume filter assigned to the chosed fader." It seems to me a pretty standard use case would be to have multiple channels (e.g. two for stereo), each with its own volume/loudness filter combination all controlled but the same fader. Is that not possible?
Thanks
Sorry to perhaps be dense but I still don't understand the part about "When used like this, there should only be a single Volume filter assigned to the chosed fader." It seems to me a pretty standard use case would be to have multiple channels (e.g. two for stereo), each with its own volume/loudness filter combination all controlled but the same fader. Is that not possible?
Thanks
Correct!
There should only be a single Volume filter definition assigned to each fader, but that filter can then be applied to as many channels as you want.
Ok, got it. Only a single volume filter “definition” (filters section of config file) but multiple instances of that filter (in the pipeline section) are allowed on a given fader. Definitions vs instances (of a definition) was the source of my confusion. That is actually how I was trying to use the loudness filter when I mistakenly thought it also included the volume filter functionality.
So for the sake of completeness, can there be more than one loudness filter definition assigned to a given fader? (Not really sure why one would want to but always good to understand the rules).
So for the sake of completeness, can there be more than one loudness filter definition assigned to a given fader? (Not really sure why one would want to but always good to understand the rules).