fix issue when fps and timing differ

[transitive-bullshit]

Hashes produced from perceptually equivalent GIFs currently suffer if the timing and fps of two
GIFs are slightly different, resulting in the first / middle / last frames used for comparison not being close enough to be considered perceptually similar.

We need to figure out a better way of producing hashes that are robust to this kind of attack.