Melda plugins don't receive the sidechain signal in Bitwig (solved!)

Official support for: meldaproduction.com
RELATED
PRODUCTS

Post

Hi guys

It looks like Melda plugins don't see the sidechain signal in Bitwig. I tried other 3rd party plugins (like GuitarRig) and they receive the sidechain signal, as expected.
Am I the only one having this issue?

.....
Later edit: it works if the surround mode in Melda plugins is deactivated!
Last edited by KTlin on Tue Nov 22, 2016 11:50 am, edited 2 times in total.

Post

Bitwig is a very good DAW! Nice choice.
Sometime Melda plugins have to have a sidechain switch activated for it to work.
Which plugin are you using?
Jason @ Melda Production

Post

My guess would be that Bitwig doesn't understand the fact that these plugins support surround, hence reporting 16in8out. Hard to say, could you be more specific about plugin interface, OS etc? Anyways please try VST, this one reports 4in2out as other plugins. Live also doesn't properly support any plugin interface and using VST helps there. SInce Bitwig is sort of Live clone, I assume it could be similar.
Vojtech
MeldaProduction MSoundFactory MDrummer MCompleteBundle The best plugins in the world :D

Post

MeldaProduction wrote:My guess would be that Bitwig doesn't understand the fact that these plugins support surround, hence reporting 16in8out. Hard to say, could you be more specific about plugin interface, OS etc? Anyways please try VST, this one reports 4in2out as other plugins. Live also doesn't properly support any plugin interface and using VST helps there. SInce Bitwig is sort of Live clone, I assume it could be similar.
I'm using the VST 64bit version of the plugins, both in Bitwig and Ableton.
As you can see in this printscreen, Bitwig says "Signal will be sent to the second stereo pair of the plug-in. (channel 3/4)". I don't know what that means, but it says the same when I use, for example, GuitarRig, and GuitaRig receives the sidechain input.
2016-11-21_224411.jpg
You do not have the required permissions to view the files attached to this post.

Post

MCompressor does not support side chain, those 8 ins and outs are for surround.

Post

pone wrote:MCompressor does not support side chain, those 8 ins and outs are for surround.
Then what's the "Side-chain" tab for?
Anyway, I tried the MAutoDynamicEQ as well. In Ableton it receives the sidechain input, in Bitwig it doesn't.

Post

KTlin wrote:
pone wrote:MCompressor does not support side chain, those 8 ins and outs are for surround.
Then what's the "Side-chain" tab for?
Anyway, I tried the MAutoDynamicEQ as well. In Ableton it receives the sidechain input, in Bitwig it doesn't.
Side chaining of the same signal that gets processed but filtered. MCompressor is free and that is one of its limitations.

Post

MCompressor Sidechain Info page wrote:Side-chain panel lets you do additional filtering of the level detector input. Please note that its name does not mean it is related to the processor's secondary input (if it has one). Its main purpose is to filter the signal fed to the level detector. This is useful when, for example, you want to remove high volume peaks of a particular frequency.
But it should work for MAutoDynamicEQ in Bitwig. When you try it what do its meters show?
DarkStar, ... Interesting, if true
Inspired by ...

Post

pone wrote:Side chaining of the same signal that gets processed but filtered. MCompressor is free and that is one of its limitations.
DarkStar wrote:
MCompressor Sidechain Info page wrote:Side-chain panel lets you do additional filtering of the level detector input. Please note that its name does not mean it is related to the processor's secondary input (if it has one). Its main purpose is to filter the signal fed to the level detector. This is useful when, for example, you want to remove high volume peaks of a particular frequency.
Thanks guys! I wasn't aware of this limitation in the MCompressor.
DarkStar wrote:But it should work for MAutoDynamicEQ in Bitwig. When you try it what do its meters show?
The Side meter in MAuroDynamicEQ shows no activity, even though I activated the side-chain input in Bitwig.

Post

Hmm, that's odd. And when you replace MAutoDynamicEQ by another sidechaining plug-in then that plug-in receives the signal OK.

To check the audio into the plug-in how about putting Manalyzer on each pair of channels? Or MMultiAnalyzer?
DarkStar, ... Interesting, if true
Inspired by ...

Post

I'm not a bitwig user, but I tested it right now with the version I had and the signal was indeed sent to channel 3/4 and the melda plugin received it when set to surround mode.

Post

Yes, the surround mode was the problem here. I deactivated it, and the side-chain feature works as expected now. Thanks for the help, guys! :tu:

Post

Ah ha, in Surround Mode MAutoDynamicEQ has 8 main input channels, followed by 8 sidechain channels; in that case the sidechain signal would need to be routed to the first two sidechain channels (9 and 10 on the track).

The upper screenshot here is the initial view of the plug-in inputs and outputs in Reaper (on a 4-channel track:
Untitled.png
In the lower screenshot I have re-routed track channels 3+4 to the sidechain inputs.


I have not yet worked out what all those other sidechain inputs are for (for a 7.1 sidechain signal?), nor how it would work. ;)
You do not have the required permissions to view the files attached to this post.
DarkStar, ... Interesting, if true
Inspired by ...

Post

<< nvm >>
DarkStar, ... Interesting, if true
Inspired by ...

Post

DarkStar wrote:... in that case the sidechain signal would need to be routed to the first two sidechain channels (9 and 10 on the track).... The upper screenshot here is the initial view of the plug-in inputs and outputs in Reaper (on a 4-channel track:
Unfortunately, afaik, Bitwig doesn't have this routing capability, or does it?

Post Reply

Return to “MeldaProduction”