Turbocomp threshold improvement

[Svama]

Hi Vojtech,

please make the threshold global for all active presets.
Would love to see a behaviour like trackcomp 2. it uses the same threshold for all units.
Why doesn’t turbocomp just use one threshold for the active presets? Some working with gain in, other with threshold, why?
Would so much improve the workflow. We would just need to set the threshold once and then can concentrate on the tone of the different units.

Thanks

[ElVincente]

Oh yeah, that would be much better! Please!

[AlexShesha]

+1 from me for sure. It`s really obvious and very needed
Literally only thing I dislike about Melda plugins atm

[MeldaProduction]

I'm afraid that's simply impossible, since the thresholds are part of a much bigger picture - we analyzed all these comps and they all behave differently, have different ranges etc.

[Svama]

Sorry Vojtech,

but isn't threshold just the starting point of the compressor?
Please explain a little bit more, cause I'm really lost and ask myself how trackcomp can behave this way?
What's the best input gain for mturbocomp at all? It's not the regular 0VU (-18dBFS)!!

Thanks and greets,
Marek

[.sintacks.]

Imagine trying to set a 'global threshold' for a rack of analog compressors. Some of the most famous hardware ever has no threshold control. People have different output level needs as well, do you want all the compression models to have PPM, or RMS or even some LUFS target output?

I'm happy with Turbocomp's models reacting totally different. Fairmeld is crazy! Should be trivial to make a few custom/default presets that behave the way you want

[.sintacks.]

lol first post, since 2008

[Svama]

But these are all limitations I don’t combine with Vojtech and Meldaproduction. As long as I understand compression, the curves, saturation and attack/release behaviour makes the different sounds and not the threshold.

[.sintacks.]

It’s true a lot of these terms lose meaning when modeling analog hardware - and then to make a single set of controls for all models

input/output gain, threshold and ratio on some compressors are inter-dependent. So those same values on a different model produce non-similar results.

for instance it’s kind of confusing that when the ‘compression’ knob is all the way down (-100%) on the Medley VariMeld you still get -15dB gain reduction (which sounds amazing) the edit button explains what’s happening of course

I’m just glad i’m not the programmer!

[DaneJ]

Would it be possible to get a visual representation of the Input signal on the Threshold? For Dynamics, TurboComp & anything else regarding a threshold? I think this would clear up a lot of confusion too.

[steve2KVR]

@DaneJ...best visual feedback display ever, those folks use that technique all the time, would fit perfectly with Melda.../s~

[Hexspa]

Or have the knob glow red when there's more compression

[Held]

Would it be possible to get a visual representation of the Input signal on the Threshold? For Dynamics, TurboComp & anything else regarding a threshold? I think this would clear up a lot of confusion too.

That's pretty cool. At first I was wondering how that's an improvement over the current visualization, but now I think I got it.

It doesn't show the amount of compression, it shows the input level so you can easily set the threshold in relation to it. Right?

As cool as that is, I don't think it's very likely to be implemented in Melda products given how easy screen UIs are built.

[Svama]

These are three different default thresholds of mturbocomp. There is no consistency to say go in with the classical 0 VU for example and you´re good to go.
Why these different thresholds? I don´t understand, please explain. For me it complicates compression.

Thanks

In Advanced mode you have this lines, which correspond to this in kotelnikov. In advanced you can see the actual input volume of the signal and yout threshold as a line.

[Nspace]

This:

Would it be possible to get a visual representation of the Input signal on the Threshold? For Dynamics, TurboComp & anything else regarding a threshold? I think this would clear up a lot of confusion too.

It doesn't show the amount of compression, it shows the input level so you can easily set the threshold in relation to it. Right?

And this:

Or have the knob glow RED when there's more compression

Got me visualizing a very, very immediately informative GUI...
With such, as an user, once could act (and react) at a never-before-seen intuitive mode with MeldaProduction Plugins.
///I see myself rapidly reacting to those gradually moving red lights, fine tuning thresholds to the incoming signals. This would be an unexpected evolution for my workflow, usually focused on careful measuring and setting levels.