Killer run ggs gamer!

I'd like to chime in and clarify a bit why Avidemux and yt-frame-timer specifically vary in their results, what exactly this means in the context of timing runs, explain a little more about why neither of them are very accurate, and ultimately why Avidemux is the timing method of choice.

yt-frame-timer is a great tool, and would be ideal for our purposes, but is ultimately relying on the frame scrobbling feature youtube provides, which is inaccurate, and can produce varying results even on the same system, in the same browser, during the same session. What this means is the starting or ending frame times can be off anywhere from a few thousandths of a second to multiple frames.

Avidemux on the other hand relies on a local file, so a moderator/reviewer has to extract the video from youtube or twitch. There are ways of doing this and pulling the raw video, but there's a catch (that I'm very surprised hasn't been worked around yet): when we pull the raw video from a youtube stream, the server auto-selects the video quality. Unfortunately the videos that are pulled are almost always in 30fps even if it has selected a 1080p instance of the video.

The reason why we've opted for Avidemux is simply because of the inaccuracy of youtube's scrobbling feature, and that the inaccuracies vary wildly. At least with a 30fps video we know each frame is always within +/- .01666s.

I think there's definitely moves that can be made to solve this timing issue, especially in the speedrunning community as a whole. We've tossed around the idea of working on an auto-splitter (which is something I don't really know anything about), and hopefully that would take some of the headache out of timing these.

I hope this helps explain where our heads are at. Please post thoughts, questions, suggestions, ideas, memes -sations

Edit: I also forgot to mention that it seems that the IGT for this game floors the end time, that is it always rounds down to the nearest whole second. Keap has mentioned that the IGT sometimes doesn't reset properly and it's possible there are fluctuations in it's starting/ending frames (which I have yet to reach out to the creator of the game about to ask).