scook

SHIFT-C

You may create a shortcut key to call up the Tempo Change dialog. To do so open Keyboard Shortcuts in preferences search for tempo in the Global Bindings Area assign an unused key combination to "Project | Insert Tempo Change"

The MIDI output drop down is exposed in the MIDI tab of an instrument track inspector just below "I" in the image below But that is only half the job. To change a synth in an instrument track also requires changing the audio input. This requires splitting the instrument track to gain access to the underlying audio track input drop down. Or use "Replace Synth" in the track header context menu.

CbB uses a different folder for themes. The OP asked about SONAR Platinum, at least that is how I read it. By default both use folders in "Cakewalk Content." But you may be right. Re-reading the OP it may be a question about CbB and NOT Platinum. If the question is where are CbB stored - by default they are stored in C:\Cakewalk Content\Cakewalk Themes

Yes "Cakewalk Content" may be anywhere on the PC. By default it is the root of C. By default several of the entries in Folder Locations in preferences use "Cakewalk Content" such as Track Templates, Track Icons and CAL Files. Another way to see where themes should be is run the theme editor (assuming it is installed) and try to open a theme. It should open the theme folder. The Edit button next to the theme drop down in preferences runs the theme editor.

Don't use dots in project or export names Add .wav to the files if you do (and you are exporting wav files otherwise add the appropriate file extension for the export format).

Noel has been recommending this for years It may be time to disable the scanner in the PIM when running CbB.

C:\Cakewalk Content\SONAR Themes

Probably no need to physically move the plug-ins. A directory junction in the 64bit path pointing to the 32bit path should work. Running as administrators open a command shell and type mklink /j "C:\Program Files\Cakewalk\Vstplugins\32bitPath" <enter the real 32bit path here> Name "C:\Program Files\Cakewalk\Vstplugins\32bitPath" what ever you want in the current 64 bit path

Uninstalling will likely removed the shared folders used by SONAR and CbB. These include PC modules, all the DX plug-ins and utilities such as the plug-in manager and vst scanner. As mentioned above removing the DAW itself does not free up much space but if you installed the Platinum tutorials run the Cakewalk Command Center, right-click SONAR Tutorials and delete them. It will free up almost a 900MB. If you never archived and purged the Cakewalk Command Center download cache, now would be a good time. Click the Gear in the upper-right of Cakewalk Command Center to open its settings, click the Paths tab then click the folder to the far right of the Download Path. This opens the folder containing all the installers downloaded by the Command Center. Back them up, then delete the files. Depending on the last time this was done, this could free up a lot of space.

Check out the Matrix View

Several drum plug-ins has this feature.

fixed

Another thing to try is adding the 32bit plug-ins to the 64bit folder that is getting scanned.

or C- created a project without a master bus. This happens when a user starts a project without using a factory supplied project template or their own template where they failed to add a master bus.

Did you try copying the records from the Platinum VST Inventory to CbB? May want to export the Platinum registry as a backup.

No, it was part of SONAR a product BandLab did not purchase. BandLab purchased the IP not the products from Gibson. Currently the best way to integrate the Reference Guide PDF is add it to the Tools section of the Utility menu. If one needs more help doing this please post in this thread.

Email service for the old Cakewalk site was shut down when Gibson closed the company. CbB supports mp3 export. I do not know if support@cakewalk.com can send out the old Cakewalk mp3 unlock program.

The track volume fader is after the FX Rack and Prochannel so, lowering the volume fader does not affect the signal going into the plug-ins on the track. Refer to the signal flow diagram.

Don't believe so but you may enter the number directly into value field.

Use this page in preferences for all VST scans and settings. Only use the plug-in manager for exclude list and layout management.

FYI CbB and SONAR use the SAME scanner and plug-in manager on the same PC. Their VST inventories are in different places in the registry.

Make sure to do everything from preferences NOT the plug-in manager (except for exclude list and layout management).

Worst case you could copy the registry entries for the missing plug-ins from Platinum into CbB.

I don't use jBridge. I ran a reset a couple of days ago and the few 32bit plugins that I have scanned OK. Running a VST reset from preferences can't hurt. Make sure to create a scan log. There may be a clue about what is going on in the log. The only recent change I know that happened to the scanner is it no longer scans dll in the VST3 folders.