There is no need for that as the encodes are variable frame rate and drops 99% of the duplicate frames already.
Actually I have been slacking, sorry about that =p
----
Edit by FractalFusion: Merged two posts.
About hinting, hmm, never noticed this, but since we are using pseudo HTTP-streaming, hinting is not required for it to work on our site.
The range bug existed with RGB input, but even then I think the bug has been fixed.
That Windows 7 is a tricky one. I'm assuming it shows up fine normally in the actual Mupen window, right? I doubt this is the cause, but what GPU (graphic card) do you have? Also, have you tried setting compatibility mode to Windows XP on .kkapture?
About your problem with .kkapture, maybe if you use the right ctrl key to end the capture instead. It may work. What the right ctrl key does is tell .kkapture to shut down and force terminate the application it is capturing and then close capture file gracefully. You would need to alt-tab to another windows first before pressing the right ctrl key as .kkapture only recognizes it then.
Well, I just finished reading the thread and noticed the subtitle file and the suggestion of chapters. I don't see any reason not to add the subtitles, but can someone give me the times for chapters?
What are the rules for making our own encodes or Youtube uploads of a TAS?
You can make your own encode, but in order for it to be used on the publish page, you need to follow the Encoding Guidelines here: http://tasvideos.org/EncoderGuidelines.html
IMO, really you should not choose a set bitrate. Some require more some require less. It will even out. Just set it to a certain CRF and be done with it. On a side note, TASVideos site itself already streams from archive.org to get great quality and full frame rate. It's what the _512kb files we make are for.