scook

Depends on how monitoring during recording is performed. Most audio interfaces have a way to adjust the mix of the direct and DAW signal. If everything is monitored through the DAW try dim solo or create a send for each track to a "monitor" bus and route that bus to interface. This provides level control separate from what the master bus receives.

Bit depth should not matter but an audio interface can only operate at one sample rate at a time. Here is one way to get to the Win10 sample rate setting

Are they be listed in CbB Preferences > MIDI > Control Surfaces?

Bit Depth is not the same as mp3 Bit Rate Click through the "Save As" export window to access the mp3 export options including Bit Rate.

Verify the CbB and Windows sample rate are the same.

If a user has access to a version of SONAR that includes Rapture Session, the installer for Rapture Session is separate and available though Cakewalk Command Center. The installer needs to run after Cakewalk Sound Center. If Rapture Session has already been installed before CSC, it should be uninstalled and reinstalled (or rolled back and forward) so the installer can copy the CSC programs.

Yes, Rapture Session was a Cakewalk Sound Center, Dimension Pro and Rapture player. For it to play these synths' programs, the plug-in needed to be installed after the legacy synths. The install process scanned for the legacy synths and copied their programs into the Rapture Pro/Session program folder. Of course, this does not help anyone with an X series or older version of SONAR, Music Creator or other Cakewalk DAW; BandLab has yet to release their version of Rapture Pro/Session.

The Sonitus plug-ins were never available as 64bit VST plug-ins. There was a time when Cakewalk sold the Sonitus Suite separately. That package included 32bit plug-ins in VST2 format.

Not sure the symptom calls for re-installing CbB. Regardless there are two methods to perform a CbB re-install. 1. The simple method uses BandLab Assistant to uninstall CbB. Once uninstalled, the Open button changes to Install. 2. A clean install is described here Regarding the Melodyne runtime uninstall, there is this thread

It may be the audio is coming from outside the DAW and not a soft synth in the DAW. External audio sources must be recorded into the project before they will export. What is the MIDI track output setting?

To open synth UI click the small icon to the left of the track name

When sharing the same audio hardware (such as the internal PC sound chip) between CbB and Windows and make sure that both Windows and CbB are set to the same sample rate. Sample rate for new projects and projects without any recorded audio in CbB is set in preferences. Here is how to set sample rate in Win10 If running Win10 try using the WASAPI driver modes instead of ASIO in preferences. Double check the output drop down in the project's Master bus. It should be set to the audio output device selected in preferences.

What this did was install FL Studio's version of ASIO4All. Unlike some DAWs, CbB does not need an ASIO driver to work. CbB support a variety of driver modes. For those using CbB and Win10 who do not have a dedicated audio interface with a factory supplied ASIO driver, using one of the WASAPI modes is often a good solution. Generic ASIO drivers like ASIO4All and FL Studio are not really drivers at all. They are wrappers that present Windows WDM drivers as ASIO to programs that can use ASIO such as DAWs. CbB natively supports WDM too. Should you ever get a dedicated audio interface with a factory supplied ASIO driver remember to uninstall the FL Studio Generic ASIO Driver as an interface should have only one ASIO driver installed.

The message is cause when something is routed to a destination that no longer exists. The message indicates the problem is with a bus called Master but consider reviewing the output settings for tracks, sends and buses. Anything that can send data out of the DAW. It is not a fatal message, just a warning that one or more output drop downs in the project is going nowhere. This message even appears when an output is intentionally set to None.

If the machine has internet access, could try Cakewalk by BandLab. There have been a lot of bug fixes since 2012. The only impact installing CbB has on 64bit X2a is it will update the shared folders which include the plug-in manager, vst scanner, DX plug-ins and PC modules. While it is extremely unlikely to cause a problem with X2a, the worst that could happen is it may result in a need to perform a clean install of X2 and X2a. Something which may be on the short list of things to try anyway.

Not likely. Like most DAWs, CbB cannot use mp3 files directly in the project. All audio in a project must be wav (or wav64) files using the project sample rate. The conversion to wav along with sample rate conversion happens when importing the audio into the project.

When adding legacy plug-ins, to insure the most recent version of the plug-ins get installed, usually the best solution (albeit sometimes not the easiest) is useing the installer from most recent version SONAR available. For Z3ta+ though, since the synth was last updated in 2011, an advanced install of X3 will likely pick up the most recent version.

Contact support@cakewalk.com to regain access to your old Cakewalk account. You should use Cakewalk Command Center to install SONAR Platinum and the included content such as Dimension Pro once support restores your account access. Then use BandLab Assistant to install Cakewalk by BandLab

https://help.cakewalk.com/hc/en-us/articles/360021858313-How-do-I-access-my-older-Cakewalk-programs- Platinum should be installed before CbB

Depends on the version of CbB. Prior to CbB 2019.09 build 25.09.0.68 depressing CTRL invokes quick group for all tracks. Starting with CbB 2019.09 build 25.09.0.68 quick group is disabled without an active track selection.

Please do not cross post. Continue using While backup is always a good idea, uninstalling CbB does not affect user modified files including project data.

Seems like this guy had the same problem

This type of report should be made in the 2020.05 feedback thread A thread is created each time a version is released. Problems with the current release should be made in that thread. Here are some additional steps for reporting crashes

If I was experiencing this problem, before opening a ticket with support I would try to create a recipe for the failure using plug-ins bundled with CbB. Here is a test I might try. start CbB (if the machine has not been booted today may want to do that too, I turn off my machine every night and cold start the machine every morning, no sleep/hibernation mode used ever.) create a new project with the "-- Blank Project --" or an unmodified BandLab supplied project template. (Make sure to specify exactly which template was used to create the new project when reporting to support) using the add track menu, add "SI-Electric Piano" as an instrument track to the project (I selected this synth because it is supplied with CbB and part of the same family of plug-ins as "SI-Drum Kit", one of the plug-ins reported as a problem) record enable the track and record some MIDI notes using the keyboard controller making sure to include notes in the range documented for SI-Drums (roughly MIDI notes 35-59). verify the notes are recorded and play as expected on "SI-Electric Piano" with the cursor at the end of recorded MIDI, replace "SI-Electric Piano" with "SI-Drum Kit" by right-clicking the small icon to the left of the track name and selecting "Replace Synth" from the context menu then selecting "SI-Drum Kit" from the available synths. repeat step 4 verify the notes are recorded and play as expected on "SI-Drum Kit." If step 5 fails, the problem is not a Drum VST issue. If step 8 fails, this is a recipe to report to support. If step 8 does not fail then try steps 1 though 5 using "SI-Drum Kit" instead of "SI-Electric Piano." Make sure each step is performed exactly as the initial test all input settings must be identical to the initial test. If the second test fails, this is a recipe to report to support Include the info about the test that passed and the test that failed. When supplying information to support include as many details as possible. Include info about the OS and release level of CbB. Details about the keyboard controller and audio interface. Include how the controller is attached to the PC. Include the test projects.