Noel Borthwick

@Glenn StantonThe 053 installer installs the same redistributables that the 04 release did. We did not update them because there was a known Microsoft installer problem that I posted about here. My best guess is that you directly downloaded the new Microsoft redist (or waves had you download that) and that messed up your install.

Its not clear if you are asking about BandLab issues or CbB. We can't assist with problems related to the BandLab Mix editor since there is a different team managing that. Contact support to report issues with BandLab. Also there is no interaction between the bandlab software and Cbb so one cannot affect the other.

Which previous version specifically were you running earlier? Have you tried a rollback to verify that its related?

@Sidney Earl GoodroeMost likely something independent on your system changed. What was the previous version of CbB you were running - have you tried rolling back to see if its actually related to this release? What plugins specifically are taking longer to load.

You may want to contact the plugin vendor to fix their issue as well.

This error is because you are running Win 7 which is an out of date and unsupported OS and you are missing updates to TLS protocols. Read this thread for a solution. I meant "Browse BandLab Projects" sorry. Its also referred to as the bandlab library view.

@jsg follow the instructions here on capturing a hang dump and send it to me. We should be able to see what is hanging from there.

We can't possibly solve crashes with every known plugin. They have to be addressed by their respective vendors. "Normally reliable" doesn't necessarily mean that they will not crash if they have bugs that are latent. That said, what specific problems are you seeing. The only way for us to investigate is if you actually submit crash dumps to us. Follow the instructions to capture a crash dump. A white screen is a hang and you can also capture a dump for those. See this article for more info.

You may as well install Platinum since you own it. There are several bundled plugins that will be useful to you. You can skip installing content that you dont need. The basic installation won't occupy any significant disk space.

@Hillmy Thanks for the dump file - I investigated it. It happens because the plugin doesn't complete its processing while you are changing presets and because cakewalk waits for it to finish processing it hangs. Its actually faulty multithreading on the plugin's part. However the actual hang happens due to some thread safety changes we made for 06. I am fortunately able to work around the problem and have implemented a fix. You should be able to prevent the issue for now by changing presets only when the engine is off. (turn off the engine button on the transport when not playing)

Yes just make sure that your are able to successfully log in from Cakewalk and from then onward no user intervention is typically required. You can verify it's working by doing a check for updates from the help menu and opening the BandLab library view from the file menu.

Its an installer not a program you need to keep around. Cakewalk doesnt get deactivated on its on unless the lease expired. Since the old build you had we implemented auto activation so you will be unlikely to run into that again as long as you can log in. It likely activated itself because something was preventing web access and now that its successful it self activated. BandLab assistant will likely not be used going forward so its in your best interest to log in through Cakewalk itself since updates and activation are seamless. This was explained in the release notes for the 2021.01 update.

Unless your in app install isn't working for some reason.

Which cakewalk version are you currently running? There is also an alternate installer that you can use now. This should allow you to install the latest version of Cakewalk. For the login problem see the thread linked above. Also keep in mind that we're not actively supporting Windows 7 anymore

I don't think this would be anything related to 053. Why do you think these issues are related? The symptoms look like a microsoft redistributables issue rather than an app issue. Nothing in the plugin handling of relevance has changed that would affect Waves in any way.

Its the amount of virtual memory in the page file compared to the max size of the page file. You can see the same numbers in task manager. If you exceed the page file size then things will start to fail in Windows potentially.

The waveform is a preview to tell you the levels of the input signal coming in - its not the actual data in the recorded wave file. So if something failed while writing the file there could still be an issue. The fact that it goes away after recording possibly means that something failed at the end of the recording when it writes the wave file. Thats why I'm curious if the file is actually present on disk. It would be good to try and get to the bottom of why it happens if nothing a better error message may help find the cause.

A patch point input is no different from any other stereo hardware input. It has 2 channels. When you use it you can choose the left right or both channels. Sends are OUTPUTS. Cakewalk doesn't support outputting to a specific channels in virtual outputs today. If you need to send to the left channel of a patch point just use send pan to hard pan it left.

The tooltip already shows the channel numbers.

This is not a Cakewalk specific issue. Many drivers can only have the buffer size set through their control panel. Yours is likely the same because our slider is grayed out, so even if we implemented saving and restoring the value it may not work.

Article on how to bypass tpm check. https://www.mpnrc.org/windows-11-tpm-2-0-error-fix-bypass-method/

@Hillmy upload the file to any file sharing service like google drive, onedrive or dropbox and send the link

It is possible to set the ASIO buffer size for some audio interfaces. Typically you will see the latency slider in preferences for those cases. However we don't allow setting the buffer size automatically today. You can log a feature request to have a latency presets picker.

Which version of Cakewalk are you running and what plugins do you have in your project. The OP had cases where no clip showed up after recording - is that what you are seeing? That can happen if something interfered with the recorded file being written. There were actually cases of plugins doing destructive things like this that I found, believe it or not. Positive Grid was one such example. When it happens look in the audio folder for the project and check the latest timestamp of the wave files to find the newest file. Then drag it into your project and check if the recording is intact. If not something prevented the file being written.

I figured it out. The plugin is posting spacebar messages to the main application window. Cakewalk currently doesn't accept random processes sending keyboard messages to the app window so it throws such messages away. Lets say ahem that this is pretty unorthodox behavior for a plugin to do and I've literally never seen any other plugin do this. My guess is the developers tried it in a couple of DAW's and it happened to work so they started doing it. This is exactly the kind of thing I'm referring to when I say you cannot infer anything by looking at how a plugin works in one DAW. Most plugins send keystrokes to the PLUGIN window not the host window. If VEP had done that it would have worked properly. I have made a couple of changes to listen to keystrokes at the app level, and now the play button and spacebar work in VEP. However we'll have to test it and make sure there aren't any unwanted side effects to this.