scook

Any FX plug-in that supports MIDI input has the option to "Enable MIDI Input" in its VST2/3 drop down in the standard header like this After selecting "Enable MIDI Input", the plug-in will appear in the output drop down in all MIDI tracks. Create a MIDI track set the output to the plug-in.

They are in the new release announcements like this one for 2021.01

Deselect all the MIDI output devices in preferences

May be an install problem. I just tested and it worked fine in CbB. I have X2a/3e Producer, SONAR Platinum and CbB installed using all defaults. If you removed the version of SONAR which included the BT bundle it may have messed up the license. It may be possible to re-install to recover without performing a clean install but make sure to install CbB last to insure the shared folders are up to date. WRT Don't Crack and the bundled BT plug-ins the email they sent out is memorialized in this thread http://forum.cakewalk.com/FindPost/3699781 Don't Crack routinely puts the Nomad plug-ins on sale. There has been at least one important update since the BT bundle was added to SONAR.

Try changing the MIDI driver mode

https://help.cakewalk.com/hc/en-us/articles/360021858293-What-happened-to-Cakewalk-SONAR-What-happens-to-everything-I-paid-for-

With the recent updates to CbB, I rarely run BA. Often it is when someone posts on the forum. Just ran it and got the prompt to update. Updated to v7.0.0 OK.

Bad assumption. The only items in preferences stored in the project are listed under Preferences > Project. The rest of the preferences are the current global settings. The project modified date does not mean much WRT audio clip data as they are stored separately from the project file. The clip depth shown in the image is the result of either recording or rendering at 32bit.

Audio Driver Bit Depth has nothing to do with Record or Render Bit Depth Driver bit depth is what the driver will send to the DAW. Record bit depth is what the DAW will use for recording. Render bit depth is what the DAW will use for bounce, freeze and export. Note all of these effect how the DAW will operate in the future. They have no effect on existing data. Most ASIO drivers work a one bit depth. This is why the setting is disabled in the video above.

It's called Ripple Edit

SHIFT+left/right arrow

While waiting you could extend the CAL script to do randomize velocity and note lengths. There is a randomize function in Velocity MFX and Quantize MFX bundled with CbB. There is also a user created MFX for humanize Frank's MIDI plug-ins also include a humanize MFX

As a rule a plug-in's UI is usually designed for audition purposes. In some cases, they generate MIDI data but the plug-ins are after the track's input. In all cases they generate audio which may be recorded as it occurs before the audio track (assuming the use of an audio+MIDI pair of tracks and not an instrument track). Either way using the plug-in UI is an awkward way to record. The virtual keyboard provided with the DAW, step recording or one of the editors are better choices. Ultimately, a real keyboard controller or other input device are the best long term solutions. There are some lengthy threads on this subject already on the forum like this one

The DAW and nothing bundled with the DAW require running as administrator. Some XP era plug-ins need access to protected parts of the registry. Some 3rd party plug-ins try to write to their plug-in folder. Often rather than address the cause of these issues some users elect to run the DAW as administrator.

Missing drag and drop from the OS is often the result of running the DAW as administrator. Windows does not allow drag and drop into programs with elevated rights.

v2.0.7 added a couple of extra checks to prevent cw130auto.dll from getting out of sync with CbB. Note: v2.0.6 and 2.0.7 are Launchpad specific. These changes do not affect the other tools.

I have no idea what series of events cause the error. While I have seen the old version fail, it never failed silently. There was always an error message thrown by Launchpad. That said, I rarely run the DAW outside of Launchpad. It does not matter where CbB is installed. As long as it was installed correctly, the registry holds the path to the shared utilities folder used by all Cakewalk DAWs and CbB. If one attempts to have any Cakewalk DAWs and CbB installed on different drives, there will be problems. Running the current version of CbB from Launchpad before exiting should write the current cw130auto.dll is into shared utilities. When the cw130auto.dll is out of sync with CbB, it can crash the DAW.

Putting synths in an audio FX rack should be avoided unless the synth is designed to work on an audio stream such as a vocoder. Only MFX plug-ins are permitted in MIDI FX racks. Instead synths should be added using one of the insert synth options or dragging the plug-in from the plug-in browser and dropping in the empty space below the tracks. Here is some info on using the Add Tracks menu http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Arranging.14.html It includes a section on adding instruments.

The old "Cakewalk Launchpad.exe" did not use shortcuts. The new "Launchpad.exe" is a shortcut created by "CbB Tools.exe" to run Launchpad without starting up "CbB Tools.exe" first. There is no confusing the old version with the new one. They are visually very different. If you have any more questions about Launchpad here is the dedicated thread for CbB Tools including Launchpad

There should be a directory called "sub" where the "Cakewalk Launchpad.exe" is located. If the folder is missing that is a problem. To use v2 you will need to copy "CbB Tools.exe" in the same folder where "Cakewalk Launchapd.exe" currently resides or it will not pickup the old dlls. The new version relies on the same "sub" folder.

v2.0.6 fixes a cw130auto.dll copy bug in Launchpad

@gmp @Noel Borthwick I found a condition that caused Launchpad version 2 to skip the cw130auto.dll copy process. The problem is fixed in v2.0.6 available now at my Google page

There may be an issue with v2 of Launchpad I am checking now.

There are only two files regularly involved in the copy process, the cw130auto.dll in shared utilities and the version needed for CbB. Launchpad first checks if CbB and cw130auto.dll are the same version If they are, the program starts CbB If not, the program looks for an appropriate version of cw130auto.dll in its backups If it cannot find an appropriate version of cw130auto.dll it returns an error message If it does find an appropriate version, if necessary, it make a local copy of the cw130auto.dll and attempts to overwrite the copy in shared utilities. If either copy fails it returns an error message The program attempts to resync on exit and always make sure the exe and dll agree before starting CbB. That said, there is always a chance the program could fail and leave the current CbB out of sync with the cw130auto.dll. This is why if one chooses to use Launchpad, they should always use it or at the very least run production from it to verify everything is in sync when encountering problems running outside of launchpad.