TBProAudio releases GainRider, the gain riding plugin for Windows and Mac OS X

[TB-ProAudio]

AAX Win/OSX released

[ObsoleteAcc99]

I'm really getting into your plugins and have some questions now for gain rider also.

1) Would you consider adding attack and release

2) Please consider a lower latency mode

3) Please consider having a way to ride the vocal above the mix like vocal rider/autogain

I love the display and real time infos and your demo video is great for basic riding.. vocal rider does not do that well actually and melda sounds a bit unnatural (imo)..

HOWEVER, my favourite upwards compressor of all time is:
https://www.youtube.com/watch?v=DXkzJGhkjMg

Different thing i know, but there is some overlapped functionality in that a volume rider can increase the level of low signals also..

the unique thing about the curve is the way you never make noise louder unlike normal upward compression.

The thing is, he has no latency and only 1ms in look ahead mode.. which means i am sure you can add this functionality to the gain rider also, as it can already be set to only increase soft parts.. and the noise control would be the same as the range on the curve, right?

[TB-ProAudio]

1) Would you consider adding attack and release

Well, GainRider is not a compressor, more a Leveler based on RMS. As RMS creates the detector value there is always an buildin attack and release. The RMS speed (aka window) can be controlled by parameter Sensitivity.

2) Please consider a lower latency mode

As I is said, GainRider is based on RMS, and RMS needs a certain time to calculate. As RMS is behind peak you need to delay gain change as well, so the whole processing chain is delayed. Lowest latency is 50ms (aka ca. 2k samples). There is a direct relation between RMS window size and internal delay, so we would need to change the whole design of GainRider to lower latency.
But you already said that other leveling tools may not work for you as expected, maybe this one of the reasons?

3) Please consider having a way to ride the vocal above the mix like vocal rider/autogain

The need for riding comes from the unsteadiness of the vocal loudness (aka RMS). So GainRider keeps the loudness constant and therefore always above the mix.

Different thing i know, but there is some overlapped functionality in that a volume rider can increase the level of low signals also..

the unique thing about the curve is the way you never make noise louder unlike normal upward compression.

Compressors (even upward) are a different thing: compressors can be designed with 0 latency.
As I can see from the far The Curve has a "normal" compressor design with a 2 point gain transfer curve. But maybe I'm totally wrong here.
But this is what I would do to increase vocal loudness, by keeping the peaks under control and noise away:-)
You are right: I should consider this in a new version of Impress, but not for GainRider.

The thing is, he has no latency and only 1ms in look ahead mode.. which means i am sure you can add this functionality to the gain rider also, as it can already be set to only increase soft parts.. and the noise control would be the same as the range on the curve, right?

I understand that high latency values could create trouble in "not so modern" DAWs. But in case of GainRider there is not much to improve, sorry. It is just the design!

RangeMin/Max controls how much the gain can be changed. As I do not have The Curve on hand, I cannot compare...

[DrReacto]

Does this do auto riding like Waves Vocal Rider?
Dr. Reacto

[ObsoleteAcc99]

Does this do auto riding like Waves Vocal Rider?
Dr. Reacto

Yes but it does it much much better.

What it doesn't do is have a way of listening to the entire mix and making sure the vocal sits at a user specified relation to the rest of the mix at all times. In fact I'd use this to even the audio volume wise, then use vocal rider or the ten buck hornet auto gain to keep the result at a specific relative level to the rest of the mix at all times.

BUT I won't use it as the latency is just too high. Pdc or not, plugins with this much latency just cause too many transport hiccups in pretty much any daw. I'll need to test it further on some wildly uneven vocal before I totally say no though.

[TB-ProAudio]

What it doesn't do is have a way of listening to the entire mix and making sure the vocal sits at a user specified relation to the rest of the mix at all times. In fact I'd use this to even the audio volume wise, then use vocal rider or the ten buck hornet auto gain to keep the result at a specific relative level to the rest of the mix at all times

Ahh, now i got the point:
You always want the vocal loudness in a fixed relationship (lets say +3dB) to the rest of the mix (loudness), correct?

I have to think about it...

[ObsoleteAcc99]

Correct. All the other riders do do that my friend.

[TB-ProAudio]

Well, then we will start GainRider II, adding the mentioned features and optimizing plugin latency!

