scook

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.

Both the computer output and the direct signal need to be sent to the same interface output pair. Adjust the monitor volume knob to control the mix of DAW and direct signals.

The link in my post above is the current model. I found an older model that may be the one used here. Here is the description of the monitor section from page 17 of the user manual https://www.bhphotovideo.com/lit_files/374206.pdf This is how this interface implements zero latency monitoring

Do not monitor the microphone through the DAW, use the direct monitoring available on the interface. IOW, turn input echo off the recording track. The Komplete Audio 6 has a knob to the right of center that controls the mix of the interface inputs and DAW output.

Use a different driver in SoundForge and Audition.

May want to check the entries under HKEY_LOCAL_MACHINE\SOFTWARE\ASIO and HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ASIO My guess is the Cubase Generic Low Latency Driver is listed there along with the RME driver. If so, this driver is the problem.

So Cubase has never been installed on this machine? CbB does not install any audio drivers.

There have been a few threads reporting the same issue over years. In this past the user reported Cubase was installed on the machine The first message in the OP looks like the Cubase Generic Driver message. It seems strange that this machine only has CbB, SoundForge 13.0 B100 and Adobe Audition 2019 installed. I suppose Magix could have added their Generic Driver to SoundForge (although I do not recall it throwing the Generic Driver dialog) or Audio Audition may have added one to their newer software.

Some DAWs install a Generic Low Latency Driver. CbB is not one of them. The Generic Low Latency Driver supplied by Cubase has been know to cause problems, The Generic Low Latency Driver supplied by Samplitude is a rebadged ASIO4All. These generic drivers interfere with manufacturer supplied ASIO drivers. The best solution is remove or rename the generic driver and use the RME driver. Please do not cross post the same thread in multiple areas.

To avoid copying imported audio, turn Always copy imported audio files off. Keep in mind this forces CbB to use absolute file references to the imported audio clips instead of the relative file references used when audio is copied into the project. As a result projects are dependent on the imported audio directory structure.

set "Link to Original Clip(s)" along with the number of Repetitions using Paste Special

Use the Repetitions setting in Paste Special

make sure the record and playback timing masters are set up The settings depend on the audio I/O devices selected and the driver mode

My guess is you used default installs. If this is the case, the installers will tell you where the plug-ins are located. There are a couple of common locations already mentioned in the thread but VST2 plug-ins have no formal standard install path. VST3 provides a standard location but most if not all of the plug-ins you list as missing are VST2. iLok should matter as long as the plug-ins show they are activated in the iLok License Manager. Hopefully you remembers to deactivate the the plug-ins that stored their licenses on the computer as this is a new install requiring new activations. The dongle won't have that problem.

If you cannot remember where you installed the files, run the installers again and look for the default paths used by the plug-ins. Every installer should show you where the plug-ins will be installed.

The log should be much smaller. Most of the non-vst dlls should not be in the log this time. The scan path should show Now all you have to do is find where you installed your 3rd party plug-ins.

In this case, it was a bad path added to the scan path. The scanner was trying to load every dll under "C:\Program Files." This is guaranteed to cause all kinds of problems. There may be a few extra dlls in the normal VST scan path but if there are a lot, this is a good indicator the scanner is looking in folders that should not be in the scan path.

That is a log with the bad scan path. Check the PC clock if you want accurate timestamps. Delete all the files in %appdata%\Cakewalk\Logs and create a fresh log by running a VST reset from preferences using the default scan path as shown in the help

Could this be a scan log including "C:\Program Files" as part of the scan path? The scan path used is shown near the top of the log. When running a scan (or reset) using the default paths as show in the help, the log will show the following path info about 10 or so lines from the top of the log. To avoid confusion about which log you are reviewing, delete all the logs in %appdata%\Cakewalk\Logs and create a fresh log by running a VST reset using the default scan path

Protools runs on OSX and Windows. This does not explain how the ProTools stuff found its way into the VST scan path on your PC.

By default most manufacturers install all available formats for their plug-ins. This includes the Protools plug-ins, however; they are always installed in their own folders. Protools plug-ins do not get installed in the default CbB scan path. This indicates that either the installers were not used to install the plug-ins or the path was changed during install to put the Protools plug-ins in the VST scan path.