The encode scripts we use for HD encodes normally adjust the FPS of the video to 30 fps - the use of 30fps is, of course, a problem in this case, so we usually use another fps value (24-25) in these cases.
Clearly, the encoder forgot to do that in this case.
Yes, that's my fault. This will not happen in future encodes; I am truly sorry.
For some reason Mupen64 crashes during video capture when it reaches a part in the ending credits.
It's possible for me to do an encode leaving the credits out of it but it's prolly easier to let someone else that don't get this crash give it a go.
Same thing happened to me with both the camstudio codec and the lagarith codec.
arflech wrote:
IMO you should produce an encode without the credits, at least for distribution via YouTube.
Point probably is that his account, as well, is just a step away from getting a "strike" stain to it (get three of those, and your account is deleted along with all its videos).
This isn't true. I got about 20 of those (got one on Gradius also) and my account is going just swell.
Thanks to Tompa, the run has been improved by 52 frames due to his work on mainipulation, optimization, and route finding. Can someone please replace the current file with this?
