Philip G Hunt

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

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. ?

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'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.

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

I've already reposted my original post here in the feedback thread, about a week ago (at Noel's request). I've also shared my projects with the team to find the issue. As to rolling back, yes, it seems to have resolved 'most' issues... meaning, I can now get some work done. But the performance is not as good or stable as it was before. All this was reported in the feedback page.

You'll find it here. There's a link on the first page.

I know how you feel, and I'm glad you confirmed I'm not that only one. I really regret updating this time.

Honestly, the change in performance was so extreme that it can only be a problem with the update. And I am not the only one. I usually have a very low buffer size for performance, and that has never caused problems like this before. Rolling back fixed most performance problems. Increasing the decimation number improves performance. Repeating the update brought the problems back. It's as simple as that. I have repeated it several times. I even uninstalled CbB completely and reinstalled the new version. Immediate problems. Roll back. Fixed-ish. The fact that most people haven't experienced this does not negate the fact that it is happening. I would stick my neck out and say...it has something to do with multiple instances of same brand VSTs. If I've got raw audio only (or frozen tracks) there is no issue. When I have 3 instances of Spitfire instruments (and no other tracks) the session buckles. I've gone from 20-30 track sessions running with effects and plugins to being unable to run 3 VSTs simultaneously.

It's not hardware. It's not firmware. It's not drivers. The only change was: before updating to the new CbB build everything worked seamlessly. After updating...shit show.

Michael, Did you roll back to the previous build? If yes, did it resolve the problem for you, or are you still having issues? I've been happily running 20-30 track sessions with VSTs and effects for years with no issue, but since the last update, I'm getting serious choking even after rolling back. My most recent 3 track session with only spitfire instruments cannot play without audio drop outs and the audio engine stopping. Is this the same for you?

When I update the Bandlab app, I always end up with 2 instances of the app in my Windows install/uninstall program list. One is the previous, the other the mere one. If I uninstall the earlier one, they both uninstall. It's that normal?

The worst thing about this is that even after rolling back, I'm still having issues with drop outs on Spitfire's OPW. It's never caused me problems before, and now all of a sudden it's killing my projects.

It has been working absolutely fine for years with all previous incarnations of CbB (and all old versions of Sonar), as well as power/resource hungry tools such as Trillian/EastWest/Izotope etc.. I've only ever had problems with Iris 2 before. So, telling me that my CPU is below minimum spec is not very helpful, I'm afraid. A better question would be: What has changed in CbB from the previous version to the present to make it so much more resource hungry, or to make virtual instruments take up more resources where they didn't previously? Surely the mark of a good DAW is one that can work efficiently without hogging resources needed by these other programs.

EZGroupie?

I upgraded to the Current Release: 2021.04 yesterday and started getting problems with audio stuttering, dropping out and choking of the system. I've been running previous versions of CbB seamlessly on my i5 laptop but the latest update is overloading the system. I've found it doesn't play well with the Spitfire libraries, in particular Firewood piano and OPW. Firewood can be a bit system heavy, but OPW has never caused me problems in the past. With the current build I am unable to run three Spitfire libraries on the same session, the whole system chokes up, stutters and stalls. If I add izotope or Raum, the system buckles completely. I've rolled back to the previous build and, so far, it seems to have resolved the issue. I thought I'd report this here so the dev team can consider it. Thanks