Noel Borthwick

Hi @eric chevrier, Is this an 8 physical core 16 virtual core PC? Can you provide some more detail on what you saw before this update? Are there fewer missed buffers at lower latencies? Also try with plugin load balancing off and on. @Blades, @Glenn Stanton do you see any difference in this release?

Which automation problem are you referring to? Can you provide a project file or a step by step recipe?

@AdK Studios thanks for the feedback. Some of the automation issues reported were bugs already fixed in the latest 2021.01 release. ESP the freeze issue. The plugin automation issue with pitch riser is also the identical issue. The bug was that in 2020.11 freeze or bounce could cause envelopes to get orphaned. If you had hovered over the envelope he would have noticed that it showed a tooltip saying “orphaned”. When automation doesn’t render this is the issue 99% of the time. Regarding clip based workflow our piano roll is currently not particularly tailored for that but well consider allowing a mode to show only selected clips. Its not something that most of our users have requested in the past. Regarding automation accuracy, its not clear what your buffer size is. You are running a VST2 plugin and in VST2 automation is only accurate to the buffer size, unlike VST3 which is sample accurate. If you want sample accurate automation you should only use VST3 plugins or run at a very low latency. This could also be something specific with the plugin since I have not encountered this specific issue. If you share a simple project file with a repro we can look into it. This is inaccurate. Its by design that bus effects are not applied and has been this way in every version of Cakewalk going back all the way to 2003. As far as stems go its intentional that source category tracks does NOT include bus automation since this is the typical use of track stems. If you want bus stems you should export with source category buses and make specific buses for the stems that you wish to deliver. Alternatively you can simply solo tracks you want and export with source category set to buses to get the results you want. I do agree that when source category is set to tracks, we need to gray out the bus options. That’s just a UI oversight.

Only Waves 12 has that component AFIK.

If you are running Waves V12 plugins, please read before installing the 2021.1 Update. There is a bug in a Waves V12 program called WavesLocalServer that locks a component used by Cakewalk and prevents the installer from updating it. If you receive the Code 5 error trying to replace sndfile.dll from our installer, the current workarounds are, either: 1. Reboot your PC before upgrading; or 2. End the WavesLocalServer process from within task manager, and click Try again Waves has been notified of this problem and will address it. NOTE; This issue only affects the installer and doesn’t cause problems with the normal execution of Cakewalk.

Reboot your pc and retry the install.

Yes we delayed to address some API changes for the BandLab back end. It should go out today. Preparing rockets to launch. 10..9..8..7..6..5..4..3..2..1....

Steinberg has fixed this but have not released the patch to elicenser. They sent me a patch over a month ago. If you need it PM me and I can forward the link.

Thanks for all the incredible feedback and participation folks. We plan on releasing the final update publicly this afternoon in a few hours. Keep an eye out for a notification in Cakewalk.

Try rebooting your PC and retry. Also for updates you don't need to use BandLab assistant anymore. Its all done inside Cakewalk by using Help | Check for updates.

Could any of you folks running high core count PC’s please try the latest hot fix? ESP those running AMD Ryzen systems. There are some optimizations and fixes for MMCSS that might improve performance. If nothing I just want to make sure that it doesn’t cause any issues.

The idea of posting early access is for users to test them early and report back if there is a regression. So its in your best interest to install it early, considering how easy it is to roll back if necessary. All these changes are going into the final release which will go out shortly.

This is resolved in the EX hotfix posted yesterday. Please verify

Build 93 has been posted. Thanks for your support testing this hotfix. In particular, please test ASIO with MMCSS enabled (and disabled) since there are some specific optimizations to the audio engine in this area that should make it more efficient. You will need to reboot your PC after installing this update to test this properly. The following new fixes are in this build. Ripple edit delete using section overlaps crops the clip at the end of the left sections MMCSS threads not properly unregistered on engine termination MMCSS threads could exceed quota with repeated changes to preferences CbB no longer attempts to set ASIO thread priority when MMCSS is not enabled Plugin Load balancing threads were not being released Remove unexpected dropout message when creating or loading new projects Unexpected sample rate conversion message when bouncing audio Add Instrument Track not putting audio track in folder / unable to remove from folder

Indeed, good catch! You shouldn't be seeing a sample rate conversion message unless actual sample rate conversion is occurring. The reason its showing it is the export process uses the same component to do bit depth and format conversions and this is triggering the faulty message. Its not actually doing any SRC. I'll fix it for the upcoming hotfix.

No just a few hours We had a few builds today.

Build 91 has been posted. It includes fixes for some more reported and preexisting issues. Freezing a synth could cause synth automation on all tracks to get orphaned MMCSS now assigns all threads to the same MMCSS task groups for better efficiency. MMCSS thread limit has been increased to 128 to handle high number of cores. Increased contrast of PRV clip outlines so they are visible regardless of current theme. Arranger: Fix for trailing notes being incorrectly picked up by a section. Ripple All not working when deleting from Arranger Inspector - additional fix for handling del key in the inspector. Ripple Edit delete Section with overlapping notes at the end not working Skip non automatable parameters in choose parameter dialog Updated CWAF tool to latest known version number string to "27.13.0.xxx". Please report back in the main thread ASAP if you have any issues.

Crash with Kuasa plugins is fixed. Download the new hotfix.

An updated hotfix build has been posted which includes the following extra fixes: Crash inserting Kuasa plugin Ripple All not working when deleting from Arranger Inspector Adding a new articulation event should default to velocity 100 Fixed bitmap memory leak in when editing using audio snap that could cause blank screen VST3 Host Bypass does not work with plugins that report it as non-automatable Automation write not working with certain VST2 plugins until envelope was created Please report back in the main thread if you have any issues.

Yes as mentioned the crash is fixed. Automation also will work but you will need to manually create the envelope rather than recording automation via the plugin UI.

@Traveler thats not a crash. Your issue has already been solved. See this thread.

@Sergio Miranda Which error? The crash issue is fixed on our end. I've also fixed another issue with host bypass for this plugin. However the fact that you cannot write automation by moving plugin knobs is a bug in the plugin. They are not sending the proper begin/end edit transactions to the host so we don't sense those changes. I am referring to their VST3 version.

@Sergio Miranda I've solved the crash issue. It was a problem on our end handling the host bypass from this plugin which is not automatable. However note that this plugin is not properly following the VST3 spec for parameter notification so you cannot write automation via the plugin in CbB. I can follow up with the vendor on this but you can also log it with them.

That's great news. I'm happy that they responded so quickly and fixed the issue.

Are you getting a crash dialog or is there app shutting down? If the latter it's likely heap corruption caused by the plugin and may not be something we can fix. If you get a crash dialog then you can also manually capture a dump file from task manager.