I know this is an old post, but... what's wrong with the sidechaining option for VST3 plugins in Cubase?Ah_Dziz wrote:Because if it does I'm willing to pay a hundred bucks to not have to use quad channels to sidechain in cubase.
NYRV Releases AGENT 1.4
-
- KVRAF
- 35410 posts since 11 Apr, 2010 from Germany
-
- KVRian
- 765 posts since 1 Sep, 2007
I just Installed the CM version, is that suppose to be mono only?
I can't find any specifications that it should be. I've tested it in Live 9.7.2 with a loaded plugin as well as the default empty setting but it makes everything mono even if I press the bypass button on the GUI.
Any ideas?
I can't find any specifications that it should be. I've tested it in Live 9.7.2 with a loaded plugin as well as the default empty setting but it makes everything mono even if I press the bypass button on the GUI.
Any ideas?
-
- KVRAF
- 2564 posts since 2 Jul, 2010
I've also run into similar problems with the CM version in REAPER. The VST2 version comes up as having two inputs, one of which seems to be a sidechain. The result is that REAPER patches the left channel to the functioning input and effects only hit the left-hand side. The VST3 version is identified as "mono" in the plugin browser and has the same behaviour.
Was looking forwards to skinning up some nice combinations of airwindows plugins, but mono-only is a dealbreaker. It's not mentioned anywhere, so I'm assuming it's unintentional?
Was looking forwards to skinning up some nice combinations of airwindows plugins, but mono-only is a dealbreaker. It's not mentioned anywhere, so I'm assuming it's unintentional?
-
- KVRAF
- 9576 posts since 16 Dec, 2002
Fyi the CM version can only load CM pluginsimrae wrote:I've also run into similar problems with the CM version in REAPER. The VST2 version comes up as having two inputs, one of which seems to be a sidechain. The result is that REAPER patches the left channel to the functioning input and effects only hit the left-hand side. The VST3 version is identified as "mono" in the plugin browser and has the same behaviour.
Was looking forwards to skinning up some nice combinations of airwindows plugins, but mono-only is a dealbreaker. It's not mentioned anywhere, so I'm assuming it's unintentional?
Amazon: why not use an alternative
-
- KVRian
- 765 posts since 1 Sep, 2007
I believe you are thinking about another similair plugin CM have had which name I can't remember. The main limitation here was the amount of plugins you could load, unless they changed it later but I have not been able to find any information that it's locked to CM plugins only.VariKusBrainZ wrote:Fyi the CM version can only load CM pluginsimrae wrote:I've also run into similar problems with the CM version in REAPER. The VST2 version comes up as having two inputs, one of which seems to be a sidechain. The result is that REAPER patches the left channel to the functioning input and effects only hit the left-hand side. The VST3 version is identified as "mono" in the plugin browser and has the same behaviour.
Was looking forwards to skinning up some nice combinations of airwindows plugins, but mono-only is a dealbreaker. It's not mentioned anywhere, so I'm assuming it's unintentional?
https://www.musicradar.com/news/tech/fr ... -cm-627578
-
- KVRian
- 765 posts since 1 Sep, 2007
... New Sonic Arts Freestyle CMKr3eM wrote:...
I believe you are thinking about another similair plugin CM have had which name I can't remember.
https://www.musicradar.com/news/free-vs ... eestyle-cm
-
Danilo Villanova Danilo Villanova https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=418331
- KVRian
- 986 posts since 30 Apr, 2018
Anybody using the CM version? Is it true that it’s mono only?
