Promidi

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?

Oh ok.

It was not showing up on my PC either - so I opted to install it manually. Of course this was after I made sure my PC was not affect by any of the known show stoppers. When I did the installation, I disabled any real time malware (I use Malwarebytes Premium) scanners as this has been known to interfere with the process. Also, you might want to fully patch and update all drivers (via manufacturer's websites, not via Windows update ) for your Windows 10 before commencing. Taking an image of your system drive before commencing would be prudent as well. Good luck.

If you're not a programmer then you will probably have to contact the vendor to see if they have made a 64bit version. Rewriting a DLL would normally require the source code to do it reliably - something very few companies would be willing to give up.

First thing I would be checking is the sample rate of your project in Cakewalk. Make sure it matches the sample rate in audacity Settle on a sample rate that you would like to use and then make sure that you use that in all programs (Including Windows itself)

Preferences | Audio | Playback and Recording > select "Suspend Audio Engine When Cakewalk Is Not in Focus." See: (CTRL + F search for "sus") http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x22B19

While I do not have CM Motormix, and I may be way off on this. My totally off the planet, uneducated guess is that possibly the "MotorMix.dll" file is 32 bit.