scook

There is no local help for CbB. The local help option in Preferences was removed. I do not believe there are any plans to release the help in alternate formats. There was some discussion early on about making the html downloadable but there has not been any mention in some time.

It would be nice to have search available for the CbB help. Until that time, here is how I located the urls for posting here:

1) use the web search to generate results for old Cakewalk products

2) narrow the search for Platinum, Professional and Artist Documentation using the link at the top of the search results

3) select a topic

4) if the topic is what I am looking for, I replace SONAR in the url to Cakewalk

5) open the new url

Most times this will open the appropriate CbB help. If it does not, for example if the SONAR page is in "New Features," I fall back to the CbB help index.

AFAIK, the local help code switch "UseOnlyOfflineHelp" and the supporting code are still in place. Most of the most recent SONAR help is still applicable to CbB. I have not tried it recently but it still may be  possible to use the chm from SONAR by copying the chm into the CbB program folder and setting "UseOnlyOfflineHelp" to 1 in HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Core

By default, project templates are stored in C:\Cakewalk Content\{DAW Name}\Project Templates

I prefer to change the Template path in Preferences because a custom path is not updated by the installers and I do not have to copy templates with each new DAW. Since Platinum and CbB the copy is less of an issue but updates by the installers are more frequent.

The MS library to support multi-touch prevented XP from installing X2a.

It does not matter - some force everything into the Cakewalk default folder, some use a folder outside of Program Files, some use manufacturer defaults. There is no standard location for VST2 plug-ins. The VST3 spec provides a standard location and VST3 installs should use it but even then Cakewalk will load VST3 plug-ins found anywhere in the scan path. Some programs are not as forgiving.

Starting with SONAR X3 there is no need to configure any effect as a synth. If the VST plug-in reads MIDI data, make sure "Enable MIDI Input" is selected on the VST2/3 drop down above the plug-in UI. If the plug-in sends MIDI data select "Enable MIDI Output" from the same drop down. Doing this will cause the plug-in to show up in the input and output drop downs of MIDI tracks

Here is an image of both options selected for the MidiShaper plug-in by CableGuys

To summarize, the setup is the same for any effect plug-in that reads MIDI data. The steps are:
1) add the plug-in to the FX rack of the track/bus to be affected
2) Use the VST2/3 drop down above the plug-in UI to "Enable MIDI Input"
3) Add a MIDI track with input set to the controller, output set to the plug-in, enable input echo

For plug-ins that send MIDI data in step 2 "Enable MIDI Output" then there is an additional step to add the plug-in to an instrument or MIDI track input.  The additional step may be instead of step 3 depending on the plug-in.

CbB runs on Win7 but is developed and optimized to run on Win10. Very little testing is performed on Win7.

The only other non-destructive way is the Transpose MFX. Insert into one track, setup the parameters then CTRL drag/drop to each of the MIDI track FX Racks

The fastest destructive way is Process > Transpose

Quick Groups

In short, select the tracks, hold the CTRL key and select the desired operation in one of the tracks. All of the selected track will perform the same operation.

contact support@cakewalk.com

Since the project may be opened, have you tried rebuilding it? If not, it may be a good idea to save incrementally under new names while rebuilding and test adding DP after each save.

AFAIK, the start screen should display everything with a cwt extension in the folder defined in preferences for Templates.

Click the black dot or star to the left of the subject.

The stars are threads where you posted.

No black dot or star indicates no activity since last read.

Does the plug-in show up in the Plug-in Manager?  If so, which plug-in layout are you using?

Please add version information for the OS, DAW and DP.

May want to look at the Windows Event log for clues to white screen.

I doubt tuning is the problem but could test it by creating a new project, detune DP, save and see if it will load.

CbB includes BitBridge. The same BitBridge that was bundled with SONAR for years. That said, if a manufacturer supplies a 64bit version of the plug-in, more often than not the 64bit version is a better solution that loading Bitbridge. As a rule, 64bit VST plug-ins are drop in replacements for 32bit VST plug-ins of the same release. It appears the latest update to Battery 3 has a 64bit VST (see https://www.native-instruments.com/forum/threads/does-battery-3-work-on-windows-10-64-bit.269915/)

IIRC, Battery 3 also shipped in DX format. No 32bit DX plug-in will be recognized in a 64bit host.

When a plug-in does not show up in the plug-in list, here are a few things to do:

See if the plug-in is in the exclude list in the Plug-in Manager. If so, try a manual scan with "Re-scan Failed Plug-ins" enabled (make sure to disable the rescan options after the manual scan)

Run a scan log - the option is on the same preference screen as the re-scan options

Run a VST reset - same preference screen. This will clear the VST Inventory in the registry and rescan the plug-ins.

Dropped MIDI notes usually means the Prepare using nnn Millisecond Buffers setting is too small. The default is 250 but many get better results with 500 or 750. Some use an even higher value.

No

Should be in the track inspector and console track strip for audio tracks in Platinum and audio tracks in the track view starting with CbB 2018-05

Depends on the source material and version of Melodyne. Here is information on the algorithms.

https://www.cakewalk.com/Command-Center

Before wiping the system check if you already have the Platinum installers. To see if the installers on still on disk, run the Command Center, click the gear in the upper right, click the Paths tab, the click the folder icon to the right of the Download Path. This will open the download cache. If the installers are there save them before wiping the disk and restore them after installing the Command Center. This will save the time it takes to download the installers.

Don't forget to grab the XLN installer if you use the bundled Addictive Drums. It is on their website.

Melodyne will come from the Celemony site. If you are using v4 of Melodyne, hopefully you saved the v4.1 installer. If not you are stuck using v4.2 or you will need to contact Celemony support to get the older version if you have trouble, like many do, with v4.2.

Current recommendation is install Platinum including the DAW itself. Pretty sure some of the Platinum exclusive plug-ins will not install if the program is not installed. To save space, do not install the tutorials. Once Platinum is installed add BandLab Assistant to get CbB.

This is a known issue with Melodyne 4.2.  To get around this problem first open the clip as a Melodyne Region FX clip, make sure the algorithm is set properly then try dragging the clip to the timeline.

May have the same issue with audio to MIDI. The same workaround applies.

I believe Celemony will provide the last 4.1 release if you contact support. This version should work as expected.

full url is https://audio-assault.us10.list-manage.com/track/click?u=103973dfc53e49bb06f89a912&id=c7059fb689&e=94d9fdc72e

Maybe plug-in related. Might take a little sleuthing to isolate the plug-in. If there are any 32bit plug-ins in use, test them first.

This  plug-in

Should be listed in clip context menu under Process Effect > Audio Effects

It is not listed in any other plug-in list. It is an offline effect. The plug-in is not bundled with CbB but should be available if SONAR is installed.

11 hours ago, mdiemer said:

Hello there, it won't work for me. It will cause very nasty noises and crash everything. Same thing happens with TTS-1. both are DXI so I'm suspecting it has something to do with Direct X. Also, and I have Windows 7, which may also be a factor.

Are you running 44.1kHz sample rate?