scook

CbB is a DX host so the only time DXshell would come into play is 32bit DX plug-ins. DXshell is a pretty sketchy solution involving multiple wrappers around 32bit DX plug-ins. First wrapping them in DXshell then running them in BitBridge. It does work for some but can be pretty unreliable for others. Moreover, it does not work for migrating projects as the plug-ins will not be recognized as the original 32bit plug-ins.

Yes, I know. I was not aware the label pane was exposed in the theme editor.

My themes were started a long time ago and I did not mess with the PRV color scheme. I like the original SONAR Mercury/Tungsten settings and carried them over to CbB. Never checked to see it the label pane could be changed but it appears possible.

Are you using the latest RME firmware and driver According the readme in the firmware, the Babyface version is 225. The latest driver is 1.219.

The Softube VSTs that have PC modules use the same dll as the regular VST2 plug-ins. The Boz Digital plug-ins have separate dlls for PC and VST2 formats. Yes, none of these plug-ins are free. Many of the 3rd party PC versions lack some of the features of the full VST2 versions due to the size restrictions for PC modules.

Using safe mode and a process of elimination. Too invoke safe mode hold down the SHIFT key while opening a project.

Must not have followed the link in my post

All the plug-ins installed with 64bit Cakewalk DAWS run in CbB. This post goes into more detail about how to install legacy products

After two years, Softube finally decides to release working versions of their PC modules again. In addition to the paid modules, the Saturation Knob also has a PC format. Of course, this is bundled with CbB. AFAIK, Boz Digital still includes the PC format with the +10db and Hozer XT plug-ins. The free Bark of Dog and Panipulator plug-ins were updated and the PC format was dropped in the new versions. The only PC modules Overloud wrote that are not part of CbB are the VKFX plug-ins. These were only available at the Cakewalk store. Purchasing the suite anywhere else did not include the PC format.

Using "Sort by Category" add the plug-ins to a "_favorites" category to have the plug-ins appear at the top of the layout.

Right-click between the clone track button and the track control drop down to add it back

MIDI files contain MIDI data only. Plug-in assignments are not part of the MIDI spec. Save as a Cakewalk project to retain non-MIDI data.

One at a time or all at once? Must one track at a time

Not sure what release of Producer but all the parts of the SONAR Producer installer are needed. Once all are downloaded, running the installer executable about 3 pages into the process will have options to run a full or advanced install. The advanced install option will show a pick list of components to install.

Session Drummer 3 should not need one. It, along with the BFD series and Sitala all implement the VST2.1 opcode effGetMidiKeyName. The DAW automatically detects when this is supported by a plug-in and uses the results in the label pane instead of the default keyboard. Here are images of the PRV label pane in my Tuncury Light Green theme (a Tungsten based theme with SONAR style light Drum and Notes panes) showing the names supplied by Session Drummer 3. I did nothing other than add the plug-in to the project and open the PRV. Although the theme should have no bearing on the label display. That said it would not be difficult to create an instrument file for Session Drummer 3. Instrument files are text files. Open the SI-Drum Kit instrument definition files with any text editor, change the name of the ".Note Names" section, replace the ".Note Names" mapping with the map from the Session Drummer 3 help file (or use the names provided in the images above.) and modify the ".Instrument Definition" section to use the name from ".Note Names"

If this is really the case, the best solution for getting the software is rollback then update from the current product announcement. If that is not enough, run the rollback for the current version, then the rollback for the previous version then update. This will cause the update process to download the full CbB installer. Alternately, perform a simple uninstall and re-install using the Cakewalk Installer found near the bottom of this page. This too will grab the full CbB installer. Note: the rollback links in this post assume CbB 2022.02 is installed. Any other version would use different links.

CbB does not come with any version of Session Drummer. It includes the Studio Instruments Suite. SI Drum Kit is part of the suite but is not near the plug-in Session Drummer 3 is. The Studio Instrument Suite is a separate installer. But if it were my machine, I'd consider installing Session Drummer again and all the other plug-ins bundled with SONAR. Here is a post on the process If you only want to get Session Drummer back and have X3 or older, run an advanced install and select just that one plug-in.

How and where was the plug-in installed

They are in folders wherever the plug-in dll is installed; by default, "C:\Program Files\Cakewalk\Vstplugins\Session Drummer 3\Contents\Programs".

No doubt. The main menu Process > Transpose was not part of my original reply. Here is the documentation about that feature. It only becomes active when MIDI data is selected. But I would not use it in this case. If I needed to reassign note values of some part of an e-drum kit my first choice would be the hardware itself. Then knowing the target was Superior Drummer 3, that would be my second choice. Finally, the DAW can remap notes too using the methods I linked above.

Where?

Change the note assignment in the hardware or transpose the note in the DAW using MFX Transpose or a Drum Map or change the note assignment in Superior Drummer

remove the keys under HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Core\Recently Used Plug-ins HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Core\Recently Used Synths may also need to set their permissions to read only.

Yes, MAGIX dropped CDA some time ago. While it was sold separately, it was also part of the SoundForge Pro bundle. Once they integrated the CB burning into SoundForge, CDA was discontinued. As noted above, along with the purchase of Sony Creative Software, MAGIX acquired the customer data. So, legacy products may still be installed.