Noel Borthwick

Anyone who was having this problem please install the latest 2022.06 Update 1 EA that we released. Even though the error 20 is caused by something completely external to Cakewalk, I've added some defensive code to the application that should prevent it from deactivating the application. (Something was causing the windows API's that read certificates to stop working. and this is what lead to the issue.) Please check it and report back ASAP if it solves the issue. Attn: @Wong Jian Ming @Mark MoreThan-Shaw @Illogistical Resource Dept. @mesabassman @Lombardi

Did you install the redist installer linked above?

Clicking solo in the mix module is a global operation to solo or unsolo ALL tracks. For soloing individual tracks or buses you have to click on the individual strip solo buttons.

@Skoo we updated the main app installer a couple of weeks ago. If you download the latest it should install fine on Windows 11 for ARM64. Download the Cakewalk Installer from here

The biggest use of mix recall is to avoid the need to save different version of a project just to compare mixes. Its much quicker to switch mix recall presets than load the entire project file. Mix recall also will save and restore plugin settings and all your automation envelopes, something that digital mixing consoles cannot do.

@Wong Jian Ming and @Mark MoreThan-Shaw I've PM'ed you a link to a build that has some extra diagnostics. Please install it and PM me your results. If the error still occurs the extra information should shed some light on why its failing with the cakewalk exe. Thanks!

Mix recall affects MIX settings, automation and fx, as documented here. Think of it as recalling mixer snapshots for your project including effects and automation data. It works by applying those settings to the current track data your project, which is the actual tracks and clips. If you remove tracks or clips, mix recall will not bring the deleted tracks and clips back. Also any saved mix recall settings that reference tracks or buses that do not exist in the project will be ignored. Why do you need to delete tracks from the project? Just mute them and use mix recall to save a snapshot of the mute state.

Strange. It would be good to find out which redist was damaged. Can you see if this installer helps?

Yes mix recall is the solution that handles this. It will actually save all the envelopes and plugin / track settings that can be restored from a snapshot.

Reminder: This thread is exclusively to discuss the 2022.06 update. For general inquiries or issues please make new threads. OT posts will be removed.

Ok that indicates that it's not related to the release and is environmental. Nothing has changed with the activation process in over a year. Which version of windows are you running? It's possible that some windows update impacted this, or for that matter one of the Microsoft, redistributables.

Bizarre And only on this release? If you roll back it’s ok? Also what version of windows?

That would imply that the issue isn’t related to the program but something environmental. Do you have an antivirus that may have blacklisted the program or something like that? If you rename it back or copy the exe file does the problem return?

You shouldn't need to do a full uninstall. The first thing to check is look at the version info for cakewalk.exe. It should look like this: Check if it says "this digital signature is ok" If not can try deleting (or renaming) the cakewalk.exe file and reinstall the application and retry.

If all tracks are selected and you Ctrl click the pro channel enable button on a single track, it will quick group enable all the PC modules for all tracks. However simply turning on the pro channel won't do anything by default unless you have modules with modified settings.

Try rolling back to verify if the message appears in Portuguese

If it is it's not on our end as far as I can see.

@Dylan O'BrienI've PM'ed you an updated installer to try.

@cheeseman check your PM's I sent you an updated installer to try.

That string doesn't come from Cakewalk resources. It comes via a Windows API to read the device name from the registry, so something likely corrupted there. Nothing has changed in that code for many years.

The device you inserted or removed is returning that string to the Windows API's we're using. Not much we can do to solve it. That is supposed to show the device name that was inserted or removed. Not related to this update.

We identified the issue and will release an updated web installer tomorrow.

Any chance you can share one of the projects that exhibits this? I doubt we’ll be to repro but its worth a try.

Can you share a link to the project that crashes?

We’ve identified an issue with the web installer. We’ll post an update tomorrow. Thanks for the report.