a few extras on this…
resolution = 8192 / N , where N = bend range
(its, 14 bit, so, 16384 is used for bi-polar, so + and -)
ideally, you’d use the longest slide range your controller has…
e.g. if your grid is 24 cells long, then 24 is ideal (?!)
this allows you to slide from any where to any where and it’ll be correct,
and since the 8192 is spread out evenly over your surface, its the highest resolution possible.
BUT we don’t often need to slide the full length of a controller
so really, you can set the pitchbend range to what you want your longest slide to be.
the issue is for very large surfaces, this can become a bit too low-resolution.
this is why Haken introduced (optional) MPE+ , where they use 21bit (using an extra CC) for pitchbend, because they used to have a continuum with 93.50 ‘notes’, and so 14 bit was deemed insufficient.
this actually raises a couple of other related topics…
as mention by others, synths will often ‘slew’ midi values, everyone knows how low res standard midi is, so to avoid stepping synths will glide to values so the quantisation effect is not as obvious.
(this has been done for a long time… well before mpe, even on old hardware synths)
its actually interesting to think about how this ‘resolution’ is compared to physical space e.g. if you have a small surface, or if your sensors are not that accurate - having a ton of resolution isn’t really going to help much. e.g. something else might force ‘quantisation’
microtonal - something like the continuum are sometimes used for microtonal work, here resolution is pretty important, as everything is going to have a pitch bend. same situation with non-12 note scales.
so here the ‘slide range’ aspect is not important…
btw: all the above is for continuous surface, something like an Eigenharp/Striso, where you dont slide, you’d typically use much smaller values (higher resolution) - I quite often use +/-2 on my Eigenharps.
but, as mentioned above, now with MPE defaulting to 48 semis, and synths usually coding these into presets, unfortunately… often we leave it all at 48, simply to not have to update the presets
in some ways, I think perhaps the default should have been +/- 12, enough for most practical purpose - but I guess, they felt some would get confused as to why they couldn’t slide the full length of their surface. so chose a value that this was less likely to happen.
btw2: I should also point out that MPE does have the ability to communicate between controller and software what the pitchbend range is… theoretically bi-directionally. but Ive never seen it really work that well… though I might just be unlucky