Noel Borthwick

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.

@Sergio MirandaWe’ll take a look but can you provide us with the minidump for the crash and the project file?

@Sergio Miranda is this crash new to the 2021.01 release? Where was this reported earlier? Can you send me the minidump since thats the only way to diagnose easily. Instructions in my signature. Also please send me the project file that crashes.

You can turn off device change notification toast messages in Preferences.

[Updated to build 93] This hotfix addresses a few problems users have reported since 2021.01 was released and also includes some new fixes and optimizations. The following issues are addressed: Projects containing certain plug-ins fail to open in 2021.01 release. We received reports that some SoundToys plugins cause projects to fail to load Crash inserting Kuasa plugin Deleting an articulation occasionally splits it into two smaller but invisible articulations Show/Hide Articulation Pane in PRV does nothing if there are no articulations on the track 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 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. [Requires reboot after install to take effect] 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 latest known version number string to "27.13.0.xxx". 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 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. If you are still seeing any issues after installing this hotfix please report them in the main 2021.01 feedback thread to keep reports centralized. Please note that this is an early access release - we should officially release this sometime next week after collecting more feedback. Download the 2021.01 hotfix (build 93) Should you need to revert to the 2020.11 release, you can download the Cakewalk 2020.11 Rollback installer. To install, download and run the hotfix installer. Note: If you are running Waves plugins, you may need to reboot your PC prior to running the installer if you receive an error that sndfile.dll is locked.

@Mick Moreau and @Tamas Erdosi I just PM'd you a link to an installer that Steinberg sent us. It should fix this problem.

@Max Arwood where did you see a Waves Cakewalk update?

If you are dragging files its the order in which they appear in the selected file list. BTW if you drag multiple files into a lane it will auto insert in subsequent lanes and create new lanes as needed. I dont think there is a way to put the files back to back today.

@Ken MThanks for the report. Which version of CbB were you running? Most likely your media browser was pointing to the desktop where the zip files are present. Please check if this is the case. If you point the browser to a different folder and resave the problem will not occur. However I was under the impression that this issue had been addressed earlier. It was an issue with the shell browser extension we are using rather than Cakewalk itself. We'll look into it for the next release. Thanks for the detailed report. You can PM me the process monitor log.

See this post

Do you get a crash dialog? That is the log. If so send a link to the dump file and we can tell you why its crashing. Link in my sig.

I have not followed this whole thread but your symptoms sound like you are getting phase cancellation in the signal path somewhere by doubling your input. You should not use direct monitoring and input monitoring though the DAW at the same time or you are doubling and causing potential phase issues. You may get better help if you post the project you are having trouble with to allow others to look at three rooting.

In the picture above, you can drag the file from the browser or windows explorer to the divider between the tracks view and clips view (where the dB scale is drawn) or you can also drag it onto the track pane itself and it will automatically place it at time zero irrespective of the current position.

Just rename the file to .ogg. Its the same file format but oga is the correct file extension for ogg audio files. See this link.

We'll look into it. Its a harmless if annoying notification.

Edge is part of the operating system now whether you use it or not. This is not related to BandLab Assistant, webview is used to serve up html content and to handle the security requirements for single sign on authentication.

Another quick way is to drag the files to the track view or the divider between the TV and clips pane. This is a shortcut to insert at beginning.

Ive never understood how people can tolerate running such old builds of Cakewalk. 8.5 and SONAR literally have thousands of issues that have been since been addressed. The only reason I see some people running Win7 is for aging hardware that is no longer supported with drivers. We’ve said before that we don’t have resources to support Win7 anymore and only allow it to install as a courtesy. If it stops working due to new features we’ll have to block it installing at that time. The older builds will potentially work but would still need authentication as before.

Yes. Also turn off any surround stuff as noted.