(EDITED) Discussion was held about the timing of runs and it was decided that time starts on the first totally black frame after the title screen, and ends on the first totally black frame after defeating Master. This has been updated in the categories ruleset and runs are being double-checked for time to account for this. I had previously used this criterion for Sacrieon's former any% WR but somehow forgot to mark it to future-me, so past-me apologises to you for the upheaval :P

Thanks for the info, petaQ. I was really lost about the starting frame situation.

Just to explain my numbers: I saw the rules state that "Timer starts at the first input on the title screen [...]", but there was no information there about when this input happens.

Sorry, I should've asked before submitting. Since I didn't know what to use for frame 0 (zero), I took the first visual indication that shows the game started: the first frame the title screen starts the fade (four frames before title screen goes full black). This was my frame 0 (zero). With that, I got the following times:

• [All Bosses] 10:27.183 - 37631 frames
• [Any%] 5:37.700 - 20262 frames

But now that I know frame 0 (zero) is seven frames before the first fade (frame 7 = full black screen, correct?), I did a new frame check, and got these new values:

• [All Bosses] 10:27.233 - 37634 frames
• [Any%] 5:37.750 - 20265 frames

Since my new values aren't even a frame away from your numbers, can I assume they are correct? If yes, I'm going to fix my thumbnail and video title with them.

Thanks for putting time in checking and making adjustments.

(EDITED) Hiya! Mm, I've had a number of games before where I'd noticed a language gap between 'first input', 'title screen fade' etc, so I like to add the firm data. Your initial numbers based on what was written were totally correct when I used https://slashinfty.github.io/yt-frame-timer/ with 60fps timing. I've experienced confusion when green as a runner/mod before with video/console timing so I'm glad we can post and share information to help future runners!

The golden rule is, if a run is uploaded at 60fps, you are only retiming it in a divisor of 60.

Doesn't matter if it's emulator or console, the video output is what determines divisor. If you go to somewes.com/frame-count/ you'll see a conversion where you can get 'video time' based on this or 30fps, and 'console time' based on presets that interpolates the necessary data based on console vsync. Because you've kindly put framecounter on in your run, and submitted a 60fps clean recording with no frame drops, I can use the actual frames data from Bizhawk to accurately retime based on vsync. For SMS it's 59.922751013551. That means we avoid the situation where a run is timed at 60fps and winds up half a frame off another in future. He said, still sore about his 5:50.000 any% :')

Your retimes are the frame count which was calculated from a framerate of 59.922751013551, but divides by 60, that's the common error that comes up with this.