Noel Borthwick

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

Hotfix preview build 93 has been posted to the EA channel. 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. PS: Some of these issues predate CbB and have been present for more than 10 years 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

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

@NealClark I am unable to reproduce any of these behaviors. What build are you running?

Generally speaking it's risky to conditionally target host versions because the version number doesn't necessarily mean functionality changes. Some plugins also do this and it can lead to unexpected issues.

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.

Thanks for checking. What was the issue?

Hotfix Build 91 has been posted to the EA channel. 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".

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.

Not sure if you registered the DLL or turned off logging. You should definitely register the DLL since we use it for logging.

The WavesLocalServer Has nothing to do with Windows. Its its an unintended consequence of the path used by the WavesLocalServer Process that also happens to use the sndfile.dll internally. Waves has already acknowledged it and will be fixing it in their next update.

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 @Sergio Miranda

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.