scook

"Generate Scan Log" was added to CbB 2018.06 If you are running an older version of CbB, it may be worth updating. Maybe you are looking in the wrong place. Here is the documentation for the 2018.06 scan enhancements Always run scans from preferences NOT the plug-in manager. The plug-in manager retains a scan page for backward compatibility but it does not support new features like logging.

What does the log show?

If X3 and CbB are on the same machine, they use the same vst scanner. There is no reason to move the plug-in binary around, just make sure the scan path in X3 and CbB are the same in preferences. Assuming X3 and CbB are on the same machine, open the plug-in manager while running CbB and see if the plug-in is in the Exclude list. To check the exclude list, click on the appropriate category for the plug-in then click the Show Excluded radio button below the plug-in categories. If the plug-in is there, try to enabled it by clicking on the plug-in then click the "Enable Plug-in" button. If that fails you can try a manual scan in CbB with "Rescan Failed Plug-ins" enabled or a Reset (also an option of the plug-in is not excluded) from preferences (same link as above). Make sure to enable the "Generate Scan Log" option so that a record of the scan is retained. This can help if the plug-in fails either scan attempt. If using the manual scan with rescan option, make sure to turn the rescan option off after the scan.

Please edit the OP and add [Solved] to the subject line Compressed folders do not play well with the DAW. Don't see it very often and it is the source of a lot of confusion when encountered. Glad you got it sorted.

After reading your comment I tried removing all drum maps and only leaving a few that have ASCII characters in the folder and they still do not show up in the background. This goes for the path to the drum maps as well. Also make sure the folder is not compressed. Maybe the install and or the drum map path are not in the default locations. If so, it may help to know more about the install.

Just like upgrades from the past, the installer does not look for existing plug-ins. ALL Cakewalk DAWs use the same "Shared" folders. As I mentioned above these are updated by CbB. They are backward compatible. I have SONAR X2, X3, Platinum and CbB installed. They all run OK. There are very few VST plug-ins installed with CbB and anything overwritten by CbB will be the same or newer versions of plug-ins that came with Platinum. For a complete list of the plug-ins included with CbB see http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Plug-ins.1.html Many of the plug-ins are DX and ProChannel format. These are installed in the "Shared" folder area. All Cakewalk DAWs must be shut down when performing an upgrade so the shared files can be updated. SONAR Platinum is still available in your old Cakewalk Account along with the Cakewalk Command Center to install it. If you have trouble accessing your old Cakewalk account support@cakewalk.com can reset the account password. I would recommend you make sure you have access to the old account even though you may not immediately have need for it. I am pretty sure that everyone who replied to this thread along with many of the forum users have performed the upgrade from some version of SONAR to CbB. The upgrade follows a decades old pattern of SONAR upgrades. This one just has a slightly different product name.

Please Do not cross post

The project templates supplied by Cakewalk may be overwritten without notice with a later update. The only way to prevent losing custom templates is avoid using the template names supplied by Cakewalk or create a custom location for project templates. The template path is specified in preferences. The Cakewalk supplied templates update the default location only.

The image is set in the notes browser IIRC, it is a little fiddly with project templates. The image area does not get written when the template is created but will when the template is updated.

Drum map presets are not plug-in instruments that appear in the plug-in browser Here is the documentation about drum maps. It saves a lot of typing. The Studio Instrument Suite (including SI-Drums) is a separate install performed from the Install Addons... option found in the menu to the right of the CbB Open button in BandLab Assistant. Once installed and scanned, the plug-ins will appear in the plug-in browser.

Open a project then open preferences with the project open, see if this make a difference

I used this string in Google site:forum.cakewalk.com Lexicon MX 200 There are a few detailed posts about users setting it up like this one http://forum.cakewalk.com/FindPost/1577372 There are a couple more in the thread This post is about the MX300 http://forum.cakewalk.com/FindPost/2958074 There were a few from 2005. Can't believe it is worth the effort but it is one way to spend a long weekend.

http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x2011A

Search the old forum. There are a few threads about setting it up. The VST plug-in is for controlling the hardware. The audio routing is handled like any other external hardware.

https://help.cakewalk.com/hc/en-us/articles/360021858293-What-happened-to-Cakewalk-SONAR-What-happens-to-everything-I-paid-for-

No, auto-save is not a per-project setting. The Project section on the preference screen contains the settings stored in the project.

To set the sample rate for new project use the File > New dialog and make sure to add an audio clip before exiting the project.

Yes, I hope everything gets fixed to every ones satisfaction too.

Yes, an audio interface can only run at one sample rate at a time.

Suspend Audio Engine When Cakewalk Is Not in Focus but sharing the ASIO driver should not be a problem with most Windows programs as they do not use the ASIO driver. Most use regular Windows drivers. Those programs that can use the ASIO driver usually may be set to use Windows audio too. This eliminates the need to share the ASIO for most users. As a rule web browers do not need access to low latency ASIO drivers unless they are being used for applications like web-based DAWs. They run fine using regular Widows drivers. Only a few support ASIO drivers.

This could all be avoided if drum synth plug-in developers added the appropriate information to their plug-ins. There is an opcode available in the VST specs that provides for assigning names to notes. The old Cakewalk Session Drummer, the BFD series and now Sitala appear to be the only plug-ins whos developers bothered to do this. Implemented this way the note names in the DAW are synced with the plug-in. Add a kit piece/swap out or rename a drum in the plug-in, refresh the DAW and the new names appear in the step sequencer and PRV Notes Pane no instrument file or drum map needed. Since most plug-in developers choose not to add this feature it up to the DAW developers and users to work around the missing data. If the goal is a better way for Cakewalk to associate instrument names with notes making alternate note names in the Notes pane persistent across sessions seems like a more direct solution - request logged some time ago.

Don't have the unit and have no experience with one. I would not consider it as my primary DAW interface because it is battery powered and class compliant (IOW no manufacturer supplied ASIO driver).

If you want to use FreeG at least get the 64bit version directly from Sonalksis If loudness monitoring is important, Insight 2 is on sale for $39 at Plug-in Boutique. Melda Production's MFreeFXBundle includes 64bit loudness meter and spectral analyzer plug-ins. While free, they also offer a licensed version with a few extra features. The license is current on sale for $30. For a free alternative to the gain control in FreeG consider Blue Cat's Freeware Plug-ins Pack II

intellectual property

There are not a lot of direct audio inputs on a PC and none of them are designed for DAW use. There may be a line in or mic in that could be used but the results won't be that great. Kind of defeats the purpose of having a $300 direct box. If the goal is to connect a guitar or microphone to the PC for recording in a DAW and the Torpedo C.A.B. M+ can be exchanged for an audio interface, it may be a good idea to do so. You need an decent audio interface more than a device like the Torpedo C.A.B. M+ to work with a DAW.