[ObsoleteAcc99]

Ok well i am buying it right now as it's just a great plugin for riding volume (sounds so much more natural than hornet/waves/melda) and will look forward to any updates! Just going to shareit now.

PS can i ask the exact amount of the latency? cause pro tools has a limit.

[TB-ProAudio]

Ok well i am buying it right now as it's just a great plugin for riding volume (sounds so much more natural than hornet/waves/melda) and will look forward to any updates! Just going to shareit now.

PS can i ask the exact amount of the latency? cause pro tools has a limit.

Thanks.

You can measure the latency with AB_LM, sic
In any case: 8192, 10240, 16384, 26624, 47104, 90112, 133120 smp

But as i said, i took your remarks regarding latency for granted: i have already the prototype for a GainRider update (zero latency and other nice things). Pls stay tuned, btw we just released dEQ6!


PS: Order already processed, thank you!

[ObsoleteAcc99]

Ok well i am buying it right now as it's just a great plugin for riding volume (sounds so much more natural than hornet/waves/melda) and will look forward to any updates! Just going to shareit now.

PS can i ask the exact amount of the latency? cause pro tools has a limit.

Thanks.

You can measure the latency with AB_LM, sic
In any case: 8192, 10240, 16384, 26624, 47104, 90112, 133120 smp

But as i said, i took your remarks regarding latency for granted: i have already the prototype for a GainRider update (zero latency and other nice things). Pls stay tuned, btw we just released dEQ6!


PS: Order already processed, thank you!

That's good, cause there is no way it can be used in PT as it stands except for the smaller two choices. 16384 is maximum in pro tools so it should work ok too but then you can't put any other plugins with ANY latency in that same signal path. So the safest would be 10240.

i kind of regret it now, i really had no idea it would be that high. You are right i should have measured it first.

[TB-ProAudio]

That's good, cause there is no way it can be used in PT as it stands except for the smaller two choices. 16384 is maximum in pro tools so it should work ok too but then you can't put any other plugins with ANY latency in that same signal path.

Well, maybe PT could improve this?

[ObsoleteAcc99]

That's good, cause there is no way it can be used in PT as it stands except for the smaller two choices. 16384 is maximum in pro tools so it should work ok too but then you can't put any other plugins with ANY latency in that same signal path.

Well, maybe PT could improve this?

that's never going to happen. Talk to avid. Their entire engine and revamped one they remade with PT11 is built around the 16384 maximum plugin latency.

Which is the correct latency choice on gain rider to use for vocals?

[TB-ProAudio]

that's never going to happen. Talk to avid. Their entire engine and revamped one they remade with PT11 is built around the 16384 maximum plugin latency.

Thats bad, most of the others DAWs are further ...

Which is the correct latency choice on gain rider to use for vocals?

Sensitivity 2 or 3 (aka 250/500ms window size, aka 10240/16384 smp latency)

[ObsoleteAcc99]

that's never going to happen. Talk to avid. Their entire engine and revamped one they remade with PT11 is built around the 16384 maximum plugin latency.

Thats bad, most of the others DAWs are further ...

Which is the correct latency choice on gain rider to use for vocals?

Sensitivity 2 or 3 (aka 250/500ms window size, aka 10240/16384 smp latency)

Hi, most DAW's ARE further but there's a few things to consider here.

pro tools users were begging avid for any form of PDC for more than ten years (after all, even Cubase SX3 and Sonar 1 had full PDC!).
Avid finally responded. They are basing the maximum on *hardware* limitations of their DSP system. If they put the maximum at the software only version higher, then when those projects are sent to studios with HD versions, everything would be out of time if large latency plugins were used

Second, unlimited PDC also has it's downfalls. The DAW *has* to catch up in some way, the time has to be accounted for somewhere. So if you are having say a second of PDC, that means every single time you press play there will be a second delay (or move the playhead during the project playback), so the DAW can align itself, OR, there is a second of overshoot audio every time you press stop (how Studio one does it).
There's a point where working with a huge latency is just not enjoyable, even for mixing purposes.

I think in this case we have to examine that it's simply a case of your plugin having far too high latency. It really is. It *is* my fault for not measuring it first, and you HAVE responded that you are looking into it for updates, so all i can do is hope you will improve it, and use it then.
Cheers