scook

That's right. ASIO is restricted to one driver at a time. In order to insure only one ASIO driver is in use, the DAW disables all other ASIO drivers in preferences while any selection exists.

Remove and forget about generic ASIO drivers regardless of where they come from. All a generic driver is doing is adding another layer of software between the actual audio driver (MME, WGM or WASAPI) and the DAW causing the DAW to believe it is communicating with an ASIO driver. This is completely unnecessary with CbB. WRT, ASIO drivers being disabled in CbB preferences. Only one ASIO driver may be used at a time. To change ASIO drivers, deselect both input and output before making a new selection.

Projects get their sample rate one of two ways: if the project contains no audio clips, the sample rate is read from the Sampling Rate entry in Preferences > Audio > Driver Settings If the project contains audio, the sample rate is read from one of the audio clip headers. Here are the instructions on how to change the sample rate of a project containing audio clips.

Re-run the license manager to renew the activation.

If CbB is installed, after installing an older Cakewalk DAW, rollback (or perform a simple uninstall) and re-install CbB. This makes sure the latest shared files are installed. It's not that difficult.

A large portion of that are the optional demo/tutorial data.

create a hang dump and send it to support

To avoid the usual mistakes made by editing the registry directly, try the free Tools Editor available in this thread

Keyboard shortcut "J" toggles scrubbing

With the RXP Groover Browser open press the F5 key to rebuild the browser tree.

Allow importing of WAV File Cue Markers

All settings under Preferences > Project are stored in project and project template files. Create new or modify existing project templates as desired and use them for new projects.

Something like the navigator pane?

The image in the OP is unusual. Tracks 7 through 10 are synth tracks with their inputs set to at least one instance of Session Drummer and these tracks also contain audio loops. Normally, synth tracks are empty or contain the frozen audio output from their associated synth. They would not contain audio data from a source other than the synth.

Instead of importing the song make sure no MIDI output device is selected in Preference > MIDI > Devices use File > Open to open the MIDI file This will automatically add and setup TTS-1 to play the file. Compare how this project looks to the one in the image to see how to the DAW added the TTS-1 synth, and audio track and routed the MIDI tracks to the TTS-1.

The message indicates you are starting CbB with the SHIFT key held down invoking partial personalization. For safe-mode hold down the SHIFT key while OPENing a project. IOW... SHIFT while starting CbB = partial personalization SHIFT while opening a project = safe-mode. Alternately, physically moving the offending VST3 out of the scan path should allow the projects to open with a missing plug-in message.

Wav files are binary files and have the same recovery challenges as other binary files. Whenever needing to post a large file (or any file really) consider uploading the file to a hosting service such as OnceDrive, GoogleDrive, DropBox.... and add a link to the file in a post here.

It is possible to both remove old plug-ins from view (and possible accidental use) and still have them available when an old project needs them....the Plug-in Exclude List. The Plug-in Exclude List is maintained by the Plug-in Manager. From the Plug-in Manager help Alternately, moving plug-ins out of the scan path or uninstalling work too but as noted in the OP, the plug-ins will not be available when loading old projects. By default, the VST scanner only scans a plug-in one time. Of course, it has to walk the scan path to find unscanned plug-ins. Plug-ins that load in a shell such as Waves must be scanned every time because this is the only way to know what is available using the shell.

One could map a CC to the filter cutoff or just use plug-in automation. Because of the way the plug-in resets the filter, it might be a good idea to start the project at measure 2 or later so that the automation can set the filter before the note data starts to stream to the plug-in. Here is a video showing how to automate the Filter 1 cutoff. In this case. I manually assigned and drew the automation. Another way (and probably the easiest) to assign and draw automation is Arm the plug-in for automation by clicking the W on the right in the standard header above the plug-in UI Start the transport Manipulate the filter cutoff in the plug-in UI Turn off Write automation by clicking the W again. IOW, your original video is just missing arming and disarming Write automation.

This is covered in the help. The steps for adding a new item like RX10 is noted below the image I posted previously The Edit drop down contains existing entries to edit. To add new entries, skip the Edit drop down and fill out and Submit at least the "Required Entries" section.

Yeah, another old school approach. These days, I avoid the Plug-In Manager for most things plug-in related except for layout maintenance. Exclude list maintenance is one of the few other functions unique to the Plug-in Manager and as noted can be used to force a rescan. It has also been the source of threads on the forum when user get to aggressive enabling plug-ins.

It is part of the MTotalFXBundle and MCompleteBundle. No additional purchase necessary.

Both VST2 and VST3 scan and run OK here. The plug-in installer only puts the "Shadow Hills Mastering Compressor.dll" in the designated VST2 path and "Shadow Hills Mastering Compressor.vst3" in the designated VST3 path. All the other support files go elsewhere. The problem is not plug-in name length related. The VST plug-in names used depend on the VSTPlugInNameFormat settng in Cakewalk.ini. By default, CbB uses a label found in the plug-in dll. For some reason, the last "r" is missing on the label in the Shadow Hills Mastering Compressor VST2 dll. If might be a good idea to post the full fully qualified names for the "Shadow Hills Mastering Compressor" VST2 and VST3 plug-is and the scan path as shown in preferences. If the VST3 is scanned as not a plug-in, then something happened when the scanner tried to load the vst3 file that causing the scanner to fail the plug-in.. It could be a bad vst3 file, an activation problem, band/missing support dll or some system failure. There are several ways to try and correct the problem. A VST reset from Preferences > File > VST Settings with the two log file options mentioned above enabled is the easiest although it can be very time consuming if one has a lot of plug-ins. In this case, a more targeted approach might be a good idea. To force a scan of the VST3 only: move "Shadow Hills Mastering Compressor.vst3" out of the scan path, run a VST scan from Preference > File > VST Settings with both log options enabled, after the scan search the scan log for "Shadow Hills". The only references should be the VST2 and possibly removing the VST3, put "Shadow Hills Mastering Compressor.vst3" back into the VST3 folder, run another VST scan from Preference > File > VST Settings with both log options enabled. This should pick up the "Shadow Hills Mastering Compressor.vst3", If not there should be a log entry explaining the exclusion. If this fails, uninstall the "Shadow Hills Mastering Compressor" confirming the VST3 is gone, re-install and re-run the scan with the log options enabled.

I am surprised notes outside the documented range work at all. IIRC, the kit is mostly GM with some notes below 35 controlling the MIDI loop transport. The note mapping is in the Session Drummer 3 help installed with the plug-in. Hit the F1 key to bring up the help when the plug-in UI has focus.