Noel Borthwick

That means you are running the wrong rollback. Make sure your are running the one from here https://discuss.cakewalk.com/index.php?/topic/33755-current-release-202109/

I'm thinking of adding a parallel export to wav for other encoders

Which version of Windows are you running? This sounds like you potentially have a bad installation and some components did not install properly if its crashing immediately on creating a new project. I suggest rebooting your computer make sure you don’t have Antivirus software running and then try reinstalling Cakewalk. You can also rollback to the last version and reinstall the software again.

@Jean Corivo Have you tried rolling back to the prior release to verify that this is actually specific to 09? Upsample on render depends on whether the plugin supports it. Not all synths support it properly. Also by any chance are you setting the render buffer size to a higher value?

I can repro it with your file! I'll investigate it thanks.

Yes you can create two tasks and they will render the wav and mp3. Its not rendered at the same time however it will do two bounces.

In addition to what Jon said, have you set your bounce buffer size to a high value? If so set it back to Follow Playback buffer size and retry. Also you can easily disable the plugin flushing as mentioned in the release notes: Edit > Preferences > Audio - Configuration File: BounceFlushTailsMaxDurationSec=n (0 to 60; default is 20; set to 0 to disable tails flushing) Effects tails maximum flush length while bouncing (seconds).

Yes we should not be displaying that error message. Its a known issue thanks.

This is a known issue explicitly mentioned in the release notes. Its out of our control: Caution: Some plugins can be unstable or crash with large buffer sizes so use this with caution. Depending on the plugins used, we recommend using moderate sizes like 50-100 msec rather than higher sizes. Also if you are using plugin automation, large buffer sizes will not sound smooth if you are using plugins that do not support sample accurate automation. Several IK multimedia plugins also have this issue.

@rocstudio I'm not seeing any cases where audio disappears when you do a bounce to clip with buffer size set to 350. If you can reproduce this can you share a zip of your project folder so we can look at it?

Yes the that buffer size is global so is used by bounce to clip as well. That part is not new to this release. Perhaps we should ignore that setting for bounce to clips since it has no UI.

Possibly assuming he is using 32 bit plugins. I did a test rendering a large project with over a hundred tracks and a hundred plugin instances. I bounced the whole project to a new track with a buffer size of 10 msec. Then I did the same test at 350 msec. Not only did the two renders align perfectly, they null cancelled when I phase inverted. So if there is a problem is isn't in the actual bounce code.

@Toy there is no difference between setting bounce buffer size or manually or changing the audio latency to a higher number and redoing the bounce. Behind the scenes it has the same effect except its not changing the driver latency. If you are seeing differences its due to the plugins in your project and out of our control. You can repeat this test by changing the playback buffer size and redoing the bounce each time with the default "PlayBack Size" option selected. i.e. Do this test: Export with bounce buffer size set to 20 Export with playback buffer size set to 20 and bounce set to Follow playback Compare the two wave files. They should be identical assuming you set the buffer size the same Another thing to try: Bypass all your plugins and do the test again. If the audio aligns then the issue is caused by one of the plugins. You can use a process of elimination to find the problem.

@Helene Kolpakova Re 1 the sources are per project while export presets are global. So this isn't really possible without having a concept of per project presets which seems a bit overkill. I'm not sure I understand your workflow and why you need it to remember that state though. We could possibly consider remembering the selected sources state for the duration of the editing session but I'm not sure how useful that would be. Re 2 its already available. Go to the media browser tab and choose the "Project Audio Export Folder" preset. That should take you there automatically.

Fast bounce is not related to the buffer size option directly. All it means is that Cakewalk exports as fast as it can and is not gated by realtime playback. The custom buffer size itself only applies when Realtime playback is unchecked in the 2021.09. The only change in 09 is that fast bounce is now renamed to "Render in real-time". So to do the equivalent of a fast bounce make sure render in real-time is unchecked.

Please keep this thread related to the 2021,09 release specific features. For other general inquiries create new threads.

>>Up to E.A.134, all "BOUNCE BUFFER SIZE" settings are invalid in ASIO. Yes this was a bug that was fixed >>-As a result of the setting being enabled in E.A.137, there are no options other than "PlayBack Size" in my plug-in. I'm not sure what you mean. In the latest release you can either use playback size or any other buffer size. If you leave it at playback size it uses the driver latency setting otherwise its whatever value you specify. As described in the release notes depending on plugins used, use conservative buffer sizes such as up to 50 msec. The only benefit to larger sizes is to speed up export time.

Its impossible to understand looking at a screenshot. You will have to send the project file if this is a change in behavior and describe the steps you are taking. Most likely there is an audio routing issue in your project.

@Skyline_UK There should be no decrease in bounce speed. The only new step added is to flush effects tails. Please read the release notes there is a way to disable that if necessary. In fact if you are bouncing the entire project it should be faster because we no longer duplicate the project in memory in that scenario. Also check your audio buffer size. If its set low bounces will be slower unless you use the new bounce buffer size to set it to a higher value.

I think you may be confusing it with an issue that was fixed in the EA. There was a bug where in ASIO mode it was not respecting the bounce buffer size and defaulting to the playback buffer size. In the final release it will use the bounce buffer size unless it is set to "follow playback buffer". If you are using a high bounce buffer size some synths do not handle it properly so this could be what you are seeing. If so set bounce buffer to "follow playback buffer"

It is not.

Are the dropouts actually impacting your work or is the message and audio stopping bothering you? If so you can turn off the dropout detection here:

Not seeing any issues with selection in tasks. I created multiple tasks some with entire project and some with specific selections and they all rendered properly with source category Entire Mix

The bounce buffer size is global and is not saved per task. This is intentional

Thank you everyone for the incredible feedback and participation this early access! 2021.09 has now been officially released. Please use the main 09 release feedback thread for any further comments.