scook

Could note replicate using CbB 2020.02 build 39 with a simple one-track project using plug-in in the FX rack or in a bus.

The circled area has grown over time as new features were added. Prior to CbB all it housed was the Navigator and Video Thumbnail tracks. CbB added tracks for the Arranger and Tempo.

When features appear to be missing the first place to look is the Workspace setting There is also a drop down above the track headers in the Track View that determines which controls are visible in the headers SHIFT+left/right arrow scrolls through the settings.

No but you can assign MIDI notes to start and stop the transport in Preferences > Customization > Keyboard Shortcuts

Can't be done SI-Drums ignores channel assignment. It is a very basic MIDI in/Stereo out plug-in. To isolate each kit piece in SI-Drums requires separate instances of the plug-in. Most advanced drum plug-ins don't care about MIDI channel assignment either, but they do have multiple audio outs.

Whether a 64bit DAW replaces a 32bit plug-in with a 64bit version is similar to whether the DAW knows that it can replace version 1 of a plug-in with version 2. It is up to the plug-in manufacturer to add the information to their plug-ins. If the 64bit DAW determines there is a suitable 64bit version of a plug-in the DAW will use it instead of the 32bit version.

Access to this forum has nothing to do with the old Cakewalk site. The old Cakewalk site does not have e-mail service. Password reset for the old site is handled by support@cakewalk.com For more info about legacy Cakewalk product access see https://help.cakewalk.com/hc/en-us/categories/360001718094-

OK, then I am out of ideas This is when logs may help

I thought there were 32bit and 64bit plug-ins in the same folder and 32bit only plug-ins (in some unspecified path) If all the 32bit plug-ins are in "Program Files (x86)" and were not showing up until the 64bit plug-ins were removed, could it be the scanner hung or failed before it got to the x86 folder? This is where a log can help.

I am guessing you confirmed this by adding a 64bit plug-in back and saw the 32bit disappear. Check the scan log after. If it does, try moving the 32bit plug-in to a folder under "C:\Program Files (x86) " and add it to the scan path. Can't recommend running scan logs enough while trying to sort this out.

AFAIK, there is no logic to suppress 32bit plug-ins during scans. There is logic to replace 32bit plug-ins in projects where possible but the "plug-in not found" message indicates the 32bit and 64bit plug-ins are considered different plug-ins by the DAW so the replacement logic would not happen. One possibility is the 32bit plug-ins need MS libraries that are missing from the machine. Running a VST reset with "Generate Scan Log" enabled from preferences and reviewing the log may supply some clues about why the plug-ins are not getting picked up.

You are not the first. I really wish support would add a warning about step 9 of the clean install instructions @Noel Borthwick, don't you think there should be some caution added about the potential to lose 3rd party plug-ins in "C:\Program Files\Cakewalk\Vstplugins" (and maybe even C:\Program Files(x86)\Cakewalk\Vstplugins)?

see the Locating crash dump files for Cakewalk section in

I have never bothered setting up MIDI shortcuts, but it is done the same place as regular keyboard shortcuts in Preferences > Customization > Keyboard Shortcuts. It is possible to use a note or CC to shift the keyboard into shortcut command mode. For more info see http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Templates_KeyBindings.4.html

I hate to tell you this but AFAIK, using Edge Webview2 Runtime was scrapped for technical reasons. I am not sure if Edge is a requirement, but I have it set as my default browser and have never had a login problem.

The inspector cannot go in the multidock. It may be attached to either side of the track view or float. The browser and synth rack view default to opening in a separate container similar to the inspector but in addition to floating, these views may be moved to the multidock. The docking options for all of the above are in the down arrow menu at the top of each component. When it comes to managing the size of views in the multidock, my guess is many use the shortcuts D - to expand/collapse the multidock and SHIFT+D - to maximize/restore the mutlidock

Color codes indicate plug-in format (DX, VST2, VST3) and whether the plug-in is 32 or 64 bit. The current theme determines the colors used. The default "sort by" layouts are sorted alphabetically irrespective of case. User layouts are a completely manual process.

This is correct. Bounce to Track(s) can only use tracks that may contain audio as a source. So, to bounce a soft synth, not the MIDI track.

Yes, a clean install was the next step. The confusing thing I was hoping to sort out first was the existing layout of the DAW. From everything above, it appears that even after a clean install there may parts of previous installs still resident. This is why I waited to recommend a clean install.

There is no need to freeze and bounce. Freeze is an in-place bounce+archive+disconnect synth So, to get the same result as a freeze but into a new track Select the instrument or audio track associated with the synth From the Tracks menu in the Track View select Bounce to Tracks(s)... Archive the instrument or MIDI track (the A button next to the Freeze snowflake in the track header) Using the synth rack view, click on the synth and disable "Synth Connected" from the synth settings menu "D" in the image below This is the old school method predating freeze.

The current release is 28.2.0.39

version info is in Help > About or just run Help > Check for Updates if there is an update available, the DAW will download it.

Melodyne is a separate installer. It is not part of the full or update core installers.

Studio Instruments, Demo Projects and Drum Replacer are not part of the core CbB package but are add on installer. The missing folders indicate a non-standard install. If I had to guess the original install did not use defaults. Where is the cakewalk.exe? The "shared folders" need to be installed in the same folder as "the "Cakewalk Core" folder (which contains the cakewalk.exe).