Noel Borthwick

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.

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.

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?

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.

Today the only way to pick the automation envelope is through the edit filter on the track or bus. We'll consider adding a shortcut from the parameter itself in the future.

Send me a link to the dump file and I'll take a look.

We should offer to auto switch the driver mode to WASAPI when no audio devices are detected.

You have two choices. 1. If you are running in ASIO mode make sure that "Suspend audio engine when cakewalk is not in focus" is enabled. 2. Use WASAPI shared mode.

Yes you can certainly do this. Its as simple as selecting source category = tracks. You don't need to change any of the bus enables since when you are bouncing with source as tracks anything downstream from the track is automatically disengaged. See the settings in the picture. There is no way for the sends on the original track to affect the newly bounced track. Perhaps what you are hearing is confusing you. Watch the track meters and they should be unaffected.

Cakewalk doesn't support multichannel vst plugins. It's a niche that not many people requested.

Is your problem only with virtual instruments? What if you have a normal audio project. Do you see the same dropouts there? Also send us a link to the project that has the issue.

No because 5 replaces version 4.

Does it matter which fader is moved? Do you hear noise when moving a fader that doesn't control that signal, such as the fader for an empty track?

Are you using ASIO mode and do other applications work on the system? Based on the video it looks like the driver is not processing callbacks properly. That could explain why there is no dropout if the frequency of the audio callbacks isn't fast enough. Any change with the latest release? Without having access to your machine there isn't a lot I can do to diagnose the problem further. Have you done any system troubleshooting? Try other audio programs and see if you can play without audio interruptions. If the same issue is happening in other apps then its a system or driver problem. Does the problem happen in only a single project or can you reproduce it even in a test project without virtual instruments?

You can look at the data being stored in the BLX (BandLab project interchange) files. They are JSON files with the properties embedded.