Noel Borthwick

I didn't realize you posted a video. The app is closing when trying to load TyrellN6 so try skipping that synth in safe mode and see if it loads. Also check if the default sample rate matches the project sample rate as suggested earlier.

@Stephen LathamWhich synths are you loading in the project? Does the application crash or does it appear to hang? Also what sample rate did you create that project at - is it different from the default sample rate for new projects that you have set in preferences | Audio?

@JoeGBradford what is your case number? I can look at it.

Some clarifications. There is nothing wrong with your VST scanner version. 6.0.3.0 is the correct one. If you have the scan button grayed out its likely because something (antivirus, registry corruption, or personalization failing) has messed up the app install and the app doesnt have the path to the VST scanner anymore. Look in HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Cakewalk VST X64 for a value of VSTScanPath. It should point to C:\Program Files\Cakewalk\Shared Utilities\VstScan.exe If not, you can redo the personalization for Cakewalk. To do that, launch Cakewalk while holding down the CTRL key. This will show the personalization dialog. Click OK and let it finish. After that VST scan should be accessible again.

Is your default sample rate set to the same sample rate that the project containing Iris is set to? If not, loading the project will crash Iris. This specific issue is a bug in Iris. Cakewalk first initializes iris at the the default sample rate and later changes to the project sample rate. Iris crashes when loading its state at the default sample rate. The good news is that I have already addressed this from our side for the next release even though its technically not a bug - all other plugins handle this. I will be reporting this to iZotope as well. You can resolve it for now by setting your default sample rate to be the same as what you used in the project containing Iris.

Have you taken a look at the release notes for the 05 release? We fix scores of issues every release (most of which are preexisting and some which are workarounds for problems not even directly caused by Cakewalk) If you don't consider that progress I'm not sure what to say. We are not aware of any of the issues you list. There is no way to know if they are fixed until you actually try running the latest release. If you have concrete ways to demonstrate them in the current release then log them specifically. If they are issues within our control we do our best to address them.

Or try your audio interface on a different PC.

Its already fixed for the next release.

@Marc Bleuwart This is not normal behavior. How large is the project? Can you share the project file with us so we can try and reproduce this? When this happens do you lose mouse control - i,e can you continue to open menus in Cakewalk etc or is it just the transport that is blocked? Do you have console view open?

This was the symptom of scheduling model 3 which was fixed in the latest release. Did you have thread scheduling model set to 3 earlier?

@Helos BonosNo the 2020.05 release is one after the arranger release which was in April. Check your about box. There are lots of optimizations in the 05 release.

Have you tried this again with the latest 2020.05 release?

Can you be specific about which FX chains cause this issue?

Right this is incorrect information. Of course audio benefits from multiprocessing. Turn off the multiprocessing engine and run a moderately large project and see what happens

Yes please copy and paste the list of missing plugins from the popup message. Are these 32 bit versions, VST2 or VST3? If these are Cakewalk plugins and you send the project file we can try and reproduce it.

@Rick Paul I'm not sure if you have read the feature overview.

@CJ Jacobson the zoom was changed primarily for mouse users so it zooms about the cursor rather than the center of the screen. For users doing sample based editing its important to be able to zoom in close from the cursor not an arbitrary center of the screen. However when zooming remotely via a surface I can see that it may be desirable to have the prior behavior. We'll discuss it for next release.

@Tim DavilaYou prefer it to modify controls? People found it very error prone because they were inadvertently changing values when they wanted to scroll the view.

Are the plugins actually there but not visible in the menus? If so you may have a plugin layout loaded that doesnt include all plugins. Have you tried opening a project that references one of the missing plugins - does it load ok or do you get a missing plugin prompt?

@Michal Mikulski I'm not sure what you mean by disabling making a track stereo. We fixed bugs where bypassing a plugin wouldn't remove its forced interleave. If you were using that you were relying on a bug. You can still pan a mono track so I don't see what the problem is.

@Tim Davila both those plug-ins (we tried it from the version 9 suite) don't exhibit any issues here when opening the UI in CbB or bypassing them. Its likely something system or project specific. If you can reproduce it please provide a project file. We don't have any control over what happens when you open a plugin UI. If you have plug-in specific issues regarding that, its best you log a case with the plugin vendor. They will also require some steps to reproduce it.

If you are getting noises when opening the plugin UI those are problems with the plugin and should be reported to the plug-in vendor. The same applies with plug-in load balancing on. If the plugin's do not support it properly you shouldn't use that feature.

Please send the project file so we can investigate.

Glad it's solved. There is also an option to allow prefader sends to be muted when the track is muted.

There is no way that the bounced track can send without creating sends. Are you sure you dont have prefader sends on the other tracks? Mute the bounced track and check if you still hear it.