MTurboComp input gain appears to be broken

Official support for: meldaproduction.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Hello,

When adjusting input gain on MTurboComp, the dry signal is affected, leading to potentially wild gain changes when using the dry/wet knob.

From the "?" button, I can see this is intended behavior, although this behavior is not shared with MDynamics, or nearly any other compressor featuring a dry/wet knob. From everyone I have talked to, the MDynamics behavior is far preferable, being the standard dry/wet behavior and workflow. In order to actually adjust input gain so that dry/wet is "usable", the user needs to go to the edit screen and use the "Drive" parameter instead. It would make things easier to have that on the Easy Screen page.

Could we have this switched? It is difficult to use the Dry/Wet knob when the dry signal is swinging by up to 40dB of gain, and this really is the main reason I am using MTurboComp less and less.

Thank you for the tremendous work on these plugins!

Post

Hey, this is what the DRIVE parameter does. The COMPRESSION knob does the same (except it compensates the output too).
Jason @ Melda Production

Post

Wouldn't it make sense to have the drive and dry/wet parameters adjacent on the easy screen, so adjusting dry/wet when Input gain was lowered didn't cause gain changes? The issue with the compression knob is it'll often raise peak level when lowering its value to below 0. Why, I couldn't really say.

The main issue I'm having is that I can't think of a time where I'd prioritize an input gain that was ignored by dry/wet, over an input gain that wasn't. Dry/wet ideally is close to gain-matched in my experience, as you get the density of the compression in the wet signal that you can then tuck into the dry, without fiddling with volume.

Post

I doubt this is going to be changed for backwards compatibility reasons.

If you have MTurboCompMB, you can use the dry/wet control in the Meters & Utilities section, but that's not ideal.

Maybe adding the drive control to the easy screen might be an option.

Post

It may be so. Though, if automation/state recall refers to a parameter by some ID and not by name/knob/UI placement, it's possible switching the two would not impact backward compatibility.

Post Reply

Return to “MeldaProduction”