scook

To hear the signal at a track's input requires enabling the track input echo button to the right of the record button

There is no need to rename the dll. At least, I did not when testing the plug-in.

Got it, misread the OP. Yeah, this request has been on file for years. Here is an example from a while ago

Melodyne is not a normal FX plug-in. While it may be placed in the FX rack, the audio signal does not pass through the plug-in. Instead the signal originates from the plug-in using the data transferred to it.

It may depend on how Melodyne is used (an FX or Region FX) and where the Prochannel is in the signal path (before or after the FX Rack).

There is also a dedicated VocalSync tool.

Don't have a Focusrite interface but I thought all drivers show a Left, Right and Stereo option for each pair of inputs. The left being the odd number channel, the right being the even number channel and Stereo being both channels of the pair.

If there is any noise on the right channel summing the channels may not be a good idea.

AFAIK Melodyne 3 is the 32bit Melodyne Studio. I suppose it will work with CbB but I have never seen a copy of it. Melodyne 2 and Melodyne 3 were folded in to a single product, the Melodyne 4 series. This is the first time all 4 flavors of Melodyne used a common code base and it was the first 64 bit version of Melodyne Studio.

This is not part of the synth. It is a header added by the DAW used in the video and is not necessary to get audio into the synth in CbB. Although the Surge documentation claims Cakewalk is incompatible with Surge audio processing, it works when dropped in an audio track FX rack. Add a MIDI track with its output set to the synth for MIDI control. Then follow the info starting with 3. Basics of using Surge in compatible software in https://github.com/surge-synthesizer/surge-synthesizer.github.io/wiki/Using-Surge-as-an-effect-(and-vocoder)

This usually happens when trying to run on an unsupported display. The program requires a minimum screen resolution of 1280x800.

Several audio tracks appear to be recorded on the left channel only. This happens when a mono instrument or microphone is plugged into the the odd channel on the interface and the DAW is setup to record in stereo. Mono instruments and microphones should be recording on mono tracks in the DAW. This may be corrected by bouncing the tracks using the "Split Mono" format, adjusting the pan on the good track and throwing away the track made for the right channel. The lead vox track is recorded too loud. It shows a peak level at -0.3.

Turning off Always Import Broadcast Waves at Their Timestamp will cause CbB to ignore the timestamps

LICEcap

If that fails try (temporarily) removing the Realtek registry entry from HKEY_LOCAL_MACHINE\SOFTWARE\ASIO

So the only two ASIO driver choices in CbB are Realtek and Tascam. The Tascam is powered up and after deselecting both Realtek I/O options in devices, CbB does not immediately allow Tascam to be selected? I would try re-installing the Tascam drivers.

no, there is one tempo "track" for a project and all MIDI data in the project follows this track's tempo.

To change ASIO devices, deselect both input and output preferences then select the device to use. Given how bad the Realtek ASIO driver is, it may be a good idea to delete it.

Pick your poison https://www.musiciansfriend.com/claves-sticks-blocks

A DAW MIDI track is similar to a hardware MIDI cable. A single MIDI cable may have up to 16 channels of MIDI data. In the link they talk about an interface that supports 8 instruments for a total of 128 channels. IOW 8 instruments each with 16 channels of MIDI data.

Pitch bend is MIDI Event type Wheel

right-click on the envelope for the context menu http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Automation.11.html#1158748

This does seem strange and I am unable to reproduce the problem

Common problems when using the internal PC chip are running Windows and CbB at different sample rates (audio devices run at one sample rate at a time) using the Realtek ASIO driver (bad driver) using small buffer setting (trying to achieve low latency a small buffer setting may cause distortion) If the Realtek ASIO driver is installed adding ASIO4All can be a problem because there are 2 ASIO "drivers" installed for the same device. If both are installed consider removing one or both of them. When running Win10 try using the WASAPI driver modes.

Paths should be unique. In the image below, c:\program files\cakewalk\vstplugins\cakewalk sound center is redundant and should be removed. The plug-ins in that path get scanned as a result of c:\program files\cakewalk\vstplugins being in the scan path.