user6808463577169165 10 Posted March 30 1 hour ago, Will. said: Definitely send Output support a complaint as well. It is highly important to send CbB support one too. I had found a problem where a plugin that was working in Vst3 doesn't work with the new release only the vst2 does. So I rolled back prior to the Update1 of 2022.02 and the VST3 installation works again. Of course in my problem downgrade to Previous versions didnt solve anything And I will report to output 1 Share this post Link to post Share on other sites
chuckebaby 769 Posted March 30 On 3/28/2022 at 7:05 AM, Wookiee said: @user6808463577169165 what happens if you disable or remove that plugin. If removing or disabling cures the problem then the issue is with the plugin not CbB? Wookie knows. This is the first thing I would have suggested as well. 1 1 Share this post Link to post Share on other sites
Wookiee 1,743 Posted March 30 On 3/29/2022 at 2:04 AM, Starship Krupa said: Not necessarily. Plug-ins vs. hosts is really a compatibility issue. A plug-in can expose a bug in its host, as well as the other way around. Would you say with certainty that if the same plug-in works in REAPER that it's an issue with Cakewalk? If a plug-in is fully compliant with the rules of the SDK I would agree but it has been proven that not all plug-ins are fully compliant. By removing the plug-in you establish an initial point to assess where the issue may be. As to it working in an alternate DAW proves nothing other than it has been tested in that DAW and potentially fixed to work in that DAW. It is a shame that CbB is so frequently ignored by developer's when you consider that Cakewalk developer's identified a fault in Steinbergs own SDK for VST3! Share this post Link to post Share on other sites
Starship Krupa 3,116 Posted April 1 On 3/30/2022 at 3:26 PM, Wookiee said: It is a shame that CbB is so frequently ignored by developers Is it? I haven't experienced issues in that area. Share this post Link to post Share on other sites
