scook

Here is the audio hardware setup guide https://www.cakewalk.com/Support/Knowledge-Base/Audio-Hardware-Setup-Guide use SONAR Platinum as the product. If running Win10 and the setup guide recommends MME try the WASAPI settings first.

It's pretty easy to get unintended consequences when heavily modifying Mercury or Tungsten. There are quite a few strange dependencies. This is why I chose to work around the edges of the two Cakewalk supplied themes first restoring button relief and an alternative to orange in Tungsten and providing a alternative to blue in Mercury. I avoided large scale tweaking of the the Cakewalk supplied color schemes to insure things like text fields work like Mercury and Tungsten. It will take a little detective work to find which mod changed the text field. The theme editor provides a way to narrow down the search a bit by filtering on modified colors. Comparing the modified elements of the user theme to Mercury/Tungsten and tweaking the modified colors to something that will stand out for the possible candidates are the only ways I know to detect the areas of the UI affected by a color setting.

Already built into the OS Windows+Plus very useful for failing eyes

Locking this thread because the OP created a new thread about the same thing

Removing paths before running a scan causes the plug-ins that are no longer in the scan path to be removed from the registry. The paths will be re-scanned when they are added back. The only way I know to avoid the re-scan requires manipulating the registry.

https://www.google.com/search?q=toast+messages&ie=utf-8&oe=utf-8

The popup messages in the lower right of the screen used for project load, vst scan and pending update status.

To create an automation envelope without using the parameter drop down, arm the track for automation (click the W button) start the transport and tweak the control on the plug-in UI.

There are two ways CbB sets the sample rate for a project. If the project does not contain any audio clips, the sample rate is read from the Default Settings for New Projects - Sample Rate in preferences If the project contains audio clips, the sample rate is read from one of the audio clip headers. CbB does not set the audio I/O buffer when running in ASIO mode. There is no way for CbB to do it. This is set by the ASIO control software supplied by the interface manufacturer.

Yep. that menu shows the setting for the synth that has focus in the synth rack. By default, any synth capable of MIDI pass through or generating MIDI data has this option enabled. That and the default "All Inputs" > "MIDI Omni" can create some interesting data paths.

Convert MIDI Controllers to Envelopes but you may want to record as automation instead of CC data.

thanks

If there is more than one Instrument/MIDI track and Always Echo Current MIDI Track is enabled and one or more of the plug-ins has Enable MIDI Output activated like this image shows can lead to MIDI "bleed" The best solution is turn off "Always Echo Current MIDI Track" and only turn on "Enable MIDI Output" when needed. This along with avoiding setting Instrument/MIDI track inputs to "All Inputs" > :MIDI Omni" should eliminate unexpected MIDI data showing up on tracks.

2GB of RAM may be a problem. It has been some time since I had access to a 32bit machine. Never used DP much and don't have many of the larger/newer DP libraries. I know that there are a couple of Rapture Pro programs that are too large for 32bit machines. May want to check the libraries you plan to use on your existing hardware and see how much memory they use. DP does not stream samples. All samples must be loaded into memory.

Have not seen this in some time. Did a search on the old forum and found this thread. It is a problem with a Yamaha Steinberg USB driver. I thought they fixed it with an update.

Works here. Make sure the plug-in layout is set to "Sort by Category"

Custom note names used in the PRV Notes Pane are not read from drum map presets. They are read from master.ins. It would be nice to have per-track custom note names persist across sessions.

The variable and default plug-in name change happened with SONAR X2a. Glad you found the info useful.

see LinkPFSendMute set in preferences

Of the two synths, I never really used DP. One of the UI differences between DP and Rapture is Rapture supports direct value entry. Double-click to edit a value.

The reason they don't work at all is because there was only one copy of SI installed to begin with. CbB simply overwrote the SONAR install. Running the SONAR SI uninstall removed the only copy on the PC. Any plug-in bundled with CbB overwrites older SONAR versions.

The default plug-in names where changed after X1. X1 used the dll file name, modern versions by default use a name provided by the VST. This behavior may be changed. See my reply here

The default plug-in names are based on the VSTPlugInNameFormat setting. Read about the variable and its options here. Set the variable here. Note: initially this screen is empty. Add a variable and its value to initialize the file. Custom plug-in names may be set in the plug-in browser. The documentation is in the middle of this page.

Assuming 64bit SONAR Platinum's SI installation and default install paths for both SONAR and CbB, Studio Instruments are overwritten when running the CbB SI Add-on installer. Are any SI instruments available in CbB now?

Please edit the OP and add [Solved] to the subject line.