scook

The message refers to modifications to the plug-in properties settings not plug-in presets. Each VST plug-in has a properties page like this one This page is accessed from the VST2/3 drop down in the standard header above the plug-in UI and from the plug-in manager. These settings are stored in the VST Inventory. A VST reset clears the inventory then rebuilds it by scanning all the plug-ins.

similar thread A VST Reset has nothing to do with plug-in presets.

No sound may be a different issue. Cakewalk sfz engine synths shut down when the data stream contains unexpected data. CbB has an option to ignore NRPN data, not sure about Reaper. May want to make sure the MIDI data contains note and CC data only. Often times, third party MIDI clips have setup data at the beginning of the clip that needs to be ignored or removed so that the synth does not get the data.

"My" copy of 2019.9 is 600MB... The full install includes a lot of extra files such as plug-ins, utilities, samples and other support files. The actual DAW is much smaller and that is what the Launchpad copy process works with; that is the source of the ~155MB figure.

Not sure about the impact of compatibility setting. Never used it and never had a problem with Rapture running in the current OS without compatibility mode settings including Win10. That said, I have not run a 32bit OS or 32bit Rapture in years. Never have read about a problem like this before. Something may have happened with the registry. Could try registering by running the stand alone Rapture as administrator or try a clean re-install of Rapture. Uninstall Rapture Remove the Rapture registry entries HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\rp HKEY_CURRENT_USER\Software\Cakewalk Music Software\rp Reinstall and activate. If using a Command Center era installer use the Command Center to install and activate otherwise perform a manual install and activation. To manually activate run the stand alone as administrator then enter the reg and sn when prompted. Before uninstalling, may want to save off C:\ProgramData\Cakewalk\Rapture and the multisample folder. the default location is C:\Program Files\Cakewalk\Rapture\Multisamples. Then restore these folders after reinstall. This is the easiest way to restore custom and third party programs and samples.

So we know it is the 32bit plug-in. What version and plug-in format? Might want to mention the OS too,

SONAR used the same default path for VST plug-ins. Of course SONAR had two different default paths, one for 32bit installs and the one CbB uses for 64bit installs. That said, V-Vocal is DX format. If it is installed, it does not show up in the plug-in lists though; it is a Region FX. The last version of SONAR Producer including V-Vocal was X2. V-Vocal is part of the core SONAR install and requires at least a minimal installation to get the plug-in. To run a minimal installation, select the advanced option then select the minimal installation option from the drop down. Here is what the advanced pick list look like in X2

With a softsynths it should be pretty easy to get the volume as loud as needed by adjusting the synth itself. Probably no need to mess with the MIDI data. The synth would be a good place to start to get the volume right. Most drum synths can get really loud.

Right-click in the control bar for the lock options.

You may be having an issue with Always Echo Current MIDI Track , using "All Inputs Omni" as the track input and plug-ins set to "Enable MIDI Output." All three of these are the default settings although not all plug-ins are capable of sending MIDI data. When used together, any plug-in sending MIDI data may get picked up along with the track data by the track that has focus. This is because a track with input echo enabled must have an input other than None. So, when the track gets focus, the input is changed from None to Omni as long has the track has focus. If the track has an input assignment other than None, the track track input is unchanged. To avoid this do not use "Always Echo Current MIDI Track" and turn off enable MIDI output unless the output is used in the project. "Enable MIDI Output" is found in the VST2/3 drop down above the plug-in UI.

This is an image of an audio track input drop down. A MIDI keyboard controller will never show up in this drop down as it is not an audio source The keyboard should show up in MIDI and instrument track input controls Here is an image showing the headers and default icons for an audio track (track 1) and instrument track (track 2) and a MIDI track (track 3) I see the MS-20 in the FX bin. If this is the synth version of the plug-in (which appears to be the case given the plug-in label in the FX Rack) it would be better to add the plug-in using and instrument track or an audio+MIDI track pair. It is possible to add synths directly to an audio FX Rack but in order to control the synth with MIDI data a MIDI track must be added to route the data to the synth. While this method of adding synths is supported, using one of the more modern methods is advised. Either drag and drop the synth from the plug-in browser to an empty area in the track view, use the main menu Insert > Soft Synth, right-click in an empty part the track view header area then click Insert instrument or use the Add Track menu selecting the Instrument tab (see the "So erstellen Sie Instrumentenspuren" section).

Category tags are VST3 feature. Most manufacturers provide category tags in their VST3 plug-ins although I end up overriding a few of them. When VST3 support was added to SONAR X3, Cakewalk built a database of tags for VST2 plug-ins. My guess is they do not have the staff at this time to keep the database current. I do all my initial category assignments in the Browser and use the plug-in manager to nest the folders. Hopefully nested folders will make it into the browser edit function sometime soon.

Updating in not required but the software does need to connect to the BandLab server periodically to renew its activation. Keeping the software current is a good idea though and updating renews the activation too. That said, I like to keep at least the version I am currently running available after updating. I wrote a tool called Cakewalk Launchpad and one of its functions is the ability to switch between versions CbB. Before updating CbB, I make a copy of the existing install (keyboard shortcut K). After the update, I can switch between versions on demand. Currently a version of CbB is ~155MB so, keeping a couple of version online does not take much space.

You have posted this same message on at least 5 other threads in a very short amount of time. Please do not do this again.

contact support@cakewalk.com

Cakewalk overwrites the templates in the default project template folder. To avoid this either use different template names or better still use a custom location for project templates. The installers do not write into a custom location. The template folder is specified in preferences.

http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Troubleshooting.33.html

Nice seasonal post

Groove Clips have rounded edges like the upper clip in this image. The lower clip is a regular wav

The company called BandLab makes 2 DAWs. One is called BandLab, it is an app that runs in the Chrome web browser. The other is a Windows program called Cakewalk by BandLab. The main page for this DAW is https://www.bandlab.com/products/cakewalk I believe this is the page referred to in the OP. The instruments mentioned on this page are for the DAW called BandLab NOT Cakewalk by BandLab.

The Source Category drop down in the Export Audio dialog

the current build is 70

CbB works just like SONAR in this regard. If there are no previous installations of a related product such as SONAR, the CbB installer provides the ability to initialize the install paths. If a previous installation is detected, this option is not provided and the existing registry entries are used. In fact, certain parts of SONAR and CbB must share certain paths because there is only one location in the registry for items such as "Cakewalk Content", the default Project Directory and all the "Shared" folders.

This is incorrect. There are two basic types of tracks Audio MIDI An instrument track is a hybrid track made up from one MIDI track and one audio track - displaying the input controls of its underlying MIDI track and the output controls of its audio track. Instrument tracks do not expose all of the features found in separate MIDI and audio tracks. To gain access to these features the instrument track must be split to reveal the underlying MIDI and audio tracks. It is also possible to create an instrument track from the MIDI and audio tracks that point to a soft synth as long as there is only one MIDI track and one audio track pointing the synth. While additional audio and MIDI tracks may point to a plug-in being served by an instrument track; it is better to avoid using instrument tracks when using more than one audio+MIDI pair. So, the basic routing for a soft synth using a single MIDI stream and single audio output is either: A MIDI track and an audio track or An instrument track

It may not be as basic as it seems. BA is managed and maintained by a different group in Singapore. Can't offer any help to the OP except to suggest contacting support@bandlab.com