scook

The plug-in is not a synth, it is an effect plug-in so it will be in the effect lists. It does not make sound on its own, it is a guitar ampsim/effects package. Make sure to use one of the factory supplied "Sort By" lists or add the plug-in to the custom layout. If using "Sort By Category" the plug-in may be in the Uncategorized folder.

Or let Melda install the VST2 plug-ins into paths not scanned by CbB. From there it is easy to either leave them on disk or delete the unwanted files. This is how I handle manufacturers who supply decent VST3 plug-ins but still want the VST2 plug-ins for hosts that either do not support VST3 or are 32bit.

All the plug-ins bundled with CbB are 64bit. When it comes to DX plug-ins, they are host bitness specific. IOW, 32bit DX plug-ins only run in a 32bit DAW, 64bit DX plug-ins only run in a 64bit DAW.

I do not have the plug-in and have not created an account to download the trial. I found this in their FAQ My guess is since the iLok Manager was not running when the scanner tried to load the plug-in, it was placed in the excluded list. Once excluded a plug-in is unavailable. To complete the scan for this plug-in, open preferences, temporarily set the scanner to manual scan, enable Rescan Failed Plugins and run a scan. Once the scan is complete uncheck Rescan Failed Plugins and set the scan option back to your preferred setting.

Authoritarian? No one is stopping anyone from doing anything, no one is forcing anyone to do anything. If you feel abused please report the post.

There is a 64bit version of Limiter 6

There is nothing to move. There are some theme editor feature request threads in the Feedback Loop area. If you have a new feature request, create a new thread in Feedback Loop. Creating a single thread containing all the feature requests related to the theme editor is not how this forum works.

Is the iLok License Manager installed and running?

This is one of the earlier reports of the "Slide Over Old to Make Room" bug. The videos posted by the OP are still available. Not sure when the problem first appeared but the bug has been on file some time. My guess is the option worked before the X-series but has been mangling projects for years for those who continue to use the option. Fortunately we now have Ripple Edit.

The tests may be performed on the exported audio files.

Feature requests should be posted in Feedback Loop

If Drag and Drop - What to do with existing material is set to "Slide Over Old to Make Room" this is the cause of the problem. Do not use this option...ever. Set this to one of the other options and use Ripple Edit when "slide over" is needed.

Perform a full install of 64bit Platinum if it is not already installed. Cakewalk Command Center is the easiest way to install and activate Platinum. Install AD2 using the XLN Installer. Install Melodyne from your Celemony account Download BandLab Assistant and install CbB. The instructions are here At this point all of the plug-ins in Platinum will be available in CbB.

no

This is one way but the safest is a custom project template folder location. The installers write to the default location, a custom project template folder is not touched by the installer.

Of course, Cakewalk and its VST scanner has nothing to do with Studio One and vice versa XLN issues with Windows updates are well known and covered in the XLN support link provided above. Like @abacab, I experienced no plug-in issues updating to 1809 in March.

maybe this is the issue http://forum.cakewalk.com/FindPost/3195458

So this is not true

Yes and they still show UAD plug-ins in two different paths

If this is the case, then why did the images in this post show 2 different paths containing UAD plug-ins?

Yeah, I failed to link the XLN support page about authorization https://www.xlnaudio.com/support/my-product-is-suddenly-not-authorized-wrong-computer-id-or-this-instrument-is-in-trial-mode. This is a common problem for XLN software. There have been cases in the past when plug-ins do not scan properly and instruments show up as effects. In this case, I would not try to force the plug-ins to synths because there a re likely other problems with the registry entries. That is why I suggested running a reset.

Very unusual for the VST registry entries to change without some user action. A windows update would not alter this part of the registry. May want to run a VST reset from preferences. A VST reset clears the VST Inventory in the registry and re-scans all the plug-ins. Also may be a good time to make sure the re-scan options on the same page are turned off.

For AD2 the templates already exist https://www.cakewalk.com/Support/Knowledge-Base/2007013364/Setting-up-a-Drum-Map-for-Addictive-Drums-2-in-SONAR but it is good practice to perform the exercise without the benefit of pre-made templates.

Add a MIDI track and manually assign the output to the synth then re-save the template

No need to search, just click enter after pasting the string.