scook

It might help to provide hardware details. All we know at this point is a preamp model going through some Focusrite interface. It seems strange that the information to the right of the slider in the mixing latency section of Driver settings reports 256 sample buffers but the ASIO info below that show values more in line with 512 sample buffers. I believe some Focusrite devices have large safety buffers but have no first hand experience with their hardware. Still the difference between the two sets of numbers does not look right to me. What does the Focusrite ASIO client report? I was under the impression Focusrite supports adjusting ASIO buffers from the DAW, however; the Buffer Size slider is disabled. This indicates the driver does not support the feature. In addition to the supplying the interface model, it may help to know the driver version.

Is Focusrite the device shown in the Record Latency Adjustment section of Preferences > Audio > Sync and Caching? If this page is not visible in preferences, click the Advanced radio button at the bottom of the preferences window. Is there more than one driver shown in Preferences > Audio > Devices?

LICEcap What I see is a continuously changing tempo in the transport module. My guess is this is playing havoc with the plug-in. Tempo synced plug-ins need a steady tempo. Given the current tempo map, tempo synced to host may be a bad choice. Could set the tempo to an average of the tempos or smooth out the tempo changes in the Tempo view. Changing tempo using tempo synced plug-ins can cause audio glitches as the plug-ins sync to the new tempo. This may be avoided by using clip based effects and a steady tempo in the clip or aux tracks/buses with the plug-ins at fixed tempos switching between the tracks based on the current tempo.

I am pretty sure @bitflipper does not use Pace protected software.

Something else to add to your .sig May want to create a separate thread for this. I am sure someone can help. I use a plain MIDI keyboard without any control surface features.

Worked for me before I posted. What I did notice is the BPM in the plug-in only updates when data is streaming through the plug-in. That is why I suggested looking at the tempo view. From the image there was no way to tell how the cursor arrived at its current location and if the plug-in UI had yet to update.

I found BandLab a little tricky to setup. It's pretty incredible a DAW can run as a Web app. Regardless CbB should be much easier to work with especially coming from another traditional DAW. Glad to here CbB is working for you.

Give the guy a break. The OP, new to BandLab products and the forum mentions only BandLab in his first post and it only took 2 more post before we discover immediately after that That's pretty quick. Hopefully he will come back and report success or ask for more help. Pretty sure we can offer decent help for CbB. I would recommend a bit of "do as I say not as I do" advice though. Consider adding Hardware details (both PC and audio interface) and OS in the signature section. This is found by clicking on the user name in the upper right, click on Account Settings then Signature. Adding this info in .sig can help a lot when offering advice. Also mentioning the version info found in the Cakewalk by BandLab About screen when posting is helpful.

It is confusing

Correct. This forum and the DAW specific advice provided here is for Cakewalk by BandLab, a Windows-based DAW. AFAIK, there is no comparable forum for BandLab but there is a Facebook group.

IIRC, Samplitude installs a re-badged version of ASIO4All, Like all generic ASIO drivers (Cubase and Fruity Loops install them too), they should not be installed if one has a manufacturer supplied driver. This may be the case with Avid too, IDK not having used ProTools or recall reading about this before. If this is the case, one way to avoid problems is remove all the entries in HKEY_LOCAL_MACHINE\SOFTWARE\ASIO except for the drivers provided by the hardware manufacturer. There should be at most one ASIO driver per interface.

Don't have these plug-ins and they don't have demos so can test them myself. What does the scan log show? If you have not scanned with the scan log enabled open VST Preferences in CbB select the "Scan in Sandbox" and "Generate Scan Log" options, make sure the two rescan options are NOT selected. click the Reset button. This will clear and rebuild the CbB VST inventory in the registry and write out a log.

My first guess is the audio interface buffer is too small. Unfortunately this cannot be adjusted in WASAPI Shared mode. Try a different driver mode in Preferences > Audio > Playback and Recording The audio interface buffer is set using the buffer size slider in the Mixing Latency section in Preferences > Audio > Driver Settings.

Try increasing the buffer size setting in Mixing Latency section in Preferences > Audio > Driver Settings Depending on the driver mode set in Preferences > Audio > Playback and Recording and interface driver this may be set using the slider or an ASIO client supplied by the audio interface manufacturer.

The Sonitus plug-ins were never ported to 64bit VST Are there any tempo changes in the project? Verify by reviewing the data in the tempo view.

the support email is support@cakewalk.com FWIW, when released there is a feedback thread created for the release. For example, here is the one for 2020.09 When encountering a problem with a new release, it is best to report it in the feedback thread. When posting problems here and emailing support in addition to PC hardware specs, information about the audio interface and OS is helpful. How to report hangs and crashes The load an FX chain preset in the FX rack use FX Rack context menu. The PC does not have this menu so the preset option is part of the FX chain.

CbB started with the SONAR Platinum source code. CbB installs as an upgrade to SONAR. The DAWs and content directories are separate. The shared folders are updated. Here is how to install CbB using BandLab Assistant. Both DAWS will be available. All plug-ins installed with 64bit SONAR and user added plug-in will be available in CbB. CbB can open any projects created by Cakewalk DAWs including SONAR. Just like 64bit SONAR, CbB cannot load 32bit DX plug-ins. CbB stores projects and data just like SONAR on local drives.

Then end result is the same. How it gets there is slightly different.

Ultimately safe mode must load everything just like the regular process. It prompts before loading each plug-in.

Temporarily disable your virus scanner and see if it makes a difference

Likely inherited from previous installs Each version of SONAR and CbB has a UserPaths\EffectsChainArtworkFolder in their version of HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\ For example the full registry path to EffectsChainArtworkFolder for CbB is HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Core\UserPaths Probably should be global instead of one entry per DAW.