scook

Great A download link in the plug-in would be a nice addition. That, a version check button (manual check and update are preferred) and when the update cycle slows down update notification by email would be fantastic good job

I don't have the device so this may not help at all... The labels shown in the drop down would be up to the plug-in and not the DAW. The DAW does not know what purpose the input serves. Here is an example of FabFilter Pro-C sidechain input in CbB, the plug-in in instantiated on the TTS-1 track 2, the image shows the track 1 menu w/ Pro-c in the sends "Input 2" is likely the sidechain input in Console 1 too IOW send drop down labels are constructed by appending the plug-in name with secondary plug-in input pair names supplied by the plug-in (there could be multiple input pairs which would result in multiple send selections) and track name

Establish a budget Demo the plug-ins Buy what you like within your budget Enjoy Repeat

Mercury is a theme in name only. This "theme" is comprised of the resource files used by the DAW. Theme files store differences from these resource files. Tungsten is one of these theme files with a special extension and location. Other than these 2 things it is the same as user created themes. Both Mercury and Tungsten may be updated with the DAW. When the DAW starts up, it attempts to validate the theme. If this fails for factory supplied themes, I have doubts about the installation. A simple CbB uninstall/reinstall would be on my short list of remedies.

The Village two prisoner references, one month

IDK, I've been a little of an SSL plug-in completist and believe there are a few plug-ins that have yet to hit ~80% off territory. They are 4K B Meter SubGen Blitzer DeEss could live without them but would like the whole set

Going is not near the problem staying is. Fortunately, the limestone is naturally assisting drainage the Karst way.

fixed

The Workspace setting is often the reason documented features seem missing Either change to a workspace that has the feature, create a new workspace with the feature or set workspaces to None.

The current Cakewalk support may be able to help email support@cakewalk.com legacy support page https://help.cakewalk.com/hc/en-us/categories/360001718094-Legacy-Products

How to add time rulers from http://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Playback.06.html

Jim has been offering NVIDIA cards in PCs for years. Currently using a ProStudio I purchased a few years ago with a NVIDIA GeForce GTX 1660 Ti running CbB on Win10 without issues.

The installer should be in the old user accounts. While CCC is the recommended way to install and activate but the manual process is still an option.

reported

The VST scanner recursively traverses paths defined in CbB attempting to load every dll file it encounters, except in the spec'd VST3 folders where only files with a vst3 extension are loaded. Chances are the scan path contains folders it shouldn't. Post a image of the VST Setting screen (link above) if you need help setting up the scan path. This preference screen also provides a "Generate Scan Log" option which may help. Enable "Scan in Sandbox" if it is not already. Always run scans from preferences.

The CCC should be OK Assuming you are running version 1.1.8.1 and have a valid login for the legacy site. I believe the CCC was updated after the recent Sonar/Next announcement. The current version of CCC is available here Password reset is performed on request by support@cakewalk.com

Ever since the introduction of Preferences > File > VST Settings decades ago in SONAR and continuing through CbB, the recommendation from the developers has been to perform all VST scanning operations from Preferences and not from the plug-in manager. The ability to scan from the plug-in manager is provided for backward compatibility and does not take advantage of some of the advanced features offered in Preferences.

Look again...you know one cannot select different ASIO drivers for input and output, right? It is a curious choice of names, but I suspect it has something to do with a USB connected amp or similar device.

There is one condition I know of that will cause a plug-in to not be scanned. That is if the plug-in is a VST2 dll and is in the spec'ed VST3 path. Other than that, if the plug-in is the scan path, the VST scanner will attempt to load the plug-in at least once and register the result in the VST Inventory. Unless we have the log from the initial time these plug-ins were scanned, chances are we won't know what happened. Assuming the "Skipping VST2 plug-in in the VST3 folder" is not the issue and the plug-ins failed to scan the first time, they may be marked bad and are in the excluded list. If this is the case, to force scanning of excluded plug-ins in CbB Preferences File > VST Settings set Scan to Manual Scan Enable Rescan Failed Plugins, Scan in Scanbox and Generate Scan Log Click the Scan button Disable the Rescan Failed Plug-ins option (the two rescan options should normally be disabled reset the scan frequency as desired Look for the plug-ins, if they are not listed review the log and check the entries for the plug-ins. The ultimate hammer is VST Reset. Running a VST Reset clears the VST Inventory in the registry and completely rebuilds it. Make sure when running a VST Reset to enable the sandbox and logging options. These options are only available in Preferences, they are not available in the plug-in manager.

sounds like a plan

That's a good starting point. Dual drives were the rule before SSDs but a single SSD is fine for most users. My guess leans toward config and this may be worth checking out

Probably not, Reatek is not the only manufacturer of audio gear NOT designed for DAW use. Some companies that sell products intended for DAWs have devices that just don't seem to be up to the task because of poor driver support. Hardware/drivers may not be an issue. It may be something else entirely. Of course, if one was really looking for answers they would be more forthcoming with information. Describing symptoms without describing the patient is bad medicine.

Chances are you've already overthought this. Often, excluding plug-ins is the best solution. They are effectively unavailable for new projects while still loading in existing projects and templates. Going any further runs the risk of plug-ins missing from existing projects. That said.... Here is a post about a tool to display all VST2/3 plug-ins found by Sonar Xn Producer/Platinum/CbB. It may be helpful. If the VST2/3 plug-in binary is not in the scan path, the next scan removes it's information from the DAW's VST Inventory in the registry. Whether this is done by removing the scan path from the DAW configuration, moving the plug-in files from the scan path or uninstall the plug-in is up to the user. The last option is the most complete as the plug-in is no longer resident on the machine. DX format plug-ins are host bitness specific. 32bit DX plug-in are not even seen by 64bit DX hosts like CbB. Unlike VST plug-ins, DX plug-ins are registered during installation using the Windows utility regsvr32.exe and do not need to be scanned by the DAW to be available. The same regsvr32.exe is used to unregister plug-ins. This is a manual process and may be performed at the command line. The command needs to be run as administrator. Like all Windows command line utilities /? brings up its help. But I feel like this is already TMI about the handful of DX plug-ins on your PC.

Reads like minimal hardware, a lot FXs (or really CPU intensive ones or both), very poor configuration or a combination of all three. There are limits to what a PC can do using the internal sound chip. CPU, SSDs and RAM are not going to compensate for Realtek. If this is a hardware limitation getting the project to all audio tracks by freezing and/or bounce+archive may be an important part of the workflow.

They already do or the DAW could not tell one instance from another In the image above the unique names are insured by a counter appended to the name of the plug-in Scaler 2-1 Scaler 2-2 Scaler 2-3 By default, this is also used for the track name. Change the name of the plug-in instance and all the I/O referencing that plug-in will update accordingly, Try modifying the names in the synth rack. I believe the instance counter is retained and displayed in menus regardless of the names used.