Please provide more information on why you think the current accepted time is incorrect.
I retimed myself and come up with the same result as the mod who verified it. 2:33.930
The start frame is 476 (the first frame where the timer is 400) and the end frame is 9711 (the frame where all sprites are invisible). (9711-463)/60=153.917, which corresponds to console time of 2:33.913.
Using the site, I got 476 as well, but using 3 different programs on my computer they all show 475. Regardless, I still get the same timing for all methods.
The timing of the run is correct as it stands.
I'm convinced that something isn't quite right in your process.
Youtube-dl does not give you a 60FPS video by default. You are aware of that?
Four mods have timed this run plus the two other people in this thread (one being the runner) and all are coming up with the current accepted time. It's possible for the site to have the frames shifted by one but still give you the correct time when the correct starting and ending points are selected.
There's no issue on our end. I'm closing out this discussion.
Any% (NTSC) runs below 4:57.000 must now fulfill additional requirements in order to be verified.
- The run's full session must be included in the submission description.
- For emulator runs below 4:57.000, some form of input display must be visible for the duration of the run. A hand-cam or input
