scook

A drum map or MIDI Event Filter MFX can do this.

There is a screen to add or modify Cakewalk.ini values in preferences Note: by default, Cakewalk.ini is empty so the screen may not contain any values when first opened.

All the clips in a project must be the same sample rate but the bit depth does not have to be the same. The default record bit depth is 16. I set the record bit depth to agree with the audio driver bit depth.

It's not due to the interface hardware, sometimes drivers are communicating between a software mixer and the DAW, these may have an audio driver bit depth higher than 24.

The transport shows the project sample rate and the record bit depth The record bit depth is a global setting and is not stored in the project or project templates.

It is down to your system configuration which is not detailed in the OP. Without knowing anything more about the hw and sw involved a couple of things to do, make sure CbB is not using WASAPI exclusive driver mode verify Windows and CbB are set to the same sample rate

WRT to names: Hardware uses the method described in the links above Software uses a different approach and relies on plug-in manufactures to implement the feature per the VST spec Color is another matter. This is a feature request

This is a feature request for NI. If Kontakt implementing the VST2.1 effGetMidiKeyName opcode, Cakewalk would automatically show the note names supplied by Kontakt. This is how BFD3, Session Drummer 3 and Sitala note names appear next to the Notes pane.

Colors - no Alternate names for notes - yes although drum maps may be a better solution for now Here are a couple of posts about alternate note names for the PRV Notes pane

This means Pendulate, the free synth is also updated. Unlike Generate, AFAIK, the only way to get the updated version of Pendulate is using the promo page again https://www.eventideaudio.com/products/third-party-plug-ins/chaotic-generator/pendulate

Released 27 Apr 2021 From Release Notes Individual plug-ins EQuivocate Punctuate Satturate also updated Installers at https://www.eventideaudio.com/support/downloads

turn off Snap to Grid

The thread subject could be a little more informative. After all, this part of the forum is dedicated to feature and change requests. While waiting for this to be implemented, remember it is possible to add 3rd party editors to the Utilities menu. The process supports adding an accelerator key. The bindings use the initial ALT+U to bring up the Utilities menu and an additional keystroke from the menu item name.

Yes, in all cases, the bottom image or color is from CbB resource files TTSImage.dll or TTSRES.dll, A.K.A. the Mercury theme. The top image or color, if it exists, is read from the theme being edited. Theme files store only the changes to Mercury. AFAIK, the only differences between Tungsten and user themes are its location and file extension.

Global shortcuts work regardless of the active view. Most of the number keys have global bindings. The account in the OP is one reason, I am not a fan of single key shortcuts. That said, AFAIK they have been used in every product Twelve Tone Systems and Cakewalk made. They are part of CbB too. I am not a console view user.

The VST3 spec recommends "C:\Program Files\Common Files\VST3". Most manufacturers use this path and do not offer the ability to install elsewhere. The VST2 spec is silent on the subject. There are several conventions. There is no exact path to provide. As noted above, the only restriction imposed by CbB is the dlls must not be installed under "C:\Program Files\Common Files\VST3". The log created by the reset should indicate whether the plug-ins are being scanned or not and which paths are getting scanned.

I just test both VST2 and VST3 version 3.7.4 of UltraChannel in CbB 2021.04 EA2. Numeric input using the typewriter and numpad both worked OK in EQ values without enabling capture all keystrokes (the keyboard on the right above the plug-in UI). If you have not updated UltraChannel in a while give the latest version a try. The current version (3.7.4) was released in March 2021. One way to get the version number of the plug-in is right-click Eventide at the bottom left of the plug-in UI copy and paste the support info into notepad and look for PluginVersion in the text. Eventide downloads are here https://www.eventideaudio.com/support/downloads

this thread discusses different controls but the solution is the same

Make sure the scan path in preferences has the folders containing the VST2 and VST3 plug-ins. Do not install VST2 plug-in under "C:\Program Files\Common Files\VST3", Files with a .dll extension are not scanned in the VST3 folder. Enable "Scan in Sandbox" and "Generate Scan Logs" in preferences then click the "Reset..." button. The reset will clear the VST inventory and rebuild it based on the scan paths. If the plug-ins are still missing review the scan log.

Just another reminder, this thread is for issues specifically related to 2021.04 EA2. Changes to auto-save and versioning are feature requests. Feature requests do not belong in this thread. There is a dedicated area for feature requests, please post them there. Problems with the current production release should be posted in the current release thread. Problems and questions about other releases should have their own threads created in the appropriate area.

Ditto And not very happy with how AAS handled Tassman either.

The audio scale is zoomed in quite a bit. Refer to the documentation on audio scaling.

Roland does supply a driver for it. See https://www.roland.com/global/products/rubix22/downloads/ As a rule, interfaces with a factory written driver perform better with the factory driver.

BA keeps track of what it has installed. Here is a similar thread

There is a dedicated thread for issues with 2021.04 EA 2 just like there is a dedicated thread for the current production release. It may be a good idea to read the general information about using Early Access releases