scook

Usually installers for sample-based plug-ins provide for an install path for their sample libraries. For those that lack this feature directory junctions may be used to relocate folders to another drive. Directory junctions are created using the Windows command line utility mklink with /j switch. There is plenty of documentation about mklink on the web and quite a few discussions about the utility on the old cakewalk forum. To see the old discussions use this search string on Google site:forum.cakewalk.com mklink There are quite a threads with examples of how to use mklink.

http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x18355

A slight tweak to the documented process would save automation. Export the clips as broadcast wave files. Create a copy of the project using "Save As" to a new folder. Delete all the audio leaving just the automation. Set the new project sample rate. Import the broadcast waves. Alternately, in the existing project upsample all the plug-ins that may benefit from it. Not all plug-ins do. CbB supports upsampling any plug-in so those that lack the feature may still be upsampled. I created utility to manage upsample settings for VSTs. A link to my utilities is in this thread.

If you prefer not to edit the registry directly, there is a program to maintain the Utility menu called Tools Editor. It is part of a suite of utilities I wrote. Practically anything may be added to the tools section of the Utility menu. Here is discussion thread with links

https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=AudioPerformance.05.html

For more active keys use something like PC 73 Virtual Piano Keyboard with a virtual MIDI cable, LoopBe1.

Check the relevant new features section in the help http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.038.html

There is no "Track View Snap Setting." There is a global snap setting which may be overridden in the PRV.

Another option

Another option is midiCurve. It is a VSTi which provides a graphical way to create a velocity curve. Add the plug-in to the project (it scans as a synth), set its input to the controller and enable input echo. midiCurve will show up as the input on the other synth tracks. The original developers page is long gone but 64bit versions of the plug-ins are still available from https://code.google.com/archive/p/pizmidi/downloads The most recent zip is pizjuce_x64_20120111.zip Unzip into a folder in your scan path to install all of the utilities or just copy the midiCurve.dll into the scan path if that is the only one you want.

IIRC, Sony had the same high upgrade pricing. I have used Humble Bundle to upgrade SF a couple of times. Best audio editor at their prices.

If you are trying to purge 32 bit. For 25 it is worth it. SF12 is 64bit too but the scanner bundled with it is a little buggy. The problems I had with the SF12 scanner are fixed in SF13.

Automation can only go in automation lanes, CC may be drawn in automation lanes or the PRV, Keep in mind the DAW converts automation to CC data on the fly and it may be be as accurate as data drawn in the PRV.

I have never seen anyone publish an instrument definition for any Toontrack products. I created one for Superior Drummer 3 and posted it in the instrument definition area of this forum. I found a couple of Toontrack mappings here You may be able to save some typing by looking for drum maps for Reaper. Reaper drum maps are text files which can be easily edited into CbB instrument definitions.

Try the virtual keyboard

No, there was no mention of an interface in the OP. I doubt the choice of CPU has any impact on the interface and vice versa. That said, I do not follow hardware that closely. My last two machines were built by @Jim Roseberry. I rely on his expertise. Every DAW I have ever owned has been Intel-based. I know there are some here using AMD processors.

select the clips and change the length in the clip properties inspector.

What audio interface will this machine be using?

Often it is possible to see the current documentation by setting the product in the url to Cakewalk like this https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=SoftSynths.06.html

BandLab needs to rebuild the rollback installer.

When the process officially changes the documentation will be updated

Links to rollback installers are in release announcements

Could this be what you are looking for http://www.cakewalk.com/Documentation?product=Cakewalk&language=2&help=0x1894E