Noel Borthwick

Can you send us the project file? Something is likely failing when loading the UI resulting in the strip being partially initialized. Also which build of CbB are you running? Have you checked if this happens in the prior release (09) as well?

Interesting article on win11 performance with alder lake CPUs https://ph.news.yahoo.com/intel-12th-gen-alder-lake-cpu-windows-10-11-streamers-multitasking-045701919.html

Tip for using it live. Turn off dropout detection. This will let the app keep running even if it runs into a potential dropout condition. Much better than stopping playback! Set this to TRUE in preferences | configuration file.

This is how to set it up. After a bounce I get this As you can see it respected the track lengths. As mark said "Tracks through entire mix" does not respect the track length. We'll try and make that work the same way as well.

Yes its hard to find since it depended on the order in which the sends from the patch point were created. The bug has been there since the creation of aux tracks so its good to get this fixed.

@Maxim Vasilyev thanks for sending the project that exhibited the problem. I was able to track down the cause and fix it for the next release. The main issue was that the internal patchpoint bus associated with the aux track was somehow sending twice to the aux track. As a result the gain was boosted. I'm not sure what led to the sends being duplicated but I've made the code that handles this more robust and it wont allow that to happen now. Also at load time it automatically gets fixed so that it routes only once to the aux. Did these projects originate in an earlier release of SONAR by any chance?

We looked at TDR Nova and couldn’t quite figure out how that plugin works. You may want to contact the developer if there is an issue.

You could always do this. Select source category tracks. Make sure that you have nothing selected and export the full project. It should automatically size the export of the tracks based on their length. Fully described in the release notes as well. A note about selection and the Tracks export category: When the source category is Tracks, the project selection has a special meaning: Having a project selection means there is also a time selection. So if you have tracks selected in your project selection, then all the tracks chosen in your audio source will be exported at exactly the length of the selection. In other words, the length of each tracks’ audio file will be the same. If you have nothing selected in your project, then no specific export time range has been set, and the length of each tracks’ audio file will be the length of each individual track.

Glad you could figure it out. All the scanner is doing when not actually scanning a plugin is enumerating files on the system and checking timestamps and reading from the registry. That should be very fast unless something external blocks those accesses (as AV's typically do with any executable files and the registry). When scanning plugins the plugin is loaded and queried for various parameters. This can also be blocked and made very slow if the AV needs to check for viruses. This is the main reason we don't recommend running AV's on DAW's. That said I've never had issues with Windows defender slowing down the DAW. Your mileage may vary with other AV's since some are very aggressive.

As far as delay compensation goes playback and monitoring is identical. Delay is queried at the time of inserting the plugin as well as when playback starts. And also if the plugin notifies the DAW that delay has changed. The latter is more deterministic in VST3. Re 3 it really sounds like you are monitoring something using direct monitoring. If you are listening to the band AND the backing track monitoring through the DAW's outputs it should be in sync. Of course if you are listening to acoustic sound it wont be in sync. Many people use this scenario in Cakewalk so there is most likely a simple explanation for this.

Singapore time is about 6 months behind us ?

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?

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

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.

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. Add/Remove programs should typically display something like this on a clean system. The first step to try before attempting reinstallation is to attempt to repair any redists you have. Go to Add | Remove programs and search for Visual C++. That should list all redistributables you have installed. It may look like the list above or you may have some older entries as well. To try and repair them click the ellipsis next to the entry (as shown below) and choose Modify. It should show a Repair option. Try repairing your redists and then check if your problem is resolved. If you are running into problems and have older redists installed, you can uninstall all redists and run the latest Sonar installer. However, it's 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. This installer also attempts to repair a broken C++ library installation. Running this installer will reinstall all required runtime library dependencies and should in most cases be able to recover from a damaged installation. NOTE: In some cases, you may need to manually download the latest Microsoft X64 redistributable and then run a repair install. This should repair a damaged install which can happen when another application has overwritten the DLL's with faulty versions.

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.