Noel Borthwick

That something else would be environmental. As mentioned there is nothing in the code that changes behavior of loop toggling.

Awesome thanks for verifying that.

Please refer to the dropout codes help. Code 5 : Disk reading overloaded and could not keep up with playback pump : Increase playback I/O buffer size This is completely unrelated to any work in this release. Try and breakdown your project and troubleshoot whats causing the load is the only suggestion I have. There are literally no changes to how toggling looping works since 2012.

Likely coincidental. There is zero change that would have impacted dropouts. What is the dropout code? Is it happening on a specific project? Without details its impossible to follow up on such cases.

Not seeing anything like that here. Multiple people have tried it. It is likely specific to your project. What drop out code are you getting?

@Keni please download build 28.02.0.027 which is linked from the top post in this thread. Let us know if it solves the issue.

No need now. I've managed to locate the cause and we'll post an update shortly for you to try.

@KeniPlease send a mini dump file.

@Craig Reeves can you please verify whether build 28.02.0.026 resolves the autotune issue? We don't have any way of verifying it since our license has expired.

This is something very specific to your system and nobody else has reported it. So without more information we have nothing to proceed on. We’ll start a PM thread with you to collect more information so check your PM’s and provide more information. @Will_Kaydo please respond ASAP since we are planning on releasing this update soon.

@Craig Reeves Please read the prior threads. I posted an update to try that may fix the auto tune issue as well. The build linked in the first post in this thread is the latest.

The EA build has been updated (please redownload from the main post in this thread). This fixes the problem with Melodyne or any other ARA plugins that are used as track effects rather than region effects. Please verify that this fixes the issue.

@Max Arwood @KWILD If you are running AutoTune Pro can you please check if its being reported as an ARA plugin? I believe it might be because of this: https://antarestech.force.com/s/article/Auto-Tune-Pro-ARA-Compatible-Host-DAWs You can check this by looking for it in the clip region effects menu. If you don't see it there look in the registry under HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Cakewalk VST X64\Inventory Under the record for autotune see if the isARA flag is set to 1 in any of the records for it. If its exposing itself as an ARA plugin and you are using it as a track effect then its likely to be the same cause as the melodyne issue that was reported. We'll be posting a fix for that shortly...

There was indeed an issue with using Melodyne in an effects rack rather than a region effect. I've fixed that issue now. @Laurence Levin are you also using Melodyne as an effect this way? I'm curious why anyone chooses to use melodyne as an effect when ARA is the proper way to do it.

@Jonathan Wade which version of melodyne are you using and are you using it as a region effect? We're not seeing any issues with follow playback in this release. Are you trying to manually transfer audio in melodyne? That is not required since using it as a region effect clip automatically handles that.

@Scheffler what message? Please post a screenshot. You should be able to install the EA directly through help | check for updates.

Yes this was fixed.

This thread is only to discuss issues related to the early access release. Please don't post unrelated topics here.

@sreamsCan you set exceptionhandlingseverity to 7 in preferences config and retest?

Read the release notes. Its a new path that is included as per the VST3 specifications. This has nothing to do with key bindings.

Key bindings are stored in the location that Kevin listed. If they get lost its most likely some registry corruption or something restored your registry. Antivirus programs are common culprits or even Windows updates sometimes. The cakewalk install had nothing to do with this. You should always keep a backup of your key bindings by exporting them if you have a lot of custom changes. If making changes to the key bindings in Cbb is not saving its likely that something is blocking writes to the registry. Try changing something else such as enabling 64 bit engine and see if that setting sticks. If not you have a registry issue.

Hi everyone. The Cakewalk Web Installer has now been officially released. To download it, choose Download and then pick the Cakewalk Installer instead of BandLab assistant. Note that once you have Cakewalk installed all subsequent updates can be done directly from within the application via Help | Check for updates. Notifications for available updates are also automatically shown by default. There is no need to use BandLab assistant now unless you wish to do offline authorization for Cakewalk, or you want access to BandLab loops.

Please send a link to a project file with the issue as well as the steps to reproduce it including the name of the fxchain preset

@chris.r please capture a dump from task manager and send us a link. We can't investigate hangs with out this.

We'll look into it. The issue dates back to pre-SONAR days. It's amazing how some of these issues never get noticed until many years later