scook

Plug-ins take up relatively little space. Moving them off the system drive is not a good idea. In fact, the VST3 specification states plug-ins should be installed on the system drive and some program will not recognize them being installed elsewhere. If the system drive is too full, plug-in relocation is not the solution. Data used by plug-ins is another matter. Sample-based synths usually provide a way to install their samples on another drive. Those lacking this feature often can be dealt with by using directory junctions. When it comes to specifying paths for the scanner, keep in mind the scanner recursively search though the paths supplied.

Windows has a built-in system for monitoring file system changes. My guess is CbB taps into this system and periodically launches the scanner based on info provided by this service.

Studio Instruments are in a separate installer under Install Add-ons....

Remove "C:\" from the scan path This is forcing the scanner to open every dll on the system drive.

The docs are pretty thorough but sometimes a video is helpful try https://www.youtube.com/results?search_query=cakewalk+automation

The included project templates have a master bus defined. If you are not using one of the project templates: select all the audio and instrument tracks, while holding down the CTRL key, click on one of the track output drop downs and select "New Stereo Bus" In the bus pane, right-click the new bus and select "Set as Default Bus". Now any new audio and instrument tracks added to the project will automatically be routed to the bus.

http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Automation.01.html

could be similar to these

Try Bounce to Clip(s)

Try CTRL+click in an empty part of a track or take lane

Often this is caused by the Zero Controllers When Play Stops setting

I believe some Platinum installers check the registry to confirm the DAW has been installed. This means the Platinum DAW must be installed before running any of the other installers. Doing so will likely overwrite some of the "Shared Folders" installed by CbB. After installing Platinum use BandLab Assistant to uninstall and re-install CbB.

I just received confirmation the Anderton Collection is not bundled with CbB. The documentation will be corrected. I must have copied monitorizer from the Platinum FX Chain Presets folder.

FX Chains are not plug-ins. An FX Chain a container for one or more plug-ins. They are not listed in the plug-in manager. They are listed under the effects plug-ins in the browser. Starting with CbB 2020.01, FX chains are including in plug-in browser searches. I found Monitorizer.fxc in C:\Cakewalk Content\Cakewalk Core\FX Chain Presets\Anderton Collection\Processors Not sure if CbB installed it or I copied it from the Platinum FX Chain Presets folder. The Anderton Monitorizer is listed in the current CbB documentation https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Mixing.37.html#1788004 but relies on Channel Tools, a plug-in not included with CbB. Make sure the plug-ins from SONAR Professional/Platinum are installed to use this FX Chain. The FX Chain Presets folder is set in preferences.

Thanks, looks like the documentation changed since I posted the link. It is fixed now.

The user directory contains the ini files, master.ins and could contain other data depending on Folder Locations in preferences but most of the settings are in the registry. HKEY_CURRENT_USER\Software\Cakewalk Music Software HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software I have never attempted to do the level of migration you are asking about. I do it so infrequently, it is easier to start from scratch. Far less chance for error. And I have never wanted to replicate the environment so completely. Years ago, I did create a folder tree separate from the Cakewalk install where I placed a lot of custom info (template, drum maps, CAL...) and use a combination of preference changes and directory junctions to link it into the Cakewalk install. These do get carried over from machine to machine.

Upsample settings are stored in %appdata%\Cakewalk\Cakewalk Core\AUD.ini Plug-in Categories are stored in %appdata%\Cakewalk\Library\Library.db

Yes but I believe the new versions lack the PC format.

You make change it yourself by editing the original message

CbB has all the Platinum PC modules except for the two from Boz - Bark of Dog and Panipulator. My guess is for those to be included Boz may need to agree.

I don't use "convert to mono" preferring to "Bounce to Tracks" to split tracks into mono but I have not used either on a track with take lanes. If the program crashed send the dump to support following these instructions I had already started to reply when the second post appeared. Here it is. They may help recover lost sessions. If versioning is enabled you may be able to revert to a project file setup the way you want or something close to it. Since the project has already been opened again the copy made by autosave (if enabled) may be newer than the crash. Autosave creates a copy of the project in the project folder with "Auto-save Copy of " prepended to the project file.

Uninstall removes most of what the installer put on the disk and no more.

No because I take steps to prevent unexpected note playback. The combination of conditions has been the subject of numerous threads. "Enable MIDI Output" has been the default since X3 for synths with the capability, however; many synths lack the feature. "Always Echo Current MIDI Track" is also the default. Instrument/MIDI track input set to None is not the same as Omni. When set to None the track rejects all input. When set to Omni the track accepts all input. The potential for trouble happens when a track has its input set to None and "Input Echo" gets turned on. Enabling "Input Echo" causes CbB to switch the input from None to Omni. If a track is set to Omni and a plug-in is set to send MIDI data there is nothing to prevent the track from picking up the data.