X-53mph

Yes, I was thinking the same thing - I couldn't see anything on Spitfire's site - but I just saw that it's on their official Instagram page. You can link from there.

That was exactly my thinking, but I have been told by the powers that be it is the fault of the vendor not Cakewalk....so they won't do that. 🤷‍♂️

Yes, it's an optional OPT-OUT, but is it by any chance set to OPT-IN on the last release BY DEFAULT? My argument is that it should be optional rather than a forced transition to VST3. Not everyone who updates from previous builds may realize what is happening, and, as not everyone is an IT wizard, they might lose days or weeks of work trying to troubleshoot a problem with drop-outs, stuttering audio, or unexpected closure of the software, when all they really want from the software is an out-the-box environment in which they can make music. I can see from other Cakewalk users that I am not the only one to have experienced this issue, and it has caused projects to grind to a halt as a result. Yes, it can be argued that it is the fault of the VST vendor. Yes, it can be argued that VST3 is the new standard. All this can be argued, but until CbB works nicely with these VST3s (causing an interruption of service which in turn creates bad publicity for Cakewalk by Bandlab) the simplest solution would be to make those boxes OPT-IN, rather than OPT-OUT in each new build. This would have no negative impact on those who already have VST3s happily loaded in their projects, and it will have no negative impact on those who are happily using VST2 instruments. But by FORCING the VST3 to replace VST2, it most definitely IS causing problems. I hope this clarifies what I mean.

Yep.... I'm featured heavily towards the end of the episode...along with my microphones.

Tonight is episode 4 of HitRecord's YouTube Original Series: Create Together Series 2. This series concentrates on Nature. It's called create together because the entire series is a collaborative effort, and yours truly is one of the collaborators. I cannot guarantee I will definitely be in this one...but it's very likely. Here's a link to the Live watch along tonight.

Yes, I sent an email about a week ago....never heard back.....unlike Spitfire who wrote back the next day.

A request for the next official release. In VST Settings: Make the VST Migration optional. As long as there are issues with certain venders VST3 instruments, I think it best not to force CbB to use these. Having the boxes unchecked by default would be preferable in my opinion.

Michael, I have some good news for you. I got on to Spitfire and they confirmed that there is an issue with their VST3 versions of Spitfire instruments in CbB. I double checked the Preferences in the new build and saw that the VST3 migration is set by default to Replace VST2 instruments with VST3. You need to uncheck that box and then go back into your session and replace your Spitfire instruments with the VST2 versions (if they have been replaced with VST3). I'm including a screen grab of where you will find this setting in CbB Spitfire support suggested another work around if this doesn't work for you. "Please try deleting the VST3 plugin files altogether. That way, Cakewalk will only have the VST2s to load after it rescans. As you have been advised, the default location for the VST3 version is here: VST3: C:\Program Files\Common Files\VST3 Cakewalk should rescan the next time it's restarted and will then load only the VST2 going forward. Please note, if you perform a repair in the meantime, the VST3 plug-in will be reinstalled as part of the repair and you will need to remove this again." I hope this remedies your problem and you can get back to making music as before.

What's more colonial than Taiwan?

BK is back Sha Sha

If I try to uninstall CbB using Shampoo Uninstaller, I get the following error message. Any idea why?

The hipster bongos are a must-have. 😂 Integrated annoyingness control and ambient coffee shop knob. 🤣

it took a leap of faith this evening and reinstalled the latest build and then the Early Access release...then I took a deep breath and opened my projects. Firstly, I'm happy to report that I can now get almost the same performance as in build 08. Thank you for that. I especially love the new tempo view. Secondly, there are still issues with spitfire instruments. Test 1) I opened a new empty project and inserted Spitfire Firewood piano. sonar closed unexpectedly without an error message. No recovery file made. Test 2) I opened another blank project, inserted Kontakt 5 with piano. All worked fine. Inserted Spitfire piano. The instrument loaded but I got no sound. Test 3) I did a repair on the spitfire piano via their app. Then I loaded up the previous session and this time the piano worked. I'll do some more testing over the next few days. Spitfire instruments def seem to conflict with CbB (post build 2020 08) in some way. I hope this helps

I suspected the same thing as you. I wonder what else may have been changed in the .INI files. I wish I had taken note of the previous parameters before updating so as to compare. I've now clean installed a much earlier build from 2020 and it it's performing better. They was an issue with the latest AAS VSTs not working as should with CbB. I have rolled then back to the previous install. Now, I've just got to figure out why Spitfire plugins are causing drop outs. I've tried a repair, but I might have to do a reinstall. 😢

Very true. I've already uninstalled all AAS prog.s and reinstalled older installers. This resolved the issue immediately.

Did you update to the latest versions of AAS (as this thread stated)? If yes, do me a favour: Try opening three instances of the Chromaphone 3 in the same session. Do they all open? Is there an unusual lag in opening time? Do they all function correctly when played in the same session? Cheers.

Guys, anyone who hasn't updated to the latest AAS versions - you might want to hold off. It isn't playing well with the latest CbB build. The result is that you cannot open more than one instance of AAS in a project, as well as general slow loading. I don't know if this effects other DAWs - anyone seen problems?

I was having similar problems to you - I uninstalled all AAS instruments and reinstalled from an earlier installer. Seems to be working now. There was def something wrong with the last AAS installer batch.

I'm performing a culling of AAS instruments as we speak - I'll be reinstalling the older versions as soon as I finish my Zoom meetings today. Yes, you're right - on Win 7, you probably shouldn't update AAS or CbB anymore. I'll let you know how it goes. BTW: Congrats on the airplay.

This is interesting - AAS had an update recently of all plugins - I wonder if this could be an issue.

Thanks for the offer - I got a copy from another member (infinite thanks).

Have you tried multiple instances of BBCO or other Spitfire instruments?? Are you able to load more than three with stable performance? If you've got any AAS programs, are you able to load multiple instances of these? Thanks

This is the moment when I look at my shoes, like a school boy being told off. 😢

I don't know if this will help with trouble shooting. I uninstalled CbB via the normal Windows 10 'uninstall' method and then tried installing Build 2020.08. I'm still having the same issues as above (more than 1 Spitfire instrument causing audio dropout - cannot load more than one instance of AAS) So I decided to try and deep-uninstall using Shampoo Uninstaller, and I get the following message: Any idea why I should be having trouble with this temp file?

I used to do this....then a few months ago I cleaned up my setups and thought "why am I keeping these old setups? Let's delete them" Doh!