Hi Alexey,
I don't use jogging with AZ Controller but I use a Contour ShuttlePro device, which is not configured as a Control Surface (just key bindings).
Don't know if that is a factor.
About the faders: The problem I get is always after I move some faders, not before, oddingly.
After that, the issues are:
Repeatedly selecting a track (with X-Touch Compact buttons and "Select Strip") doesn't work immediately after a couple of button presses, instead the former selected track's button (X-Touch) stays lit and the new/actually selected track/strip (X-Touch) lits too but the corresponding track in Cakewalk still shows the former track as selected.
I.e. I have to press the button to select a track twice to get Cakewalk and Controller "in sync".
At this state other buttons (M-16DX controllers) also have to be pushed twice instead of one, e.g. "UI Toggle" and Commands.
I can see in AZ Controllers UI that the first press of a button is not recognized.
The other site of the issue is less obviously because it depends on how fast I move faders (X-Touch) or knobs (M-16DX):
Slow movements "seem" to be o.k. but fast movements (e.g. going from 0.0 to -INF repeatedly) will "snap" (on the controllers) to different values than in Cakewalk, e.g. - 72.8 instead of -INF and - 2.3 instead of 0.0/Unity.
I can imagine that this all is probably pretty difficult to test without the controllers I use but it's really evident compared to CbB 2020.11 and before.
Many thanks for looking into it, AZ Controller is such a fine piece of software, incomparable to any other "DAW - Control Surfaces" combination solutions! It's "The Missing Link"
All the best,
Klaus
