Jonathan Sasor

6 minutes ago, Tim Elmore said:

In version 2021.01 Update 1, the FX Chain controls (knobs and buttons) don't survive a project reload. When I assign plug-in parameters to a knob, the knob at first controls the parameters properly. However, after I save, close, and reload the project, the knob does not function.

I have tried this with Sonitus Delay, Sonitus EQ, and BC Free Amp by Blue Cat Audio. The result is the same.

For details on how I tested this, please see my post in the QA Forum, titled "FX Chain Controls Don't Work after Reloading Project".

If it helps, I noticed that version 2020.11 does not have this problem, but the 2021.01 original release and 2021.01 Update 1 both have the problem.

 

This has already been fixed internally and will be in the next CbB update, apologies for the inconvenience!

12 hours ago, Superclown said:

I searched a little more on this forum and found that Noel Borthwick had mentioned that issue was because of some change Cakewalk made, and that the newest Cakewalk update fixed it. So, I did the update. No longer get the “illegal character” message, but.... right back to my earlier projects crashing with V12 vst3 waveshell...🤯 brother. This is driving me nuts. 

 

As far as recent changes go, we made an installer fix related to a Waves component that was causing a component to throw an error when updating Cakewalk, however the core issue with the Waves shell crashing for some users is with the Waves shell itself. They've been working on a fix for this on their end, so hopefully it will be in their next update. 

13 hours ago, Decryptid said:

I've already tried reinstalling the installer and got the same thing. Here's a screenshot of the error message, if that helps.

okay, so for this particular file, you're in the "something is blocking this file from being able to register" scenario. This is distinct from the main issue originally in this thread that was a missing dependency from an updated Visual Studio redistributable package. That was resolved in the updated installer.

If you see this error for items in the Shared Plugins folder, you should be able to skip that and the rest of the main Cakewalk install will be fine (and if you're updating those files are already registered). The issues with the sndfile.dll and cwauto130.dll are more integral parts of the app.

Your issue is likely either an antivirus program or pending Windows update that's preventing the file from being able to successfully register here. Try forcing Windows to finish any updates and/or temporarily disable your antivirus while running the installer and it should ultimately go through.

Alternately you could try reinstalling the included redists manually, but I wouldn't expect this to be the necessary case. Something else currently running in Windows is much more likely to be the issue. If there has been an issue with the redists since the last full Cakewalk install, they can be manually downloaded from Microsoft here:

VS2019:

https://support.microsoft.com/en-us/topic/the-latest-supported-visual-c-downloads-2647da03-1eea-4433-9aff-95f26a218cc0 

VS2013:

https://www.microsoft.com/en-us/download/details.aspx?id=40784

VS2010SP1:

https://www.microsoft.com/en-us/download/details.aspx?id=13523

VS2005:

https://www.microsoft.com/en-us/download/details.aspx?id=26347

16 hours ago, Decryptid said:

I'm having the same problem, my computer says it's missing a necessary part and I tried the updated installer, but it said it required a different version (2020.11).

Which installer are you trying to run and from where? The current version of the installer should read "Cakewalk_by_BandLab_Update_Setup_27.01.0.098_r3.exe" and should update any valid install from 2020.11 through 2021.01. If you're seeing r1 or r2 for the update setup, please try downloading the installer again from either the Check for Updates option or BandLab Assistant. 

I just sanity checked this, but the installer definitely warns about Windows 7 every time, regardless of if it's a new install or running the update from Cakewalk or BandLab Assistant. This dialog box appears:

@Craig Reeves Just taking a look through your videos, and I think there's some workflow steps missing when trying to use AudioSnap. When you demonstrate turning it on, you've already got AudioSnap set to "Clip Follows Project" in the palette which is not an option that's turned on by default. While AudioSnap isn't perfect, you should be able to accomplish what you're trying to do if you follow the right workflow steps (I did this for a project I was working on the other day). You need to make sure that you have the proper average tempo per clips set, then the Clip Follows project option set to Auto-Stretch. If you're having trouble beyond that, I'd need to see your project file to see how it's handling your material specifically, but the core essence of the stretching should work. As shown in your video, I think there's other settings that need to be adjusted. Groove Clip stretching is actually the oldest and least accurate sounding algorithm. 

At the moment there's a known issue with routing with patch point/aux tracks in Track Templates. We'll look into a fix for this as time/resources allow. Thanks!

4 hours ago, ian myers said:

I tried the update yesterday 03/01/21 and it failed but I rolled back and was able to use the previous version. Today I tried again using the install button (not update as yesterday) in Bandlab Assistant. This is how it went. I was unable to change file locations in the advanced tab. I like to keep my content and project folders on a separate hdd. First error asking for minimum runtime I cancelled and installation continued. Then the regsvr32 error appeared and I chose to cancel the installation. This was a repeat of the errors I received on the 3rd. only this time I was unable to run my previous version of Cakelab because libmp3lame.DLL could not be found.

Looks like you might have something a little haywire with your existing Microsoft Visual C++ redistributables. If you go to Add/Remove Programs in Windows, try uninstalling any 2015, 2017, and 2019 entries that you currently see, then restart your system and try the Cakewalk installer again. 

We've reached out to AAS for some test versions, and in some initial testing, I was able to get some instability when working with Chromaphone, but not consistently. From what I could tell it appeared to be an issue on the plug-in end rather than on CbB. Based on @ChristopherM's description of the app disappearing, that would also lean in that direction. We'll do some more digging as time allows and also pass our findings to AAS. If you're able to get any additional details or dump files related to the crash, please let us know and we'll take a look. 

Once again, thanks to all for their participation. Please now submit any further feedback to the formal 2021.01 release thread. Update 1 build is 27.01.0.098. Thanks!

You might have the "display muted takes in parent track" option disabled. Clip is not actually being deleted, but it's not visible. 

2 hours ago, jonathan boose said:

Hotfix failed. I tried running it as admin with the same result.

And I have no idea what "code 5" is.

See attached image.

 

 

Something external is accessing the file. Running the install right after reboot generally should clear it, but if you ran the previous 2021.01 update before, you should be fine if you just skip that file as it's already installed/registered and has not changed. 

As for the original problem, it sounds like there might be an issue with the project file itself rather than the install. Are you able to create new project files? Likewise if you want to send us a project file I can see if it can open on our end.

2021.01 has now been made public! Thanks for your participation and please refer any additional feedback to the official release thread:
 

5 hours ago, forkol said:

That does fix the issue for REX2 files and the WAV files. But...

1) The update must have had this flag cut off.  I had it on initially, and I thought that is the default. So, what is the proper default?

