It's time for the free AAS sound pack

[Starship Krupa]

11 hours ago, X-53mph said:

VST3 became a 'forced' option in a particular update of CbB

I don't know what you're referring to.

CbB never forced me to use VST3's instead of VST2's.

Use Plug-In Manager to exclude the VST3 version and you're good to go.

[X-53mph]

On 1/2/2025 at 11:50 PM, Starship Krupa said:

I don't know what you're referring to.

CbB never forced me to use VST3's instead of VST2's.

Use Plug-In Manager to exclude the VST3 version and you're good to go.

This was several years back when BandLab had just saved Cakewalk from near extinction. There was one particular update that auto-selected the VST3 check box without asking the user whether they wanted to or not. It caused a lot of people a lot of hassle because so many plugin developers had conflicts with cakewalk and VST3 coding. After that update, when opening old stable sessions, they would stop working because of one or two plugins, and it became a hunting game to find which ones were causing the conflict. I lost days of working time trying to resolve the issue (with Noel). In the end, cakewalk removed this auto-selection option in the following updates. That was when I discovered that many top plugin developers had this conflict including Spitfire. I hope that in the intervening years the issue has been resolved, but I imagine it may still be an issue with older plugins.

The option to force VST3 is found on the Preferences tab > VST settings. I advise you to keep it unselected:

Edited Saturday at 10:07 AM by X-53mph

[Starship Krupa]

7 hours ago, X-53mph said:

There was one particular update that auto-selected the VST3 check box without asking the user whether they wanted to or not.

So "changed the default," rather than "forced."

I wouldn't have noticed it because from the day I started using CbB, I checked that box.

I'm not coincidentally very strict about not allowing plug-in installers to clutter my system with different builds of the plug-in. If the installer either doesn't offer or doesn't respect my choice to only install one build, in one location, I go through and manually delete the one I don't want. It's odd, my two favorite plug-in developers were once the absolute worst offenders. At the A|A|S installer's peak of redundancy, I'd delete 2GB of various Pro Tools, 32 bit, and VST2. MeldaProduction were the other offenders, followed by Native Instruments. There's a tutorial I wrote still on the forum detailing where to check for spurious plug-in versions.

They've cleaned up their acts a great deal, but A|A|S still installs a VST2. Native Instrument also does on older versions of their products, like Kontakt 7. And after you delete the unwanted version(s), Native Access will indicate that your installation needs "repair." I decline their offer to "repair" my system by reinstalling versions of their software that are just in the way.

Was the issue you refer to the one where playing the first few notes from an A|A|S synth will crash CbB or Sonar to the desktop? I've alerted both developers to that one and both sets of fingers are resolutely pointed outward. Cakewalk are happy to help A|A|S figure out what's wrong with their plug-in and A|A|S are happy to help Cakewalk figure out what's wrong with their host, but since nothing is wrong with either host or plug-in, nothing can be done.🙄The crash only happens about 5% of the time, so when the engineers try it, it works perfectly.