Timing in milliseconds
5 years ago
United Kingdom

There's quite a few times that are tied to the second, but I imagine that they're not tied down to the millisecond. I think future runs should be timed in millisecond and perhaps retime the top two 100 Lines runs to see who really is first place.

Massachusetts, USA

I don't have a problem with it, but it's a lot of work for someone to go through and retime all the runs. I'm not sure how many people care if it's down to the millisecond, unless there is a tie at the top. I certainly don't, but I'm not against it either.

Minnesota, USA

The other mods can chime in if they want, but until recently there wasn’t a big need for such precise timing. While the board has grown (a good thing!) I’m not sure if millisecond timing is necessary yet.

As someone who verifies a lot of the runs; including occasionally having to frame count to verify times without a time or inadvertent early/late splits, I see several issues with this.

  1. Like justinman said, you’d have to retime runs which is big commitment since you would need to frame count the vods to verify the precise timing. Even if you said only count those times under a threshold, it would still require determining an arbitrary threshold to have those runs frame counted.

  2. All future runs would need to be frame counted as well. This would drastically slow down the verification process. Currently, the mods can verify runs fairly quickly. However, if we have to download VODs, watch, then frame count each run, chances are verification will be much slower. I am certainly not opposed to this in theory, but would want the majority of the community at least to be supportive of this change since it would affect everyone that wants to submit new runs.

  3. There is also an issue with VOD availability. Some people link their twitch highlights and others upload to YouTube. Just the process of having to find the VODs and then download them can add work. Additionally, depending on the platform, the VODs will have different FPS. While the NES rate is 60.09, many people can only capture at either 30 or 60 FPS which results in different frame counts. I also believe that YouTube caps its uploads at either 30 or 60 FPS (may be wrong?) Either way this would require another step of equalizing all the frame counts based on a set frame rate, which is not stipulated in the current rules.

TheJayJay and Neural89 like this
United Kingdom

Completely understandable, thanks for your input!