scook

Starting with 2021.06 note names in the label pane are persistent rendering the need from drum maps redundant for simple note labeling. There are several examples in the instrument definition section of this forum of instrument definition files. These files may be used to extend the note names drop down in the PRV.

This is a bad assumption. If you wish to read more on the subject see https://en.wikipedia.org/wiki/Scientific_pitch_notation

No, the GM standard note number to instrument mapping is the same everywhere. The problems start when assuming the notes displayed for pitches have only one standard. For example the GM standard for an Acoustic Bass Drum is note number 35 regardless of the pitch displayed in the DAW. Change the Base Octave for Pitches to any value you wish and the drum displayed/played for note 35 will always be an Acoustic Bass Drum. For a similar thread see

The MIDI note numbers are the same everywhere, However the pitches displayed for the numbers may vary. This is why there a Base Octave for Pitches setting in preferences.

It can be quite a task The CbB preference settings and config files are located in %appdata%\Cakewalk\Cakewalk Core HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Cakewalk\Core HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Core Also under "%appdata%\Cakewalk" are the Library and ACT data folders containing plug-in category and ACT config info. A default installation also uses "C:\Cakewalk Content" for some presets and user files. Any user presets stored using the Cakewalk plug-in management system may be exported using the Plug-in Manager (the presets are stored in the registry). Presets using the Sonitus plug-in preset manager are in ini files stored by default in "C:\Program Files\Cakewalk\Shared Plugins" The DAW has no control over where third party plug-ins store their presets.

It may help to know a little about the system. Is there an audio interface involved? If so, what make/model?

Fixed. Session Drummer uses an sfz engine like Dimension Pro, Rapture and Studio Instruments. Dropping samples onto the pads plays just one sample but a pad can play multiple samples when loaded with an sfz file.

https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Playback.03.html

Category tags are part of the VST3 specification. DX and VST2 plug-ins do not have the feature, however; Cakewalk added a way to categorize them too. Cakewalk created a database of categories for DX and VST2 plug-ins when VST3 support was added in SONAR X3. The database is %AppData%\Roaming\Cakewalk\Library\Library.db AFAIK, it has not been updated since that time. I do not recall if any or all discontinued Cakewalk plug-ins were part of the database but I doubt they were. For more info see http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Browser.08.html#1294603

No, bundled plug-ins are detailed here

Look in the instrument definition area of this forum (I put the link in your other thread)

Just like AD2, I also built an instrument definition for the default SD3

If you cannot figure out the problem, may want to post images of the following screens in preferences Audio > Devices Audio > Driver Settings Audio > Playback and Recording MIDI > Devices From what I can tell, the headphone amp does not matter to the DAW as it is using the internal PC sound chip for I/O. The amp is receiving its signal from the PC audio output which is produced by the PC sound chip. This means the WASAPI driver modes are the preferred options. If everything is configured correctly, one thing that may be missing is enabling input echo on the instrument or MIDI track. This button is to the right of record in the track header. Input echo is necessary to return the signal out of the DAW when playing the MIDI keyboard live through a soft synth.

BA keeps track of what it has installed NOT what is installed on the PC. The information is stored in HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Cakewalk\Installers

While "Always Echo Current MIDI Track" is enabled by default, I have disabled the option for years and never had a problem manually toggling "input echo" as needed.

Generic ASIO "drivers" are unnecessary. CbB supports Windows drivers natively. Try the WASAPI driver modes.

Try the Cakewalk Web Installer, at this time. unlike BA, it does not check what Add-ons have previously been installed. Copying the files from another machine may not work as it will not include the registry entries added during install.

It is not necessary to have "Always Echo Current MIDI track" enabled. It is possible to manually control input echo. In fact, some prefer not having tracks automatically input echo.

Enable input echo (the button to the right of the record button) in the instrument/MIDI track header.

Keep in mind after a minimal install of SONAR, CbB must be re-installed or the shared folders will be out of date. It may be easier to perform a simple uninstall of CbB before the minimal install of SONAR then re-install CbB.

If Always Open All Devices is enabled, try turning it off. Don't remember where it is in 8.5. It is a Global setting.

Easy to do. Running TTS-1 at 96K is a pain.

Yes, it does. It does not work at 88KHz though. To use TTS-1 with high sample rates requires setting "Light Load Mode" in every instance every time the project is loaded The setting is not stored in the project or the plug-in.

I created a second VST3 folder for the trouble makers (in my case Blue Cat's freeware) and added it to the DAW scan path. After installing SF13, I added the problem VST3s back to the default folder and the new SF13 scanner worked.

Yeah, the Dec 31 expiration is OK if one wants to flip the software but the only thing they mention is how to install.