When asked about how retiming runs worked I was told to make a forum post, so here it is!
Current runs between WH and myself are within .01, from my timing I'm ahead by a bit over .01; framecounting may be needed. Above are images showing the timing changes based on our split timing. Very close!
So... frame counting, my time is 23,372 frames. WH's is 23,372 or 23,373 frames -- I think on the very last frame of my run you can see a pixel of Sabretooth at the bottom, but that may be an artifact done via the video capturing.
This may be an actual to-the-frame tie which is quite possibly the coolest thing that could ever happen.
It's difficult to determine since both of your frame rates are different, and I can't exactly see the time when whitehat's Sabretooth disappears, because he's still in for 1 more pixel in the last frame he dies, for this reason I used a different timing method, took as the point A the moment when the words Level 01 leave the screen, and as point B, the moment when wolverine's face leaves the screen.
Results using avidemux, with THESE points (NOT USING official time rules) Whitehat: 6:31.291 Overswarm: 6:31.300
This sparked my interest when I read about it on the speedrun.com Discord. I hope you don't mind me getting involved.
Here's my very chaotic approach: https://docs.google.com/spreadsheets/d/1Fw2rlDW18ncI7vnP03Tf2-tkaBmyIokCh2sFFEnxDHI/edit?usp=sharing
Let me know if I missed something.
Summary:
6:29.926 WhiteHat94 6:29.909 Overswarm
(Note: Interestingly, Sabretooth stays on screen for 1 frame longer with 2 pixels of his face for WhiteHat. My admittedly untrained eye can't detect a missing line in the emulator render of Overswarm's recording, though, so that's for those more familiar with the game to figure out. Taking the rules literally, that seems to give a 1-frame advantage to Overswarm in this case.))
(Note 2: There are several uncertain factors in play here, most prominently, possible encoding artifacts and rounding inaccuracies when calculating the frame count. Without raw video footage there's no point in claiming absolute accuracy.)
(Note 3: @WhiteHat94, seeing that there are 5 moderators for this game, self-verification is probably not the best approach.)
(Note 4: @ViruseReturns, interesting that your findings contravene mine. May I ask how you retrieved the VODs? There are several browser extensions and standalone apps out there that seem to reencode videos while downloading them, e.g. Twitch Leecher, leading to inaccurate timing information)
@Oh_DeeR I think the last pixel of Sabretooth in WhiteHat's video is an artifact -- I thought I had a one frame advantage too at first, but looking closer you can see other artifacts appear on the same frame and the size of the pixels seems off compared to everything else. Unless the resolution of all the sprites in the game was far greater than it appears, I don't think it's possible for those little black spots to be part of Sabretooth.
Not sure about that. In WhiteHat's run, Sabretooth seems to be 1 pixel higher on other respective frames before he disappears, too. I know virtually nothing about NES, though, so I'll leave the deeper analysis to those who know their stuff.
I didn't check the other frames, so that might be the case -- I figured I'd give the benefit of the doubt because I couldn't tell :D
