For a while we've used frame-accurate timing for top times in the SotN community. A while ago we also started removing loads for certain categories to combat performance differences.
I've made this tool to make the process of doing that faster and easier without the need to download anything. But unfortunately the process is not ideal and not precisely accurate.
You can find the tool here: Segmented Timer
And a short video instruction here: How to use the Segmented Timer tool
EDIT: I made an issue request to the youtube team and they responded that they will not adjust their API to increase accuracy of the reported current time. This means that the only way for the timing to be accurate is to request the runner to provide the exact framerate, since they both don't have a visible framerate in their API and even if they did it would be rounded. My desire was for this to replace the need for yt-dl and avidemux, but it seems like it won't happen.
ive been using the Load Remover tool someone in the nsmbw community made but that requires you to have the video on your hard drive so your tool seems nice for removing loads when you dont feel like downloading the video
As a moderator of a game that has upwards to 42 segments just for Any%... holy shit. This will definitely save SO MUCH TIME for me retiming runs. Thank you so much! I look forward to using this! :)
Hope it is helpful, feel free to message me somewhere or submit an issue on github for problems, bugs or feature requests.
Love it, great tool!
I tried it and the only issue I found so far is that I couldn't put the start of the next segment where the previous one ended. -> I was playing around timing the loading times as well.
Thanks for creating this awesome tool!
Oh that is done on purpose, assuming that the segments would be spaced out by at least a frame.
Quick question. The video used in the pic below is in 30 FPS. Why is it that segment doesn't end in 0.X33, 0.X66, or 0.X00 like how SPRT or other retiming tools do?
The current time is taken directly from youtube's information for that frame, so it all depends on how the video is transcoded and timed by them specifically.
EDIT: It seems like the way they track time internally and provide it via API might have some inaccuracy. Will see if I can account for that.
Unfortunately it seems like the time youtube provides with their api is not accurate, so I've had to add a framerate field in order to properly adjust milliseconds. This reduces ease of use but I'm hoping maintains the usability of the tool while being accurate. I didn't expect the api to spit out a fraction that is straight up incorrect.
This is the best retimer I’ve seen so far. Definitely changing my current one to this.