MeldaProduction

Marcun · Post by **Marcun** » Sun Apr 19, 2015 9:08 pm

Since Beta9 I can't use side-chain in MDynamicEq or any other dynamic effect in Studio One. There's no side-chain button on DAW's plugin window, no entry on side-chain's list and of course no side-chain input inside the plugin.

mdyneq.png

On the other hand MVintageRotary got it...

mvinr.png

lachrimae · Post by **lachrimae** » Sun Apr 19, 2015 9:43 pm

Possibly related:

In Reaper MAutoDynamicEQ side-chain works fine with VST3 but the VST2 x64 version side-chain does not work. The button is there but it doesn't recognize any audio from channels 3/4.

MeldaProduction · Post by **MeldaProduction** » Sun Apr 19, 2015 10:11 pm

Exactly! Only VST3 version usually have a sidechain. In Reaper VST2 version should have it too. Anyway in Studio One and most other hosts you need to use VST3 version to get a sidechain.

Marcun · Post by **Marcun** » Mon Apr 20, 2015 7:20 am

But the second picture shows 2.4 plugin... And many of my third party plugins are side-chain ready too. So it seems with VST2 it's a question of luck.
I'm going to install VST3 and hope it'll work.

DarkStar · Post by **DarkStar** » Mon Apr 20, 2015 9:13 am

I've just tried the beta 2, VST2 32-bit versions of both MAutoDynamicEQ and MVintageRotary in Reaper. Audio registered on the Sidechain meters for both.

Also OK in energyXT v1.4.

MeldaProduction · Post by **MeldaProduction** » Mon Apr 20, 2015 11:09 am

Technically VST2 doesn't directly have side-chain support, some host "simulate it". That's why I always recommend using VST3.

Anyway I checked in Studio one 2 and MDynamicEq 9.00b3 has sidechain for both VST2 and VST3. I'd recommend letting Studio One rescan all the plugins. If that won't work, uninstall/remove all of the plugins, run S1, then install the plugins and run it again (kind of forced rescan).

lachrimae · Post by **lachrimae** » Mon Apr 20, 2015 1:54 pm

Thanks for the report Darkstar. I'll troubleshoot.

Vojtech, I am using VST2 x64 is because the VST3 versions weren't saving their theme states. I suspect it has something to do with a rights issue on my particular machine and is not a bug on your end (Win 8 has given me other issues with apps not having rights to write to their resources in the Program Files & App Data directories). My VST2 plugs reside on a different drive and wouldn't be affected by those issues...

Edit: So I just tested again and to be more specific, the VST3 version of MAutoDynamicEQ doesn't save the analayzer preset state. Again, I suspect this is an issue on my Win8 machine...

MeldaProduction · Post by **MeldaProduction** » Mon Apr 20, 2015 6:27 pm

lachrimae, ok, so are you saying that you use MAutoDynamicEq in a project, setup the analyzer somehow and next time you open the project the analyzer settings are different? That would definitely not be related to your system settings.

Marcun · Post by **Marcun** » Mon Apr 20, 2015 6:53 pm

Ok, side-chain in VST3 is of course working, however...

I use 2 graphs in analyzer of my MDynamicEq: Average and Average (Infinite) with track peaks. In VST3 the second one needs to be enabled again every time I change working track and bring this plugin to the screen. It doesn't matter if the first graph is enabled or not.

lachrimae · Post by **lachrimae** » Mon Apr 20, 2015 7:03 pm

Sorry Vojtech, I found the issue and (as expected) it's user error.

I had saved a default preset in Reaper's plug-in window and didn't consider the fact that the preset would always revert new instances to the original sonogram preset (which was making the analyzer background a different color in VST3 vs VST2 because the default preset was different).

So, I kept changing my Sonogram preset and trying to "Set Default Settings" within VST3 MAutoDynEQ but it was reverting back to the old sonogram color with each new instance... I just needed to re-save my Reaper default presets after making a change to the analyzer settings and the issue was resolved.

Thanks for looking though.

Marcun · Post by **Marcun** » Mon Apr 20, 2015 8:01 pm

I tried to re-set default settings but it didn't work for me.

And one interesting thing: when I start VST2.4 alone everything is ok but when I insert this one before or after VST3 both don't show the second graph. And after re-enabling the Average(Infinite), the graphs also look different: in VST2.4 seems to work ok, but in VST3 it's smaller and slower.

MeldaProduction · Post by **MeldaProduction** » Wed Apr 22, 2015 6:27 pm

Marcun: I'm really lost, what's the problem then? Are you still talking about sidechain or what? Please, you need to be specific...

lachrimae: Very well, I'm glad it is ok

. And yeah, overwriting defaults, classic

.

Marcun · Post by **Marcun** » Wed Apr 22, 2015 10:07 pm

Ok, let me sum up:

1. Side-chain - ok with VST3, finished.
2. VST3 - problem with second graph as described above. Maybe I should move it to another thread?

MeldaProduction · Post by **MeldaProduction** » Thu Apr 23, 2015 2:15 pm

Hmmm, sorry, I read your post like hundred times and I just don't know what you mean. Please just make a dedicated thread and explain it with all details how to simulate it, ideally with some screenshot.

Marcun · Post by **Marcun** » Thu Apr 23, 2015 8:59 pm

Sorry for my shaking hand and not too wise commentary but I hope this clip shows the problem:

MeldaProduction

KVR Audio

Side-chain lost in Studio One?