VST3 Console Plugins with Mono Tracks

[DBMusic]

I've started using instances of VST3 console plugins on nearly every track. Nearly all of my tracks are recorded mono. When loading an instance of the plugin it loads in stereo mode. So I go to the plugin pin connector I/O button and select "Request VST3 bus channel count" and select "mono". This works fine as the plugin gets adjusted to mono.

But when I do this I lose most of the plugins master output gain sensitivity. I hear very slight gain adjustments but nothing like it should. For example, setting the gain to infinity will still let most of the audio through. Looking at Reaper's track meter when doing this I also see an imbalance between L & R channels as if one channel is being boosted and the other attenuated.

To get this plugin output gain to function somewhat normally I have to open the plugin pin connector and set the Mono Out pin for channel 2 to be active. This also corrects the metering.

Is this correct? If I set the Mono Out pin for channel 2 to be active on another plugin on a mono track, say a bass amp sim, this causes an imbalance of the L&R channel. So I'm not sure if this is a bug in Reaper or the plugins, or it's just normal and by design. Can anyone could offer a little insight to clarify things as to what is going on?

The VST consoles I'm using are all from Plugin Alliance (Lindell 50 & 80, Focusrite, SSL 9000, and AMEK 9099). Same thing on every one of them.

[Heart Doctor]

Hello DBMusic,

what you describe is correct.

In order to use a VST3 stereo plugin as a mono plugin (in a dual mono track),
you must do the following:

1. Insert the VST3 plugin into the track

2. Set the VST3 channel count to "mono"

3. Set the pin connectors to L channel in, L&R channel out

If you would not connect the pin for the R channel out, the right channel
would bypass the plugin. The right signal would not be affected by the
plugin settings, and this causes the imbalance that you describe.

You can find more information in this thread:
https://forum.cockos.com/showthread.php?t=233127

For Plugin Alliance, you can use the settings described under
"Example: Softube Mono".

Henry

[cemark]

What am I missing here?

I use a bunch of channel strips (sometimes vst3), and some of them from PA.

I have both mono and stereo tracks.

I never had to fiddle with the pin settings. I just slap them on and do my thing.

For the PA SSL J you can try different settings for LINK and Stereo mode, but I never ended up in a situation that I HAD to fiddle with tese either, just to get things working (or properly balanced).

But I am probably missing something here ...

[Stella645]

Originally Posted by cemark

What am I missing here?

...

That it takes more processing power for two channels than it does for one and people are trying to save a little cpu because with console emu they may be on every track.

[cemark]

Originally Posted by Stella645

That it takes more processing power for two channels than it does for one and people are trying to save a little cpu because with console emu they may be on every track.

Really?

I understand that it might be important to reduce CPU load (especially on weaker computers). However, the OP writes nothing about that, only about imbalances in the channels and getting the plug to operate properly.

[DBMusic]

Originally Posted by Heart Doctor

Hello DBMusic,

what you describe is correct.

In order to use a VST3 stereo plugin as a mono plugin (in a dual mono track),
you must do the following:

1. Insert the VST3 plugin into the track

2. Set the VST3 channel count to "mono"

3. Set the pin connectors to L channel in, L&R channel out

If you would not connect the pin for the R channel out, the right channel
would bypass the plugin. The right signal would not be affected by the
plugin settings, and this causes the imbalance that you describe.

You can find more information in this thread:
https://forum.cockos.com/showthread.php?t=233127

For Plugin Alliance, you can use the settings described under
"Example: Softube Mono".

Henry

Thank you! While I was doing the correct thing, I appreciate the feedback as to why.

When selecting "Request VST3 bus channel count --> mono" it would be helpful if the channel 2 pin was activated by default. Not a huge deal if you are aware what's going on, but would be useful in saving a few extra mouse clicks each time it's done as I can't see a reason why the channel pin 2 would not be activated in this scenario.

I suppose life would go on as usual if you chose not to request the VST3 channel count as mono and just processed the mono signal on a stereo instance of the plug. For PA's plugins, it does save and extra TMT channel, which may or may not be meaningful to you. Personally, I just wanted to plug to look like it was processing a mono signal, which unfortunately brought up the channel pin issue.

All things considered, it's nice to understand what's going on.