Hi, it seems that connecting EG1 to EG2 SIDECHAIN/INITIAL GAIN on the patch panel does not keep VCA open as in the hardware (see here). Basically you should be able to control cutoff filter with EG2 without affecting VCA, but this doesn’t seem to happen on V-Collection MS-20.
Is this a known bug and would it be fixed? Any workaround available?
Hi @spinlud.xyz. Welcome to the community,.
I’m not sure if Arturia mean this is by design.
I think you can get the excact same results the way Arturia have designed it using other settings i believe.
I have discussed it here a couple of years ago in the legacy forum:
My views are there too.
Hi LBH!
Thank you for the answer and the link to the legacy discussion.
I am trying to do exactly what the other user was, to control filter cutoff with EG2 and amplifier with EG1. I have read the whole discussion but I still don’t understand how to achieve that. Could you please explain how should I use the EG2 SIDECHAIN to have the EG2 controlling only the filter and not the amplifier?
Hi again @spinlud.xyz,
First: I would like Arturia to add the original Amplifier patching behavior. I allways liketo have the original ways of doing things. Then added features are welcome too. Feel free to contact Arturia support about it.
But are you sure you have read what’s in the link including what’s in the links in the linked thread? I think it explains. Including about the uncommon behaviors the original hardwares envelopes have. I agree it’s hard to get the head around. It does’nt work like you normally exspect.
I’m actually still not 100% certain if there is a bug or not. I also don’t have the hardware to compare.
The original hardware MS-20 work in a speciel way. The envelopes is very speciel.
The original hardware has some quirks.
Also don’t you wonder why AutomaticGainsay seems surprised in the video. Some things seems to not work quite like he exspect. (I know AutomaticGainsay have knowleadge, but i don’t think this video is good, and it does’nt really explains the envelopes impacts.)
The questions is how to achieve the sound you want to achieve no matter how.
What’s the purpose to use the EG1 to control the Amplifier and the EG2 to control the Filter? How will the result be the same as in the original hardware? Here it’s important to understand the envelopes uncommon behaviors in the original hardware.
Hi LBH, the AutomaticGainsay video was just to show that specific behaviour, I am not claiming it is a good or bad video.
As per your question about why one could want EG2 to control filter and EG1 to control the amplifier, it is really simple: it is common for some patches to have the filter close with a short decay to a low sustain value without having the same envelope applied to the amplifier. This is a really common design even on vintage synths, and it is my understanding that this could be achieved in the original MS-20 sending a patch chord from the EG1 to the INITIAL GAIN input (basically overriding the EG2 envelope on the amplifier).
This is not working on the Arturia MS-20 plugin, so if someone knows a way to do that I am all ears 
I do understand what you aim for. I’m just not sure it make much difference in the sound.
I think it’s strange that many talk about this patching, but i can’t find any example of how it actually works and show it in a clear way. That’s the complaint i have about the video you posted.
However - as said i too would like original behaviors to be possible in an emulation.
And this kind of use and other things this could be used for is not possible as it is.
I suggest you contact Arturia support.
Well for example if you have a filter closing fast to a zero sustain, the sound is quite different if you also the VCA closing in the same way instead of keeping it open.
Thank you very much for the help, I have written to Arturia support let’s see if they can provide any info on this matter.
I’m certainly interested in the reply.
Keep the speciel EG behaviors in mind.
Just received support response:
This issue is now referenced in our database, from now on, I transmit the case to our Test and Dev Team.
We will now work on it and hope to be able to fix this in the forthcoming update / hot-fix.
Let’s hope they will do something about it 
1 Like