I'll have to do some more testing on windows, to see if there's something going on with how Windows is processing the incoming radius values.
From my testing on Mac OS, if the chain selector moved to the area corresponding to a different sample, it played the appropriate sample.
The only way I could get it to NOT play the sample at the radius value reported in Live is if I VERY lightly pressed the playing surface. I was able to get the radius value to visibly 'slide'. But if I hit the playing surface with any amount of force the radius value and note message would come in at the same time, and trigger the appropriate sample.