scook

It is hard to offer suggestions without details. It was not clear from the OP until the image of the crash dialog was posted that the crash message was coming from the plug-in. I posted a link to a primer posted by @Noel Borthwick on how to report crashes that happen in CbB. A new variable called ExceptionHandlingSeverity was added to Cakewalk.ini in CbB 2021.04 to better report badly behaving plug-ins. Read about the variable here and in the 2021.04 release notes. Preferences > File > Initialization File may be used to maintain this variable.

I found one in the CbB Preset Manager It looks like this

In addition to color, different plug-in formats use different icons. The icon like the color is theme dependent. The "2 plugs that are not plugged together" show the default VST3 icon. The other three are show the default VST2 icon.

The error message is coming from the plug-in NOT the DAW. The dump is generated by the plug-in. Send the dump to Toontrack support. As mentioned in one of your other threads, the colors used in the CbB plug-in browser indicate the plug-in format only. The colors used are theme dependent. The VST3 plug-ins are not "greyed out". The browser does not show "disabled" plug-ins.

Really don't need a thread for each VST3 plug-in. See if the crash generates a minidump, Here is more info on how to report a crash

This is your third thread created on this subject, Please do not create another.

Yes I have quite a few VST3 synths installed and they all work. I just updated Superior Drummer 3 after reading this thread to grab their new VST3 plug-in. It runs just fine. Could you be more specific? Do they crash the DAW? Do they display an error message when loading? Do they load and not play?

As John noted above the menu colors indicate the plug-in format. The colors used depend on the theme. WRT, VST3 synths not working on your PC best to keep that discussion in your other thread.

Notes Browser

Track, bus and time-based selections may be made in the track view or in the export dialog Define the export one time and save it as a task in the export dialog

yep

Prior to 2021.01, having input echo set to None and Always Echo Current MIDI Track and the plug-ins with "Enable MIDI Output" selected was even more of a problem. Starting with 2021.01, if there are any plug-ins with "Enable MIDI Output" selected instead in the project of automatically switching MIDI and instrument tracks to "All Inputs > Omni" the input "All External Inputs > MIDI Omni" is selected. Input echo on its own does not cause the problem, it depends on the input setting. Input echo simply causes whatever data is at the track input to be played as if it were a MIDI clip in the track.

When MIDI data shows up unexpectedly on a track it is often due to the track having its input set to "All Inputs > Omni" and "Enable MIDI Output" selected on a plug-in driven by another track. By default, synth plug-ins capable of sending MIDI data have "Enable MIDI Output" selected. The "Enable MIDI Output" option is found in the VST2/3 drop down in the plug-in standard header and in the Insert Soft Synth Options dialog.

In CbB, projects end where there is no more data to the right on the timeline. This could be considerably different than what users consider the project end. Clip envelopes cannot go outside clip boundaries. Track envelopes may have nodes very far down the timeline. The best way to ensure the run length of an export is use a time-based selection like I mention here

I am not sure if the UMC22 uses a real ASIO driver or a re-badged version of ASIO4ALL. Generic drivers like ASIO4ALL can interfere with factory supplied ASIO drivers.

If the track control drop down shows [Worspace] may want to review the Workspace setting. When a workspace is configured to load the Track Control Manger, overriding this with track control drop down is not persistent. Better to select a workspace that does not load the Track Control Manager, create a new workspace or set workspaces to None. If the workspace is not loading the Track Control Manager, the track control drop down setting does persist, however; is easy to accidently change using its keyboard shortcuts SHIFT+left/right arrow.

If the is no longer available or will not be used any more, uninstall the software. If the option still appears in CbB remove the entry for the driver from HKEY_LOCAL_MACHINE\SOFTWARE\ASIO in the registry.

Alternate note names for plug-ins have always been per-track, however; prior to 2021.06 they had to be set every time the track was opened in the PRV. This was how the feature was originally designed. For 2021.06, the feature was modified to store the setting in the project in order for note names to persist across sessions. There are a few and this is one of them, although there is no requirement to define all 128 notes in an instrument definition there is no way to suppress displaying all the notes. That said, the drum map editor and file layout could be improved quite a bit. The method to make bulk changes to values in the Drum Map Manager is a little clunky.

This is not an issue with uninstalling CbB. The OP in the link above discusses the 64bit registry entry for VST plug-ins. This entry is not created by CbB installers, however; users are given the opportunity to specify where to install VST2 plug-ins during the initial install of CbB. This preference is stored in HKEY_LOCAL_MACHINE\SOFTWARE\VST, a path read by many programs and installers. It would be very unusual for uninstallers to undo or remove shared registry entries. Moreover, unlike VST3, there is no standard for VST2 install paths. Not all manufacturers use the VST registry entry as the default install path. Regardless of this setting, it is common to provide a way to specify where to install VST2 plug-ins. That said, the subject of this thread is correct CbB does not remove registry entries or files users may modify using a simple uninstall process just like most Windows uninstall processes. Support has published a clean install procedure which does detail how to completely remove CbB including registry entries and support files, but it is silent on the VST install path because this is shared by other programs and installers and is set based on user preferences.

This is documented in the "Misc enhancement" section of the release notes for 2021.06. No changes were made to the menus. To use Individual instrument definition files, import them into the master.ins (see the link provided above). Of course, one may directly edit the ".Note Names" and ".Instrument Definition" sections too, but most often individual ins files are created to share definitions.

Persistent per-track note names using instrument definitions was added in 2021.06. Have not used a drum map for note naming since this feature was added. I created several VST drum synth instrument definitions and posted about them in the instrument definitions area on this forum. Once created they are easily imported into the master instrument definition file used by CbB. Instrument definition files are plain text files.

Is a project open when viewing key bindings? If not, the bindings are not displayed. Bear in mind, key bindings may be affected by the workspace setting too.

The last version of TS-64 is 17.5.2.14. All the plug-ins installed with 64bit SONAR X2 should work in CbB.

https://support.microsoft.com/en-us/windows/add-an-exclusion-to-windows-security-811816c0-4dfd-af4a-47e4-c301afe13b26#:~:text=Go to Start > Settings > Update,%2C file types%2C or process.