2) There is still an issue with the 32-bit WAV files as in the fix. They STILL do not sync to tempo even with that flag on. 

On further examination of the 32-bit files: It does seem that these 32-bit WAV files have for the Loops setting in the ACID header set to One-Shot, even though it's clearly a loop! I'd like to see a response from Cakewalk if this matters on preview, otherwise, I probably have to take this up with the sample vendor.

So the fix for your original issue had nothing to do with the bit depth of the file. There was some unusual information encoded into it by the app that created the file that our code was not handling correctly. This was fixed in the Early Access build. If you have other files that are not behaving as expected, please send us other examples to test. At the moment, I just was checking through RX2 and Wave file loops that previously had shipped with SONAR Platinum/expansion packs, and these all work as expected, so if there's another corner case with the files you happen to be working with, we'd need to verify that on our end. Thanks!

The Preview at Host option is a project-specific setting. It's off by default in the "Basic" template, but if you save a project with it on, it will persist. 

2 hours ago, Asif Ali said:

Crashing when drag copying arranger sections

Can you provide a dump file? 

6 minutes ago, Olli Buchholz said:

I have the same problem with V11 and V12. I can´t open any projects anymore without CbB crashing. Please help! I have attached the minidump file.

_12222020_214814.zip 485.9 kB · 0 downloads

This dump file is similar to ones others have sent, it's the Waves shell crashing. You'll need to send this to Waves as unfortunately there's nothing on our end we can do.

18 hours ago, Kurt Nielsen said:

 

This last update seems to have corrupted the envelope automation and or a clip lane that was switched to gain edit. I've shared more info on another thread.

Other users are reporting the same. Cakewalk is unusable if this doesn't get a fix and it sounds like a problem that has been happening since april so not sure how far back I'd have to go with a rollback since I think there have been a couple updates in between I think and I haven't been working on envelope automation for a while.

 

Hi Kurt,

I'm having trouble being able to reproduce your issue as described. Can you provide a project and/or more specific details as to how you're able to get into that state? At present I'm automating plugins/track parameters and clip gain and the automation is all responding correctly. 

12 hours ago, Bruno de Souza Lino said:

I'm smelling some sort of subscription scheme in the near future for some reason.

Not really. We'd like to make more of the plugins available at some point in one way or another, but exactly how that'll happen remains to be seen. 

6 hours ago, Robert McClellan said:

I keep hearing that they still own the rights to the older legacy plugins but haven’t released them as of yet. 
Not sure what to believe anymore really. 

Yes, BandLab owns all the intellectual property that was under Cakewalk, Inc. We have all the source code for all of the previous plugins, and maintain the authorization back end.

The plugins run additional delay. It's fairly common depending on the plugin. They require extra time to do their processing, so in this case that latency is giving the plugin time to fix those clicks before you hear it. You can either freeze those tracks to record, or temporarily disable them to get around it. 

13 minutes ago, Charles Mills said:

Hello. Since my last update of Cakewalk by Bandlab, the Navigator Pane is missing from the views menu dropdown as is the navigator pane icon. Any help finding it would be appreciated. Looks like "Video" and "Sync" and "Surround Panner" are MIA as well.

Charles

 

You're in the Basic Workspace, this hides the Navigator pane. If you change that back to "None" you'll have access to it again.

Yeah, I'd wager there's a plugin that's not happy based on the video. As mentioned, opening CbB first, then holding shift when opening the project will open via Safe Mode and you can opt for "No to All" for plugins and see if it loads. 

Some people are seeing the crash on load issue(s), but we haven't seen that problem on our end. From what we've seen in the dumps, the crashes are within the Waves shell. We've forwarded some of those dumps to Waves ourselves and encourage others to send them directly too. 

If you had SONAR Artist/Prof/Platinum, Session Drummer's x64 version installs with the Artist Instrument Collection. That installer can be run independently after installing CbB as well since it won't change any updated shared components. 

On 12/12/2020 at 8:15 PM, Darcy said:

Martin

No I just recently bought some waves V12 plugins, tried them with my old Sonar X3 and they didn't work so I downloaded Bandlab.

The project I'm working on is an old one that I tranferred in from Sonar but I don't think that's the issue.

The only Waves plugin I can get to work is IR live, 

I guess I could try with an entirely new slate and see if that works. 

HEY  is there ANYONE out there having sucess using WAVES V12 plugins? Please let us know if this is widespread or is it just us.

We have Waves V12 in house, and I use them every day. That said, we've seen some users experiencing crashes on load, and have sent some customer dump files to Waves ourselves. You definitely should try and follow up with them if you're experiencing problems.