It is already published, but only to see it, I made a MKV. We just want to show them to publishers if this perfect MediaFire Thanks

It is already published, but only to see it, I made a MKV. We just want to show them to publishers if this perfect MediaFire Thanks

Hi! I have two minor problems with the encode: 1) The aspect ratio setting isn't present (a must for runs for consoles intended to be displayed on TVs) - when using mkvmerge please specify --aspect-ratio 4:3, or you can fix the present encode with mkvpropedit <filename> --edit track:v1 --set display-width=298 (where 298 is the appropriate width, 4:3 times the height). 2) Your subtitles obscure the action considerably. If you compare to the published encode you will notice that the subtitles are displayed at the top of the screen instead of the bottom; if you're using mencoder for your encodes you can set this with -subalign 0 -subpos 0. Apart from that, it is noticeably larger than Flygon's published encode (then again, Flygon is an experienced enough encoder that he is probably using additional techniques above and beyond what the guides are showing). I would encourage you to keep the above in mind and either try another encode for this run or perhaps encode something else (one of the other runs in the queue, for example, or something on our Unmirrored Movies lists).

Apart from that, it is noticeably larger than Flygon's published encode (then again, Flygon is an experienced enough encoder that he is probably using additional techniques above and beyond what the guides are showing).

Regarding that, this, along with Super Mario Land are probably the most optimized movies on the site (Disregarding any shenanigans I just know Aktan will pull), video stream wise... I just made them because I had a very powerful computer on me at the time. Generally, the script used is almost never used due to how darn slow it is. For the curious, you can see it below:

start /wait x264 "mixed.avi" --stats "./bothumh.stats" --deldup 15 --versioninfo --ssim --crf 0 --keyint 600 --ref 16 --mixed-refs --no-fast-pskip --bframes 16 --b-adapt 2 --mbtree --weightb --direct auto --subme 10 --trellis 2 --partitions all --me tesa --merange 256 --threads 4 --8x8dct --no-dct-decimate --output "encodedboth.mp4"

The key point to note here is the merange is pretty much as large as the largest of either the vertical or horizontal resolution of the video (In this case, horizontal being the biggest at 256 pixels)... which absolutely blows the normal maximum merange used for video encodes on the site out of the water (Normally, it goes up to 64), but because using such a range could be grouped under CPU murder, I really wouldn't suggest doing so unless you have a Quad Core CPU (Or... basically any CPU that's reasonably modern). The keyint are also maximized to the safest maximum, and the same going for the deldup being at it's bare minimum which I'd consider safe (Even then, I've seen VLC freak out at just around 20). It's also worth noting that movies will normally have a crf value between 18 to 23... 0 basically means lossless, this is due to how simplistic the movies were. Anyway, I'll finish off this hugeass post by admitting that Aktan will correct some of my possibly incorrect facts, but feel free to contact me if you wish to get some encoding help. This is also motivational fodder for me to finish up writing the Flygons Guide to Encoding Oh, before I forget, this page is pretty helpful.

According to Movie Class Guidelines and Publisher Guidelines, this movie should be classified as a concept/demotration of unusual goal choice (to game over with a texture pattern).

TODO: replace the screenshot with the one that doesn't disclose everything...