afaik resolution refers to how many steps you have, so a standard 0-127 have 7bit resolution which has 128 values, a high resolution value like pitch bend/nrpn/mod wheel or 14bit has 16k something values so it’s very fine tunable, there’s a reference for this in the EC4 documentation.
IRL example: on AR the sample start/end is an integer number from 0-127, with long samples (30s) when you change from 0 to 1 to 2 to 3 etc, the jumps are very coarse and you cannot “fine tune” the sample start or have a smooth granular effect.
on the DT these values are decimal, so you have ~100 points between 0 and 1, so when you scroll between 0-1 you get smooth transition and you can have smooth granular effect.
same goes for anything that 128 steps is not enough, like filter with high resonance etc.
for some things 128 is more then enough, for example having a mix value in a delay/reverb or send fx.
another example is the offset ratios in the DN, they are very sensitive so adjusting them with 127 values would be terrible, it’s great that DN supports nrpn and I can use smooth value transition on the DN params with decimal values.
there’s another type of smoothness and that’s the encoder acceleration, i.e. how do you want it to react to your physical turn, so you can have faster change when turning faster or no acceleration, these are also controllable with the EC4 which is nice, but personally I leave it on max value as I want consistent feel across the encoders.
every encoder in EC4 supports 14bit and it’s actually relatively easy to set it up directly from the device and not going to software, I like it actually…
btw if the MFT has 3x resolution it would mean that it can support 16383*3=49149 steps which would be insane amount of control over a value but it would take you forever to scroll from 0-49k