scook

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.

Are you running 44.1kHz sample rate?

The file format is the same. Themes of any age will load into any DAW supporting themes but the results may not be 100%. New colors and images are not the problem. When new items are added to themes older versions of CbB and SONAR ignore them. However, sometimes items are removed or names changed in the resource files. When this happens themes made against the new resource files will not contain any changes to the now missing items. Loading these themes in old DAWs using the old resource files will cause the themes to look incomplete. Dark themes tend to do worse because of the way themes work. Of course, anyone can change a theme to suit themselves. Fixing a theme for a particular release is doable. It just takes the will to deal with the theme editor and possibly an image editor.

FWIW CbB includes REmatrix Solo in the ProChannel

Use the like icon in the bottom right of the OP or use the rate option above the OP.

OS? Is CbB subject to virus scanning? Notification settings

There is a program in DPro in 12-Bells called 50's Vibraphone. Rapture Session/Pro make searching DPro and Rapture programs much easier. Before Rapture Session/Pro, I used Windows Explorer to search the program folders: C:\ProgramData\Cakewalk\Dimension Pro\Programs C:\ProgramData\Cakewalk\Rapture\Programs. Often times, this was easier than looking the the synth browsers for a particular sound.

Since the introduction of patch points is it possible to directly record audio affected by plug-ins and soft synths. When doing so, it is a good idea to record the raw audio and MIDI data (if any) too. To record audio with plug-ins use a patch point to send the audio to another track or use an aux track. Record enable both the original track (to capture the dry signal) and the track with the patch point input or aux track (to capture the wet track). For synths see synth audio recording.