Promidi

1) No there isn't 2) Even though CC10 is the GM/XG MIDI default for Pan, not all VSTis follow that standard. If you want CC10 to control pan for a given VSTi and it isn't, then you might be able to use the VSTi's MIDI learn function to map CC10 to Pan.

Do you have any look-a-head plugins on that audio track? When you put the audio track back and then disable all effects, does the latency go away.. If so, then it's a plugin.

IMHO 64bit is way overkill. Hell, even 32bit is almost overkill....

Me too. This could actually be a game changer in the same way the arranger tool is. In fact, I would actually be willing to BETA test this.

At the end of the day, you might find it easer to simply pony up the cash for a replacement USB to MIDI adapter. The one I use is a Roland Roland UM-ONE mk2 USB MIDI Interface. This is a little more expensive than the cheap ones you find of Ebay. However, the cheap ones tend to have small internal buffers that cause them to have issues with a high data density (like sysex).

The only other thing I can think of is that your screensets are locked. If it's not that, then I am out of ideas. I use screensets all the time in my projects and screensets always save ok for me. Maybe drop a note to Cakewalk support. https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

Are you using version 2020.9 Build 006 of Cakewalk by Bandlab?

Are you using the latest Cakewalk by Bandlab (Which is 2020.9 Build 006)? On the latest versions, see if deselecting "Apply Workspaces on project Load" makes a difference (I can't remember when this was introduced). See if deselecting the option "Windows Layouts" under "load from Workspace" in Workspace Manager for any used Workspaces makes a difference..

I also have that library and I am pretty sure that this library does not respond to Pitch bend MIDI events..

I also have deeply customised my bindings and I have never encountered this issue. Are you using Workspaces by any chance? I do, and for all of the ones I use, I deselect the option "Keyboard Shortcuts" under "load from Workspace" in Workspace Manager.

You still could be looking at a hardware problem of some kind. Perhaps only Cakewalk is using the PC in such a way as to make the issue manifest. Maybe do a stress test of some kind - although, even that might not make it fault Earlier this year, I had an issue where my DAW PC would mysteriously reboot (I have set my BIOS to go to last state on resumption from power loss). Sometimes the only way I knew it did this were various kernel power events in the system logs. Then one day, out of the blue, while running "Space Engine" (A resource hog), the PC just shut down and would not come back up. That ended up being the power supply. Replaced it with a Corsair Corsair RM-750x. So far, no reboots. I know you probably don't have spare power supplies in your back pocket..... but, if you're able, see if you can replace the power supply.

If by "computer sometimes shuts down" you mean the PC switches off for no reason as if you've pulled the power, then the first thing to check are your PC's fans in your GPU and your CPU are actually spinning or are not clogged with dust. Excessively high temperatures can cause this. This will require taking thing the cover off. It could also indicate a problem with your power supply. The less likely cause is a faulty motherboard If you're not comfortable with any of that, then you might need to take your PC to a professional. If you mean that Cakewalk drops you back to the desktop, then that's likely to be a plugin causing this.

Yes, I use those every day in my MIDI sequencing workflow - many CALS I have written myself. In fact, I would be lost without them. I also have screensets that include Studioware panels (that are riddled with CAL scripts) strategically positioned in the work area for ease of access.

What I would love the ability to do is assign CAL scripts to menu items and toolbar buttons. At the moment, we have to use Studioware panels. It's really a shame that, officially, CAL scripts (and Studioware panels) were depreciated... Modernising CAL scripts and being able edit Studioware panels within CbB would take CbB to a whole different level. Nothing, and I mean nothing, would be able to touch CbB for versatility if they did.

Just reply to the email they would have sent you, letting them know to cancel the request and that the ticket can be deemed closed.

I think you've got it. I added a SIT with MIDImonitor. played around with offset mode - I was able to replicate the OP's issue exactly.

A SIT is a "Simple Instrument Track". That is, it has all the component tracks (MIDI, VSTi, Audio) combined into one track with all the routing correctly set so you can just put MIDI into the track and it is heard as the track is played. If you save the problem track as a Track Template and then load that Track Template in a blank project, does it happen then? To be brutally honest and frank, I am actually stumped with your issue as, in the 25 years of using Cakewalk, I have never come across this particular issue. Moving any volume slider in any console has always given me the full range (0 to 127). I am assuming you're using Cakewalk by Bandlab 2020.9 Build 006. Maybe drop a note to Cakewalk support with a copy of a project where this issue manifests. If possible, You might want to strip the project down so that it contains just the problem track (as long as that track manifests the issue). https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

What happens if you add a single SIT using MIDImonitor as the VSTi? I did just that here and when I moved the volume slider of the MIDI track inspector, I get the range between 0 and 127 on CC7 (as expected) The only difference here is that I am using the 64 bit version of MIDImonitor where as you appear to be using the 32 bit version - but that shouldn't make a difference in the actual MIDI data. Could be an issue with that particular project. What that issue is, I couldn't say.

Any chance of a screenshot that shows the inspector for the tracks?

Which version of Cakewalk are you using (The latest is 2020.9 build 006) Are you entering a VSTi as a Simple instrument - i.e. A vsti that has a MIDI track properly routed to the VSTi which in turn is properly routed to an audio track

A simple VSTi that sends MIDI Thru is MIDI monitor from Snoize. You can also use this for diagnosing MIDI issues. Version 1.4 is only for Mac. However version is 1.3 has a windows version. https://www.snoize.com/MIDIMonitor/MIDIMonitor_1_3.zip For more information, see: https://www.snoize.com/MIDIMonitor/

There are many things, however, that can only really be accomplished with CAL scripts (or much more efficiently anyway)

Requires NI Kontakt 5.5, does not work with Kontakt Player.

This is looking more likely you have PC issues that is causeing Cakewalk by Bandlab not to install I have never once had an issue installing and running Cakewalk by Bandlab Is the Cakewalk by Bandlab installer still in the following folder? %appdata%\bandlab-assistant\Downloads

Is it possible that you have added a plugin that triggers the "changes" count?. Have you tried turn off the saves after changes (by setting the count value to zero) and setting the timer to a lower value?