scook

email support@cakewalk.com it goes to the same place

The errors are coming from the plug-ins. CbB has no idea what files are used by a plug-in or where they may be located. In addition to a corrupted or bad install, one thing that may affect the ability of a plug-in to find its file compression by the OS. Check the disk to make sure the folders and files are not compressed.

Could be an unexpected "feature" of the Beta or the Beta has the same serious bug as 7.2.0 so they withdrew it by updating everyone to 7.2.1. Only the devs know for sure. Not sure who is running the BA Beta. I guess this would be something to ask support@BandLab.com. Beta programs generally have some type of communication with the testers, otherwise; why have a Beta program.

Either remove the "empty space" or make a time-based selection for export

Select the start and end times to export or place a MIDI event, such as a note with 0 velocity, or automation node where the song should end

current version is 7.2.1

Did you read this

Plug-ins running outside of the DAW effectively look and act like hardware synths. Not sure if a USB driver is what you need or just some way to send MIDI and audio between the two OSes. Maybe a something like rtpMIDI or some other virtual MIDI connection can handle the MIDI side.

It's a possibility Take a look at

Could be a mix of the direct signal from the interface mixed with the return signal of the tracks being recorded (these tracks have input echo enabled). This will sound like a slap back echo. The delay will vary depending on the size of the driver buffers and plug-in delay compensation. To avoid the echo, monitor the recording tracks directly from the interface or from the DAW but not both.

Don't use many sampled based synths. No Spitfire stuff installed. Here is CbB 2021.04 build 147 running three instances of VST2 AAS Lounge Lizard v4.3.1 (I have not updated AAS in a while) on Win10 20H2 build 19042.964

All 4 files MUST have the same version number. Reboot and re-run the build 147 update.

Check the build in the About screen. Build 144, the production build has the timing problem. AFAIK, the update checker does not know about any build newer than build 144. It only knows about production releases. The link above has a post from Noel with a temporary build 147 to address most of the timing issues with a final production build pending as noted by @David Baay

A clue to BA's main duties could be the name...BandLab Assistant. This tool, written by a dev team in Singapore, was originally designed to support BandLab, the web-based DAW. After BandLab acquired Cakewalk IP, BA was extended to handle CbB install, activation and update. With in-app updates and re-activation added to CbB, reliance on BA is not as critical for CbB users as it once was. BA does offer a loop library and most recently a front-end for BandLab's mastering service.

It has not changed in a very long time. There is a knowledge base article on the old web site about adding third party editors I wrote a tool for this purpose to avoid having users directly edit the registry and help eliminate some of the common errors users made following the old kb article. It is part of CbBTools available here. There is a thread about this

Is it? http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Introduction.30.html#1538285

Make sure you are not using CbB 2021.04 build 144 too

It does sound like a bad install. May want to perform a clean install. The instructions are here https://help.cakewalk.com/hc/en-us/articles/360034066393-Clean-Install-Cakewalk-by-BandLab If you elect to perform a clean install be aware that step 8 will delete all 3rd party plug-ins under the "C:\Program Files\Cakewalk" folder. If you have any 3rd party plug-ins installed there (usually they would be in "C:\Program Files\Cakewalk\Vstplugins") consider save the folder to somewhere else before proceeding with step 8 and restore the folder(s) after running the CbB installer. After cleaning the previous installs off the PC, here is a post about building a new DAW using SONAR and CbB. BTW, make sure to install Rapture Session after completely installing Cakewalk Sound Center and any expansion packs (and any versions of Dimension, Rapture and their expansion packs too). This will allow Rapture Session to copy the legacy presets into its preset browser. Rapture Session is the 64bit replacement for Cakewalk Sound Center.

Melda Productions installers should be in Apps & Features in Windows Settings. Click on the installer on that page to get an uninstall option. After running the uninstall. the next time CbB scans for plug-ins they will be removed, All the Melda Production plug-in share some files, it may be necessary to re-run the MFreeFXBundle installer after uninstall other Melda plug-ins. Can't say for sure, I have never needed to uninstall a Melda plug-in.

Really should review the changes noted in Running a theme with images that are not the correct size messes with the ability to use the function associated with the image. This is why it is important to either use a theme supplied with CbB, use a theme that is actively maintained or learn how to use the theme editor to properly maintain a theme. This part of the forum is dedicated for questions about the theme editor and current user themes.

The best solution I have found for drum maps in 2021.04 (the subject of this thread) is a custom location populated with the maps I use.

Unless, great care has been exercised when modifying SONAR/CbB, getting all the presets and customizations from one machine to another can be very challenging. Even when careful, the process is a chore. I have never wiped and reinstall a machine but I have moved significantly customized versions of SONAR/CbB from one machine to another. In my case, it would be very difficult to migrate to a new machine without the benefit of access to the previous install. Here are some things to consider: There is an export option for plug-ins preset saved in the Cakewalk Preset Manager in the Plug-in Manager. The exports are per-plug-in. There is an export option for keyboard shortcuts in preferences. Things like custom templates, FX chains, CAL scripts, drum maps are saved in folders by default under the "Cakewalk Content" folder or the user folder(s) in "%appdata%\Cakewalk". Of course, these may have custom locations. This is one reason to create and use custom locations. It make migration easier. If Dimension Pro and Rapture are customized the programs are under "C:\ProgramData\Cakewalk" and the samples default locations are "C:\Program Files\Cakewalk\Dimension Pro\Multisamples" and "C:\Program Files\Cakewalk\Rapture\MultiSamples" By default, Session Drummer 3 stores everything with the plug-in. Of course, there are other sample-based plug-ins bundled with SONAR. None of this covers customizations and presets to 3rd party plug-ins. When it comes to installing the DAWs, here is some info

Rapture was added to SONAR Producer X1. Unlike DP, Rapture was small enough to be part of the SONAR Producer installer. An Advanced install of any version of SONAR Producer X1 through X3 will show Rapture as an option. With SONAR Platinum, Rapture has its own Cakewalk Commander Center aware installer. The conventional wisdom is run a full install of the most recent version of 64bit SONAR you own. Apply all the updates then install CbB. For more detailed info see

Here is a little history behind the "hidden" plug-ins. The plug-ins that show up hidden in the plug-in manager are hidden by design. Hiding plug-ins has been a design element at least since V-Vocal was added with SONAR 5. The Drum Replacer is hidden for the same reason as V-Vocal. While both use standard plug-in APIs (DX for V-Vocal and VST3 for Drum Replacer) neither are regular plug-ins and cannot be used in the FX Rack or PC. They are exclusively Region FX. The hidden VST2s started to appear in Music Creator 7 with the introduction of Style Dials. These VST2 dlls are the engines under the Style Dial UIs (specially compiled FX chains). Later, Style Dials were added to SONAR and are part of CbB. My guess is, it was easier to leave the plug-ins mostly intact and use them as-is in the Style Dials rather cripple the plug-ins. That said, the "hidden" VST2 plug-ins are older than the last official VST2 plug-ins included with SONAR. While there is nothing stopping one from unhiding and using them, the practice is not supported. Maybe some day BandLab will officially release these plug-ins like they have done with the PC2A T-Type Leveling Amplifier ProChannel module and Classic Creative Suite audio effects. Until that time, there are plenty of great plug-ins in the Favorite Freeware FX Thread

DP needs to write to a protected area of the registry during activation. The standalone synth or the DAW must be run as administrator in order to activate DP. Once activated, there is no need to run as administrator.