Noel Borthwick

Thanks for your feedback but please make a separate thread for it or consider the feature request forum. This thread is exclusively for Early access 2021.09 release specific features.

2021.09 Build 133 has now been posted. This is the final release candidate so please check this out as soon as possible and let us know if there are any regressions. Details in the link above. Thanks for all your support and diligence in reporting problems!

The first thing to do is stop using ASIO4All. Its known to cause incompatibilities and we don't support it. The next build will have a warning asking users with ASIO4All and some other known incompatible drivers to switch to WASAPI mode or use a different ASIO driver.

We'll there have been a million changes to the engine over the last 3 years but the one you are seeing is a change to use a higher quality zPlane elastique time stretching algorithm. This release also has improved transient detection.

@Matthew Simon Fletcher please send a project that can repro this ASAP. I’d like to investigate it before we release

@Mark MoreThan-Shaw Would you be able to share a project with which this can be reproduced? I suspect the crash to be data specific.

Thank you that dump shows the crash reason. We'll look into it.

Yes please send this ASAP. Are you using sidechains or aux tracks? You will need to upload the file to a fileshare like dropbox etc and send us a link.

We're not making any more interface changes in this release sorry.

Some discussion of optimizations in win11 https://www.tomshardware.com/news/microsoft-details-how-it-made-windows-11-faster-than-windows-10

@stevebell001 20 MB is pretty small if you zip it you may be able to attach it to the forum itself. Without a dump we can't investigate crashes. You can upload it to google drive, dropbox, one drive or any other free service and post a link.

@Norave can you send us a zip of a project file that exhibits this?

The bounce to clips issue was reported and fixed two days ago. You can download the fix below. Also in the next release we have optimized this even further. The delay was because of effects flushing which we're now doing for bounce.

@Milton Sica We are unable to reproduce any difference in load times. Please send a project file that exhibits this.

@stevebell001 Its unlikely that this is related to this release but coincidental. However, if its crashing please attach the dump file that is saved when the application crashes and we can investigate. The crash dialog lists the dump file.

@Matthew Simon Fletcher it seems unlikely to be related to this release since there aren't specific changes I know of that would impact synths, Can you send a pared down version of the project with steps so we can try and reproduce it?

Apparently you have run into an untrappable exception lol @Mark MoreThan-ShawHave you tried looking in the windows event log as well?

Opening a project is slow? Have you tried to rollback to verify if its really due to the new release?

TBH I'd be surprised if any DAW did this specific thing. I'll continue to investigate it in case I can think of a better way.

Hm you added it to Cakewalk initialization section right? it should show up in preferences | initialization file. I've not seen crashes not show up with the highest level since this also catches heap corruption.

@rocstudio uad can't handle multiple plugins in the same session set to the same sample rate. Issues like this can be project specific so if you have a recipe save a simple project file with audio and send me a link.

I've implemented some multiprocessing optimizations that should make it much faster to flush plugin tails now. Thanks for your help testing this.

Hi @Andres Medina what you are doing isn't unusual or wrong, but it would be quite complex for us to make soloing a track smart enough to discover the entire downstream signal chain going to buses and automatically activate any other tracks that are feeds for sidechains in buses. The changes I made earlier were specific to discovery of interrelated signal flow exclusively within tracks (and aux tracks to some extent). It won't handle a track that outputs to a bus that indirectly relies on a different tracks output, unfortunately. So yes what we have is a major step to improve some common sidechaining requirements but not every imaginable scenario. I think the only solution for these is to manually render them for now.

@rocstudio thanks for doing these tests. I appreciate it. Based on my findings it appears that UAD plugins don't really process much faster than realtime so this might be a known limitation. I'm trying another optimization to parallel process this which may help. I will PM you directly to try something soon. BTW did you try bouncing at your playback buffer size instead of using 350? I wonder if UAD plugins don't like large buffer sizes and that causes an issue.