Noel Borthwick

What version of Windows are you using and how did you install Cakewalk? Error code 20 is an error indicating that the digital signature of the application is invalid or could not be authenticated. This can happen if the executable was modified or if the cryptography in Windows is unable to validate the signature.

Obviously, a crash isn't expected. So, you saved a mix from a project containing a synth, then replaced the synth and then tried to apply the saved mix to the new project? If its crashing thats a bug. I would expect it to apply the mix from the old mix recall setting but ignore the new synth. If you choose to ignore effects in the mix recall settings when applying the preset does it work ok? Please try and reproduce it with the same steps and see if it still crashes. If so please send the dump file.

It looks like something is messed up with the Windows redist installer state. Uninstalling and reinstalling might be the only solution, or you can contact Microsoft support who may be able to help. Also see this link: https://developercommunity.visualstudio.com/t/errore-microsoft-visual-c-2019-x64-minimum-runtime/1299781

That’s not accurate. Cakewalk adds that folder by default to the scan path.

What dropout code are you getting in the message when it drops out. That should indicate the cause.

How are your MIDI tracks routed? Are you playing them through a virtual instrument VST? If so the sounds would always be synchronized with audio playback as long as you are hearing audio tracks correctly because they are delay compensated. Make sure that you are not using the Microsoft MIDI synth device. Safe mode may have worked for you since it switched the driver mode to WASAPI (windows audio)

I was referring to inserting tracks not the rme device

I have the fireface and it takes less than a second to insert a single track. No difference whether the device is on or off though. If you turn off the audio engine does it insert quickly?

Adding tracks is instantaneous. If you are you using a control surface disable it and test again. Also what audio interface and driver mode are you using? Certain drivers are known to bog down the system so use a process of elimination to find out what’s causing the issue.

Did you actually get a crash dialog which shows the dump file location? If not it was not detected as a crash.

I didn't supply the instructions to clean uninstall the app I doubt that was required to solve this issue. But yes there should be a caveat that doing that will remove any plugins installed to the VstPlugins folder.

I think there is an actual bug here however. If I move the mouse over the left of a track and scroll, and then immediately move the the effects bin it scrolls the view properly. However if I wait a couple of seconds with the mouse over the effects bin it wont scroll anymore. Will look into it and see. why that happens. Edit: its actually not a bug. in CbB we support scrolling the FX rack unlike Platinum. So its attempting to scroll the rack instead of the tracks view. You can verify by adding plugins to the rack. We'll see if its feasible to improve the behavior in the future.

Have you tried starting Cakewalk without your audio interface plugged in? PS please change the title of your post since we have isolated that it is unrelated to 2022.02 Also, another couple of things to try: Start cakewalk and repersonalize by holding down CTRL when clicking the Cakewalk icon. Respond to the prompt and allow it to re-personalize. Check if this resolves the issue. If that doesn't work add the line below under the WinCake section in Cakewalk.ini that is found under %appdata%\Cakewalk\Cakewalk Core. Then try starting the app. If it crashes send us the dump file. [WinCake] ExceptionHandlingSeverity=7

If you look in task manager do you see a cakewalk.exe process after the splash screen disappears? Usually issues like this mean something is causing the main process to terminate. Try and backtrack to any changes you might have made earlier since you mentioned that it was working earlier.

Right as you guessed we have a timer to prevent inadvertently changing control values. People complained about accidentally changing values while meaning to scroll so this delay was added to alleviate such issues. I don’t remember if scroll wheel works on the effects rack but it it is treated no differently from other track or mixer controls.

The error message you list is not ours but from the Microsoft installer from the redist itself. This link seems to indicate that your windows installers may need repair. https://thegeekpage.com/the-feature-you-are-trying-to-use-in-on-a-network-resource-that-is-unavailable-in-windows-10-fix/ Also read this. https://answers.microsoft.com/en-us/protect/forum/all/the-feature-you-are-trying-to-use-is-in-a-network/80d4be22-aab6-47f0-a7dc-8a3131fc8df0?page=2 It seems that a registry entry on your pc may be pointing to a non existent drive which may be confusing the Microsoft installer. Check the path that it lists in the error message and follow those links.

@Twaddle did you follow this procedure and still have no success? BTW your post isn't about running Cakewalk. It's that you can't run the installer...

The global FX button also bypasses prochannel fx.

We install all redists that are REQUIRED by Cakewalk so using the installer provided should address any Cakewalk related issues.

Not all companies can keep up with the latest versions that is normal. However waves does test with Cakewalk and report issues to us. Changes on incremental releases are very unlikely to affect global compatibility.

Doubtful. It could be a general hang in the system or even a bug. Hard to say without the ability to reproduce it. Is it happening consistently with your project? However smaller buffer sizes can expose certain bugs or race conditions more readily so its a possibility that you may not run into it at a larger buffer size. In any case there is a simple resolution to switch to the default scheduling model.

Incorrect information. CbB started development from the last version of SONAR Platinum. The first CbB release was in fact identical other than a few bug fixes. There were exactly zero teething problems other than transitioning the activation system and some installer changes to removed bundled 3rd party licensed plugins. There is no comparison to any prior version of SONAR anymore. Cbb is a vastly improved and more stable program with thousands of bug fixes and hundreds of new features since then.

@LittleStudios you are using the "aggressive" thread scheduling model. The error code 19 means "Multiprocessing the audio tasks timed out waiting for completion". This is likely some corner case with your project that is leading to this. "aggressive" mode is not heavily tested so I suggest switching back to the default thread scheduling model. This is completely unrelated to the current update btw.

We own the licenses to them all. It was intentionally not included in the free set of released plugins when we first released Cbb. It may be released in the future.

Look ahead is not related to processing cost. Rather it is required to allow the processor to look at historical audio ahead of time. That is what causes the delay because the plugin needs to buffer audio in advance before it can start processing it.