![]() fps 24000/1001 -preset veryslow -tune animation -open-gop -b-adapt 2 -b-pyramid normal -f -2:0 bitrate 2500 -aq-mode 1 -p 1 -slow-firstpass -stats v.stats -t 2 -no-fast-pskip -cqm flat X264 10-bit encoding settings (pass 1 & pass 2), 2.5Mbit example: -fps 24000/1001 -preset veryslow -tune animation -open-gop -b-adapt 2 -b-pyramid normal -f -2:0 Scenecut=40 / intra_refresh=0 / rc_lookahead=24 / rc=2pass / mbtree=1 / bitrate=28229 / Nr=0 / decimate=1 / interlaced=0 / bluray_compat=1 / constrained_intra=0 / bframes=3 / b_pyramid=1 /ī_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=1 / weightp=1 / keyint=24 / keyint_min=1 / Mixed_ref=1 / me_range=24 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 /įast_pskip=1 / chroma_qp_offset=-2 / threads=12 / lookahead_threads=1 / sliced_threads=0 / slices=4 / Here are the source material encoding settings according to the video stream header: cabac=1 / ref=4 / deblock=1:1:1 / analyse=0x3:0x133 / me=umh / subme=10 / psy=1 / psy_rd=0.40:0.00 / All of this happens automatically, you don’t need to do anything! If your browser doesn’t support WebP (like Firefox, IE, Edge, Safari), it’ll be fed lossless PNG instead. This helps, because my server only has 8Mbit/s upstream. This is done, because at maximum level, WebP does lossless compression much more efficiently, so the pictures are smaller. Since this is all about compression, I chose to serve the large versions of the images in WebP format to all browsers which support it (Opera 11+, Chromium-based Browsers like Chrome, Iron, Vivaldi, the Android Browser or Pale Moon as the only Gecko browser). The screenshots below are losslessly compressed 1920×1080 images. The encoding speed penalty for switching from x264 to x265 at the given settings is around a factor of 8. The mode of operation is 2-pass to aim for comparable file sizes and bitrates. While somewhat “non-standard” for H.264/AVC, this is officially supported by H.265/HEVC for Blu-Ray 4K. Also, both encoders are running in 10-bit color depth mode instead of the common 8-bit, meaning that the internal arithmetic precision is boosted from 8- to 16-bit integers as well. The Blu-Ray source material is H.264/AVC at roughly 28Mbit on average. In this post, I’d like to compare 7 scenes from the highly opulent Anime (言の葉の庭) by (新海 誠) at three different average bitrates, 1Mbit, 2.5Mbit (my current x264 default) and 5Mbit. My goal was to be able to encode 1080p ~24fps videos on an Intel Xeon X5690 hexcore 3.6GHz all-core boost clock at >=1fps for a target bitrate of 2.5Mbit. Thanks to and / I got rid of x265s’ blurring issues, and I took their settings and turned them up to achieve more quality while staying within sane encoding times. So for a newbie it can be quite hard to make x265 perform well without sacrificing far too much CPU power, as x265 is significantly more taxing on the processor than x264. Thing is, I didn’t understand all of the knobs x265 has to offer, and some of the convenient presets of x264 didn’t exist here (like -tune film and -tune animation). but i now want to be able to add a few more things.Recently, after the next generation x265 H.265/HEVC video encoder on Windows, Linux and FreeBSD, I decided to ask for guidance when it comes to compressing Anime (live action will follow at a later time) in the Doom9 forums. I have been using the following for nameing my movies for year.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |