Full of CRAAAASH

[chuckebaby]

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.

[Wookiee]

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!

[Starship Krupa]

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.