scook

Yes, see the link to Printing in Notation and Lyrics

It shows $99 on the product page in the U.S. but add the item to the cart and and the price drops to $49

The PC module is still included

CbB will automatically set up TTS-1 when opening MIDI files if there are no MIDI output devices selected in preferences.

Automation problems make me wonder if CW130Auto.dll somehow got out of sync with CbB. Right-click then open properties and compare the file version under the details tab for both C:\Program Files\Cakewalk\Cakewalk Core\Cakewalk.exe and C:\Program Files\Cakewalk\Shared Utilities\CW130Auto.dll they should be the same.

ARA is the tech behind Region FXs. Notice in the CbB signal flow diagram Region FX is in the clip section before the Clip FX rack. Check out the Region FX section of the help there is a lot of good info about Region FXs in general and Melodyne. If you prefer here is an old SONAR video showing Melodyne as a Region FX

The "Advanced Install" option was available through SONAR X3. Newer versions do not have this option relying on multiple installers for the bundled content. Some of these installers validate the appropriate version of SONAR is installed prior to running.

The link in @Noel Borthwick's post is an early release of 2019-12 build 23 not available through BandLab Assistant. .

While waiting for this to be implemented - try creating a category folder at the top of the "Sort By Categories" to hold favorites or create a custom layout and add the plug-ins either directly to the top of the layout or in a folder

https://www.meldaproduction.com/downloads

Here is the thread about my tools It goes into some detail about this. The short version is... Recently there was a change to cw130Auto.dll, a file shared by all versions of CbB, that can break automation when running a version of the dll that is not the same as the version of CbB in use. The Lauchpad tool makes sure CbB and the dll are in sync.

No but given this you may not want to change the default. If there were a way to change the default, it should probably not be a global setting. It should be added to the plug-in properties page.

Not unless you have planned for this event. To save some typing... NOTE: old posts refer to simply copying and renaming folders to create working versions of CbB. This is no longer a safe practice. To have multiple versions of CbB available online use Launchpad.

Click the keyboard on the right-hand side of the VST standard header above the plug-in UI. "J" in the image below from https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Mixing.28.html

The object of the MIDI OX exercise is to validate the data in the PC. If the values are low in MIDI OX, I doubt the problem is PC (at least I have not read about a PC causing this problem), how are all these devices connected to the PC?

It is not normal and why I suggest checking the data stream in the PC before it hits CbB with something like MIDI OX. I did not read the OP fully before my initial reply. The suggestion to use the Velocity MFX was in response to the post made by @User 905133 not the OP.

CbB records audio and MIDI as it is sent to the DAW. You can inspect the MIDI data stream being sent to the DAW using something like MIDI OX.

Here is the documentation on applying real-time effects. The images show audio tracks and buses but the FX Racks are in the same place for MIDI tracks. You can also add FXs to the Rack by clicking the + at the top of the rack or right-clicking in the rack. There is no global MIDI velocity curve adjustment so the plug-in will need to be added on a per-track basis. To globally affect MIDI velocity would have to happen before the data hits the DAW. I am sure there are tools to do this but I have not needed one.

The Event View will not change because the effect is being applied non-destructively. IOW, the data in the clip is not changed, The values are changing as they are streamed to the synth. By default the plug-in has the Set To button selected and its velocity slider set to 100. So all the values are set to 100 during playback. To scale the data, click the Scale radio button and change the scale to 182 (about 128/70) to scale the data over 0 to 127. Click the F1 key with the plug-in UI in focus to bring up its detailed help.

Is only going to be enabled if MIDI Effects are on the track. This step destructively applies the effects. It is not necessary. Place the MFX in the MIDI FX Rack and it will be non-destructively applied to the track.

Instead of using the destructive Process menu, try putting the plug-in in the MIDI FX Rack.

Yes but as mentioned above it may be a workspace issue. The image shows no workspace is loaded. The workspace setting is one of the first things to check when settings don't stick. Answered something similar earlier today

Could try the Velocity MFX using scale set to 182%.

If you are going to use a plug-in, you could use the keyboard in the PRV Notes pane.

Yes, it is probably 32bit but is a freestanding program that connects to the DAW with a virtual MIDI cable. Before Cakewalk added their virtual keyboards, it was a solution I used to post on the old forum. There are a couple of other virtual keyboards that work the same way. Don't have a 2/4K Monitor to test.