Promidi

What are your full PC specs?

Personally I treat keybindings as global - regardless of loaded workspace. Any custom workspace I use, I disable its ability the save or retrieve Keybindings from those workspaces.

I have way too many custom keybindings to restore mine from scratch.

Maybe drop a note Cakewalk support here: https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

What happens if you rename the TTSSEQ.ini, AUD,ini and Cakewalk.ini files and then start Cakewalk? You might want to do the TTSSEQ.ini file first to see if it’s that. These files are in the following folders %AppData%\Cakewalk\Cakewalk Core\ You might want to uninstall the RTPMidi plugin first.

You don’t really give us much to go on... That being said, I use IK stuff all the time and I do not get crashes. I am assuming you have updated your IKM plugins to their respective latest versions. Also, try the VST2 variants The fact that IK plugins are also crashing Cubase 11 Pro indicates its not a Cakewalk issue (and Cakewalk support will probably tell you that). I am assuming you have also contacted IKM Support.

My answer is the same.

I just tried Shift+Z and that worked here.(I have already bound Shift+F to another function) Sometimes when I have found keybindings that don't work, I have to resort to a technical solution that if I make a mistake, it could ruin my entire keybinding setup. I think this issue is caused by double-ups in the internal keybinding database. When a keybinding doesn't work, I first bind the offending keybinding to a CAL script (one with an easy name to remember) Then I export my bindings to two KBN files (so you have a unaltered copy for Justin) - these are normal text file. I then open one of the KBN file with a normal text editor and look for the instance of some of the text in the CAL Script name I used. There will be a number starting with Kx bound to the CAL script....... search for other instances of that same KX number. If they exist, then those are probably the duplicates causing the issue. Delete these lines so that the only one left is the one bound to the CAL script. Then reimport the KBN file that you just edited into CbB. Leave the unedited KBN file in case you need it later. Then do your originally intended key binding (SHIFT+F to “Resize and zoom.....”) There have been many times this has worked for me when I create a Key-binding that has not worked. If your keybinding are borked after doing this you can always import the second, unaltered, KBN file to CbB. Note: I offer the same level of warning here that I would offer when editing the registry - only do the above if you know exactly what you are doing.

I just tried all the here and it worked fine.... (my CbB version is as per signature) Maybe drop a note Cakewalk support here: https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

The location your red arrow is pointing to is only the initial patch that the MIDI track is set to. Any subsequent patch changes do not change this displayed value. Maybe put in a feature request to display the most recent patch change for a given track - I am thinking the PRV would be a good place to display this. https://discuss.cakewalk.com/index.php?/forum/8-feedback-loop/

I never wait for the email. I go straight to my account (with any vendor)

When it's ready.

Only the feature (12 monthly) Windows Updates that have this issue. The Patch Tuesday Windows Updates do not have this issue (At least, not on my rig).

It's VST2. Though that's not going to stop me buy buying VST2 pluigns... It will be ages until CbB drops VST2 support.

This appears when the local echo is on due to MIDI track being active and the setting "Always Echo Current MIDI Track" being enabled in Preferences | MIDI | Playback and Recording. See: http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x22B0A (CTRL + F > "Always Echo Current MIDI Track.")

I have had precisely zero issues installing any spitfire libraries... they just work.

Yes. It's called a restore from a full backup - preferably a back that was taken daily. It could also mean restore from an image of your system disk - preferably an image that was taken regularly.

The commands you entered appear to be correct I did a test and the destination and the link worked correctly. Does the folder D:\Cakewalk Content" actually exist and does it contain the files that were in C:\Cakewalk Content"? Also, does the folder C:\Cakewalk Content" exist and does it point to the contents of D:\Cakewalk Content"? If you open both "D:\Cakewalk Content" and "D:\Cakewalk Content" (side by Side) and rename a file in D:\Cakewalk Content", does the change also get mirrored in "C:\Cakewalk Content"?

Usually Volume is controlled by CC7 - so you can start with looking for those events - either using the PRV or the event list view. Sometimes CC11 is used as well..... but CC7 would usually override that.

I'm not talking about pitch bend, I'm talking about controllers.... you know..... CC7 > Volume, CC10 > Pan, etc With most VST and VSTi plugins, controller numbers can be mapped to any parameter - hence my request for the ability to rename them as they appear in the PRV Track pane. See the following link to see where I mean. (The area bound by D and F and what G is pointing to) http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x200C6

Title says it all. Currently, these names are derived from the “Standard” entry in Preferences | MIDI | Instruments. > Define. While that is a a great start, they are global - in that the same set of names appear regardless of what vsti one is using. We either need a way to define them on a per VSTi basis, or rename them as they appear in the PRV Track pane.

Something CAL scripts excels at.....

Exactly what command did you enter in your attempt to create your symbolic link? It would have started with you opening the command line, with Start+ Run > CMD You may have used the CD \.... something command to navigate to a folder. Then you would have entered "mklink > something

Netframes are all up to date, in fact was just updated this morning. Vdist runtimes are all up to date. 2022 X64 14.31.31103 Win10 Defender is disabled. I use Malwarebytes 4 Premium with all CbB program and data folders excluded.

You mean 102 don’t you?