Ok, I chose a realy bad game, this was my first TAS complete game (I had alredy done other in the past, but level for level ) I will do another TAS for a better game!
I'm not exactly sure what you are saying there. It seems that you misunderstood what I wrote. I was not talking about the bitrate or bandwidth needed for a video with a large resolution. I was talking about the processing power needed to decode (ie. decompress) a high-resolution H.264 video stream, which AFAIK increases as the video resolution increases (which is why older Pentium 4 computers have hard time playing H.264 videos which have HD resolutions). (OTOH, I don't know if this is only for HD videos which truly have additional image information in them. It might be lighter to decode if the video consists of a small-resolution original material which has simply been scaled up...)
Also take into account that the computing resources required for decoding (ie. playing) an MPEG-4 video is, AFAIK, proportional to the resolution of the video (although I have no idea by which function), and decoding H.264 is a surprisingly heavy operation. Which means, in simpler words, that the larger the resolution of the video, the more CPU power is needed to play it. This can already be seen in HD resolution MPEG-4/H.264 videos, which slower Pentium 4's have a hard time playing in real-time (and even the fastest Pentium 4 struggles to keep up). Not to talk if you were to dramatically increase the resolution even further... Not everybody has a top-of-the-line quad-core computer.
Auto Derive = bluh bluh bluh 512 kbps is way too high for most TAS content and it makes it a weird resolution.
So what I would be interested in is, does Youtube allow for 15 minutes or for 15:59 minutes? They allowed 10:59 before...
And, what I meant by 'isn't worth the effort' is that the encoding settings for, say, a 512*448 to be crunched down enough to be streamed easily while maintaining near lossless quality would take quite a while to encode.
Is it really necessary to store the exact same movie twice there, with the only difference being the container format? It feels a bit like abusing the free service provided by archive.org for something it's not intended for. (Of course if the owners of archive.org are completely ok with this, and have explicitly stated so, then there's obviously no problem.)
It's also worth noting that modern HD encoding is able to forego borders completely, thanks to YouTubes Original encoding mode. Anything with a vertical resolution higher than 1080 pixels will be reencoded at its native resolution for Original mode, no scaling applied.
Theoretically, a 2X scaled MP4 could be hosted on Archive.org, but, put simply, it isn't worth the effort to make a well compressed MP4 that can be streamed simply.
OK, what this run really needs is an alternate encode (not to replace the primary encode) that includes a faint superimposed map that shows the path our twitchy Alucard blazes through the castle.
Wait, why are softsubs unpublishable? I would think the ones using hard subs (i.e. text actually added to the video feed) would be the ones unsuitable for publication. And why would you be changing your encoding style long-term in favor of unpublishable encodings?
Here's an encode using the FCEUX subtitles for commentary, much easier and better looking than softsubs
It has been an informal custom with NES Rygar that the run can be ended when the last boss dies, and the encoder then presses a button after some time to get the ending text.
Is that really all there is to the ending? So if I had spent countless hours playing it on an actual NES back in the day, THAT would have been my reward for all my hard work? Not even "A Winner Is You" or any text? Really, Tecmo? REALLY? (Also, post-publication Yes vote. Air walking is damn broken, like everything else in the run.)
Except that Zelda 1 is one of those stubborn games that doesn't like it when you try to convert to fm2, desyncing due to timing differences caused by taking longer to read the sram or something along those lines...I don't remember what the specifics are, but anyway, the movie doesn't act right. :p
Hmm, I just noticed that the rerecord count is totally screwed. It should really be around 10-12k I think, but I don't know jack about hex-editing so I cant change it.
Viewed it in Firefox and the sound desynced shortly into play. It must've just been my settings if it's worked for other people, so never mind.
Watched it thank to Aktan's encode (mp4 encode sound seems off, btw).