Promidi

This will be available in the next pubic update. This is available now in the CbB 2021.6 Early Release Build 41

Usually the reason most PCs will not run Windows 11 (it it's current form) is lack of Trusted Platform Module version 2.0. (it's also been stated that by the time the public release comes around TPM 1.2 will be the minimum requirement)

Just save it as a project template.....

Sometimes VST2 works best, sometimes VST3 works best. It depends on the plugin. For that reason, I like to install both. Note: The VST DLL and VST3 files themselves take up very little space. If you are concerned about the space they occupy, time for a hard drive upgrade I think.

Contact Bandlab support https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

Preferences | Audio | Playback and Recording > deselect “Suspend Audio Engine When Cakewalk Is Not in Focus” Also, I think for your discord viewers to hear your Cakewalk audio, you need to use a driver mode other than ASIO (I belive it’s WASAPI Shared).

I just tested it here with Sampletank 4 MAX using the Patch “Full Strings Multi” (A patch that has key switched articulations) I created a sustain chord on one measure and a set of staccato notes on the next measure. I used an articulation map to perform the key switching between measures and it worked fine here. This is with the CbB 2021.6 Early Release Build 32 What happens if you right click in the articulation track and select “Edit articulation map”?

I would not be so quick to write off support. There have been some specific bugs in Cakewalk by Bandlab that I have reported to Cakewalk support that have ended up being fixed in subsequent updates. One such bug fix even made it into the 2021.6 early release.

Yeah, but we are dealing with Cakewalk developers. Let me know what happens if you ever need to contact Cakewalk support and you disclose to them that you're still on an unsupported OS. Ok, they will probably still accommodate you (because that's how I think they roll) , but you’ll probably still get the lecture....

Well the benefits of Windows 10 do outweigh the issues. Besides, what do you think Microsoft will tell the Cakewalk developers if the Cakewalk developers needed support from Microsoft for an unsupported operating system. This is why the Cakewalk developers say that, even though Cakewalk by Bandlab will technically run on Windows 7 and 8, Cakewalk by Bandlab is no longer supported on anything less than Windows 10. Something to consider if you are still run on an unsupported operating system.

The last time I had an issue with a Windows 10 update was back in 2016 with a modified PCR-800 driver. And that was easily fixed by reinstalling said modified driver. I am on 20H2 (I have not been offered 21H1 as yet) All other times, for me, Windows 10 updates (feature and quality) have gone smoothly....

Can you post the KB number of the specific update that you believed caused the issue?

Probably going to need more information. Are you using the latest BBC symphony orchestra? Which version of Cakewalk? (Numerically) What are your PC specs? OS, Audio interface, Sample Rate, Bit Depth, Buffer Size?

I wonder if this is because the feature update reinstalled a generic display driver. Did you try reinstalling your display drivers prior to rolling back to 20H2 (or whatever you had before)? Remember, feature updates ignore the group policy settings to tell Microsoft to ignore drivers. I am sure other users have updated to 21H1 where this has not happened.

I've noticed that when one opens a project and that project opens further along in the timeline (say at measure 100), tempo inspector is still displaying the changes starting from the first tempo change (at measure 1). Also, scrolling along the timeline in your project does not move the tempo inspector to match. Is it possible we can have a setting to enable the tempo inspector to optionally follow the scrolling in the project track view. Also, it is possible for the tempo inspector to highlight (using a lighter grey or a colour) the current tempo change (which would also move through the tempo changed upon playback).

Personally, I would just write a CAL script to do this...

More your Now to where you want your starting point to be. I think opening a MIDI file, this is at the start. Enable the following in the track view menu: Options “On stop, Rewind to Now Marker” “Stop at Project End”

Yeah, I have reassigned many of my key bindings. The point is, that marker navigation can be assigned to any key combination.

What I have done is created keybindings in the Area: Global for Previous Marker and Next Marker. My Keyboard shortcuts are Ctrl+Left and Ctrl+Right respectively. Of course, being in Area: Global, these will work on any screen.

Title says it all......

This is why I still use the Yamaha SW1000XG (in another PC connected via USB to MIDI)..... no VST can touch it (probably never will)...

Yes. With the smart tool selected, right drag a rectangle around the notes you want to change, then do the Process | Length

One way I can think is to selected the notes you wish to change, then go Process | Length, and reduce just the durations by 50%

You wouldn’t have Ripple Edit enabled would you?

Do you have KB5003214 installed by any chance? Windows Update history may not display the knowledge base number Start + Run > appwiz.cpl View installed updates > scroll down to “Microsoft Windows”