Solving faulty rotary encoder through software

I'm not happy with the prospect of replacing my encoder and having the knob stick that far out, so I'm going to take a different approach and see if the problem is solvable in software.

Mark, could I perhaps bother you to create a version of Hijack that would provide some logging of raw encoder data?

There is already some bounce compensation in Hijack for flaky rotary encoders.

The Button Codes Display shows knob output, but I don't remember how "raw" that data really is --> it certainly comes after the existing extra debounce logic, though.