Noel Borthwick

I've fixed all known issues with solo. So if you are still seeing a problem after updating to the latest EA build (27.11.0.010) please send a simple project bundle file that shows the problem. We're planning on releasing this soon so please try this ASAP.

If the scan appears to be slow even though its not actually scanning any new plugins (no toast notifications showing it scanning plugins) then there are some possibilities. Registry access is slow (degraded or something like an AV is blocking). Or something is slowing down access to the disk where the plugins are. Again could be AV related. If this was fast earlier these are the first areas I would look at. The scan log may show something as well.

No need to uninstall Cakewalk. Run the latest web installer and choose to install SI instruments from there.

Its hard to tell without looking at your project. In your picture you have the send track soloed. Also which version of CbB are you running? There were some routing scenarios where soling sidechain sends wouldn't activate the signal flow. These have been addressed in the latest early access build. Please check out that build and post in that thread if its not working. If you unsolo everything does it work?

Thanks, I think this fix was in the original build as well.

@Apeirofobia please try the new build 10 that I posted.

Build has been updated to 27.11.0.010 This contains the following additional improvements: Soloing a bus now includes any sidechain sends to plugins in tracks/buses Improvements to plugin silence flushing

Yes

I understand your use case perfectly. Its just very tricky to handle the routing to solo it... I have implemented some logic that seems to be working but it would require some regression testing. I can send you a build to try later. As for attaching a project, the easiest way is to save a small bundle file and attach it. Otherwise you will have to zip the entire project folder.

Double click the reg file after saving them to your desktop. One enables and one disables.

While this might look simple on the surface, its not that surprising that this scenario doesn't work. The dependency graph logic for bus solo is extremely complex and corner cases have to be specifically programmed esp in more complicated routing scenarios. I'll try and explain. There are two independent solo "groups" for Buses and tracks that can be independently manipulated. When you solo a bus it figures out all of its upstream and downstream circuit dependencies and makes these audible in the signal flow. Similarly when you solo tracks or aux tracks. However these solo groups are independent. In your scenario since you soloed the kick and bass buses, it figured out that it should make the corresponding aux tracks audible as well as their dependencies which are the bass and kick tracks. However the sidechain is an internal send from the kick aux track to the bass track aux. Since you only soloed buses and nothing is soloed in the track solo group, the intra track send is not evaluated and therefore the send is silenced. If you solo the kick aux track containing the compressor this will work. Also, if you worked exclusively with aux tracks it would also work. I'll have a look and see if if I can make the bus solo dependency figure out the intra track sends. Without breaking anything else! I suggest attaching a simple project for the issue since the routing can be very specific and there are thousands of permutations.

Yes it can be used to make the toast fade. Here are two reg files that can be used to set it. The app has to be restarted to pick up the setting. ExportNotificationOn.regExportNotificationOff.reg

Please comment in the EA thread

Its described in the help. PDC causes latency so disabling it can allow you to input monitor without incurring the PDC latency. Disabling it only changes it for the input monitoring and recording signal path. Audio data from tracks will still be delay compensated.

The hardware TPM is needed if the your CPU doesn't support it. On one of my older PC's the CPU isn't supported but the ASRock MOBO has a TPM header. Nothing in the BIOS I could see. Not sure I'm going to bother with TPM.

Yes that button is to OVERRIDE PDC. Is it confusing, yes 😅

Read this FAQ on activation.

Some info on third party TPM modules. https://www.pcworld.com/article/545965/heres-where-you-can-buy-tpm-for-windows-11.html

The default export location is %PROJECTFOLDER%\Audio Export Cakewalk will auto create that folder whenever you export. You can change the folder name or location to anything you prefer. If you are saving to the project folder (like most people do) its actually saving you an extra step so there should be no need to delete the folder if you use the same folder name. Maybe I'm not understanding your issue.

You must be the first person I've heard of who got the notification, congratulations Its not even being offered for Surface books which is bizarre. I'd have thought those would be validated first and pushed through. I'm not in a rush just curious if anyone else had it officially pushed or there was something broken with Windows update!

Was anyone offered the Win 11 update through Windows update? None of my PC's are being offered it even though they are marked as compatible.

@charvel4blue thanks, I fixed another issue that may have caused this issue. Hopefully will be resolved when we do our next update. Question: Can you confirm whether it hangs while flushing after the export process completes? For now you can disable the flushing if this is blocking you.

Cakewalk relies on a proper installation of various Microsoft runtime libraries for several components (as do many other Windows programs). You can read more about the Microsoft redistributables here. While the Cakewalk application only uses the latest runtime libraries, there are other components and plugins that may utilize earlier libraries. Hence the Cakewalk installer additionally installs some of the older versions of these libraries that are used by certain known modules and plugins. Occasionally the Microsoft runtime libraries installation may get damaged by installing other programs (or even Windows update itself!) by installing incompatible components or removing necessary runtime components that are required for proper operation of Cakewalk. If this happens. the typical symptoms are crashes or hangs on starting Cakewalk or opening a project. A clean install of Cakewalk will always install the necessary components required for proper operation of the program, and typically restore normal operation. However, its not always convenient to reinstall the application, so we've built a new redistributable installer to help repair a system that doesn't contain all the necessary runtime libraries. You may download the new redistributable installer here. Running this installer will reinstall all required runtime library dependencies and should in most cases be able to recover from a damaged installation.

This is caused by a bug in the latest Softube plugins with prochannel modules, that is causing a crash on scanning which ends up leading to this issue. It has been reported to the Softube team and they are aware of it. I've changed our VstScanner to work around the crash which should at least prevent the issue that you have in the video. However the prochannel module won't be available just the normal VST. If you wish you can download the updated scanner and copy it to the C:\Program Files\Cakewalk\Shared Utilities folder. After you rescan your plugins it should fix this issue. The wrong plugin getting inserted is simply a side effect of the main issue.

Thanks we'll make sure that folder is excluded.