Hello everyone, about a month since I started to speedrun, and I ran into the problem that all the runs are counted differently, the counting starts with pressing the start button, then from the first frame of the game, then generally from a random frame after the start)) and WR in the category of 20,000 points it is not at all clear by what logic it was counted there, how there cannot be such a time. The rules say that "Timer starts when you press start (A) to play, and ends the exact frame you get 20,000 points." and, accordingly, each category has its own number of points. I propose to recount all runs according to the same system, which is specified in the rules, and accordingly, start the countdown by pressing the start button and end with the frame where the required number of points is scored, if you do not have the ability or desire to recount all runs in all categories, then I can do this. ... Many thanks in advance for your understanding.

Привет всем, возле месяца как я начал бегать, и столкнулся с проблемой, что все пробеги посчитаны по разному, подсчет то начинается с нажатия кнопки старт то с первого фрейма игры то вообще с рандомного фрейма после старта)) а WR в категории 20000 очков вообще не понятно по какой логике посчитан там не как не может быть такое время. В правилах написано что "Timer starts when you press start(A) to play, and ends the exact frame you get 20,000 points." и соответственно для каждой категории свое количество очков. Предлагаю пересчитать все runs по одинаковой системе, которая указана в правилах, а соответственно начинать отсчет с нажатия кнопки старт и заканчивать с фреймом где набирается нужное количество очков, если у вас нет возможности или желания пересчитывать все runs во всех категориях, то этим могу заняться я. Заранее всем большое спасибо за понимание.

Which specific runs are you suspecting?
I use the following rules to verify.
- The video is downloaded locally on third-party service or recorded locally with OBS.
- The counting starts the frame of pushing start-button on 30fps.
- If the video is 60fps, the counting starts modified frame (the really appropriate way to modify it is currently not well understood).
- The counting ends the first frame of exceeding 20k pts.(Same for the other categories)
I have rejudged once the top 3 runs (except HosteL's new run).

For the 20k category in particular, I figure that they are already in a frame-by-frame battle. So recording at a lower frame rate is a bit more advantageous.
Therefore, unifying the start frame independent of fps is an important concern. However, due to differences in recording methods and video submission destinations, I have yet to get a way to successfully unify these. If you have any good ideas, could you please let me know?
Re-measuring all submissions will be difficult for me to do alone, so I will need your help.

Usually they do this, download videos at 30 fps for the first 5 places to accurately measure the video, and the rest are already checked as they are. And you can do this to start the countdown, everything is correct, you need to take a frame with a start button for 30 fps and for 60 fps the first modified one, so we will equalize the difference at the beginning, since we know that at 30 it will not be fixed, but for the end of the video you can find an identical piece video for all races (in our case, you can use the inscription on the screen when it appears on the screen, it hangs a certain number of frames) and already on it you can watch which frame was recorded at 30 fps, it works like this 30 fps writes like this 1-2-3-4-5-6 and 60 fps so 1-1a-2-2a -3-3a-4-4a-5-5a-6-6a, if we know by the same piece of video that a frame was recorded at 30 fps, let's say 3a, then we find out that all the next frames will go with a letter like this 3a-4a-5a-6a from this we conclude that the second part of the frame was recorded and therefore we need to subtract one frame from the video since he jumped it, but if frames without a letter are recorded so 3-4-5-6, then there will be an accurate calculation in comparison with 60 fps. Here are two ways you can help drop the countdown for everyone.

And at the expense of examples of incorrect counting, it is not necessary to go far WR in the 20,000 points category, judging by the inscriptions here it is 20,000 points 1m 06s 036ms by NutritiousNES, it is not clear how it was received, probably without any verification, in fact, there is generally 1m 06s 503ms and further you can there to start measuring different moderators took different shots. Some early ones are not converted to the 0m 00s 000ms format, which would also be desirable.

And on the account of help, I am always ready to help as soon as we come to an agreement on the counting of runs.

I made a storyboard for ease of frame detection)) https://ibb.co/9bkGCZR

Обычно делают так, скачивают видео в 30 fps для первых 5 мест, что бы провести точный замер видео, а остальные уже проверяют как есть. А можно делать так для начала отсчета все правильно нужно брать фрейм с наитием кнопки старт для 30 fps а для 60 fps первый модифицированный так мы выровняем разницу в начале так как мы знаем что в 30 он не зафиксируется, а для конца видео можно найти идентичный кусок видео для всех забегов ( в нашем случае можно использовать надпись на экране при появлении на экране она висит определенное количество фреймов) и уже по нему можно смотреть какой кадр записался в 30 fps, работает это так 30 fps записывает так 1-2-3-4-5-6 а 60 fps так 1-1а-2-2а -3-3а-4-4а-5-5а-6-6а, если мы узнаем по одинаковому куску видео что в 30 fps записался кадр допустим 3а то мы узнаем что все кадры следующие будут идти с буквой вот так 3а-4а-5а-6а из этого мы делаем вывод что записалась вторая часть кадра и по этому надо отнять один фрейм от видео так как он его перескочил, ну а если записываються кадры без буквы так 3-4-5-6 то будет точный подсчет в сравнении 60 fps. Вот два способа которые могут помочь выронить отсчет для всех.

А на счет примеров не правильного подсчета далеко ходит не надо WR в категории 20,000 points он судя надписи тут он составляет 20,000 points 1m 06s 036ms by NutritiousNES , не понятно как его приняли наверное вообще без проверки на самом деле там вообще 1m 06s 503ms и дальше можно там начинать замерять разные модераторы брали разные кадры. Некоторые ранны не приведены к формату 0m 00s 000ms что тоже бы хотелось.

И на счет помощи я всегда готов помочь , как только мы придем к соглашению по подсчету пробежек.

Я сделал раскадровку для удобство определения кадра )) https://ibb.co/9bkGCZR

I understood about half of what you are saying.
But it is difficult to do verifications according to your rule completely. This is because I have too little experience, skills, knowledge, and time. This means that it is impossible to accurately measure the difference between runs recorded at 60 fps and 30fps. Also, randomizing the start time was your another suggestion, but it is hard too. Who can guarantee that the start time I have determined is random?

I re-measured the HosteL's run and the NutritiousNES's run. Hostel's was 1:06.433 and NutritiousNES's was 1:06.470. There may have been an omission of confirmation in the past records.
The HosteL's run was uploaded via Twitch and recorded using OBS as I don't know how to download Twitch video. And the NutritiousNES's run was downloaded from the following URL (https://ja.savefrom.net/1- (youtube-video-downloader.html ). The resolution is low.
The HosteL's run was previously recorded at 60 fps, but this time I recorded it at 30 fps. I think this method will alleviate the frame rate problem considerably.