Promidi

There are many variants of MP4 files. Maybe this is just one of those variants that Cakewalk can’t deal with properly. One thing you might want to try is to use a video converter to recode the resultant MP4 file after the rip. Another possibility is that the MP4 might have a variable bit rate. If that's the case, try converting the MP4 to a constant bit rate rather than variable.

Have you tried uninstalling and reinstalling Melodyne?

Which version (numerically) and which iteration of Melodyne do you have?

http://acronymsandslang.com/RFK-meaning.html

I believe you might get what you are asking by inserting an Cakewalk FX Velocity in the Effects Rack of the MIDI track that your midi keyboard is triggering. With this you can set the resultant velocity to any value. All notes sounded will be that value - regardless of actual velocity played. Of course there are many other things you can do with Cakewalk FX Velocity, but I'll leave you to explorer those.

Sounds like your mouse might need replacing. Or maybe see if changing some settings in mouse properties might help Start + Run (or Winkey + “R”) > main.cpl As regards deleting the markers, this would have the net effect of deselecting everything. If you’re ok with this, then you could keybind a single key press to “Select None”. Personally, I have actually set “Q” as a key binding for this.

What driver mode are you using? (ASIO is preferred). What is your buffer size?

One issue I had with a previous version of UVI Workstation is it would not remember the last opened patch folder for Gospelmusician's Bluebeast. Now it does. I think this issue was resolved a few updates back. I am now on UVI Workstation 3.0.22. It would be nice if UVI told us which actual issues were introduced, and then subsequently resolved.

Oh ok.

Wouldn’t this prevent you from activating Cakewalk by Bandlab - forcing it into demo mode? (Unless you no longer wish to use Cakewalk by Bandlab)

Or download directly from UVI (for some places, this is faster than UVI Portal) https://www.uvi.net/dwl.php?p=pc-x64

Maybe try Paste into existing clips (In the paste dialogue box).

Is there any compelling reason you changed the driver letter from D to F. Personally, I would change your driv letter to back to D as there are probably lots of processes and application that expect a D drive to be present.

It was included in Platinum's Boutique Suite

A question to ask the CbB developers.

Maybe try a lower sample rate (44.1 or 48 Khz) with a higher buffer size (say around 256) If you still have issues, then you might want to get in touch with Amplesound sound support. If Sampletank 4 works fine, then your PC should be able to handle Amplesound products.

What audio interface are you using and what parameters are you using it with? (driver mode, sample rate, bit depth and sample buffer size) Is your Windows 10 fully patched? Are all of your hardware driver confirmed as being the latest? (check this using manufacturer's websites rather than Windows updates)

I am assuming you mean you plan on downloading and installing Cakewalk by Bandlab. In answer to your question as to whether you should update your Windows OS. Yes, absolutely you should update your Windows OS. Also you should enable Windows updates to stay up to date. Same goes for Cakewalk by Bandlab. You can only really say “If it ain’t broke don’t fix it” if you are a developer of said software and have deep knowledge of the source code.

Update. I have been told that CW support have now been able to replicate this issue and a fix will be available in the next update.

Hi people I have CbB 2021.4 Build 175 with a PC as per my signature. Many of my projects have multiple tempo changes throughout the project that differ from the initial tempo. I have found that if I nudge MIDI events by absolute time (like 2000 milliseconds) at various points in the project, the Event moves by the same absolute time amount - even if its original position is after a tempo change. That is, if I nudge a MIDI Note that occurs after a tempo change, the MIDI Note is moved only taking into account the initial tempo, not the current tempo. This issue does not occur in 2021.1 Build 98 I have lodged a ticket with CbB support and they claim they cannot replicate the issue (I even sent them a video specifically showing the issue) CbB Support can now replicate this issue. I am wondering if someone with CbB 2021.4 Build 175 can do a quick test of this for me. I have created a file that can be used to demonstrate this issue. There are two notes therein. Nudging each note by 2 seconds should move the note by a different amount because of the tempo change between the notes. https://drive.google.com/file/d/11N1Swz_K56woWIppFd_WhJghlCToOiXL/view?usp=sharing

Please allow a mantissa in the menu item process > slide command to allow values like 2.75 seconds. Alternatively, allow milliseconds as the units much like you can with the nudge command.

You can also select the notes you wish to "tilt" the velocities. Then, while holding CTRL, adjust the velocity of the start or end note of the selection.

MIDI in to ST4 Max 4.14 standalone works fine here (PC configuration as signature)

Even with this downside, I still use CAL scripts for many things in CbB. Makes my MIDI sequencing so much easier and light years quicker.... In fact if the bakers ever drop support for CAL totally (though I don’t ever think that will happen), I would stay with the last version that supported it. Same goes for Studioware panels.

See: https://help.cakewalk.com/hc/en-us/articles/360022063794-I-see-a-white-screen-when-launching-BandLab-Assistant