![]() $x264 -frames 50 -q0 -m2 -r1 -me hex -no-cabac -quiet -o /dev/null $video $x264 -frames 50 -q0 -m9 -r2 -me hex -Aall -quiet -o /dev/null $video $x264 -crf 18 -b3 -m9 -r5 -me umh -t1 -A all -b-pyramid normal -direct auto -no-fast-pskip -no-mbtree -quiet -o /dev/null $video ![]() $x264 -crf 26 -b4 -m5 -r2 -me hex -cqm jvt -nr 100 -psnr -no-mixed-refs -b-adapt 2 -slice-max-size 1500 -quiet -o /dev/null $video $x264 -crf 16 -b2 -m3 -r3 -me hex -no-8x8dct -direct spatial -no-dct-decimate -t0 -slice-max-mbs 50 -quiet -o /dev/null $video $x264 -crf 30 -b1 -m1 -r1 -me dia -no-cabac -direct temporal -ssim -no-weightb -quiet -o /dev/null $video I used this script, which uses the same encoding settings that x264 uses when building with fprofile (I just added -quiet so as to not pollute the output): I took my amd64 r1360 packages, which were built on my Phenom II desktop, and ran some tests on my MacBook laptop, which has a Core 2 Duo P7550 CPU. So I did some tests as per mc4man's question about the benefits of fprofile on a local build vs. ![]() Feel free to tell me to make my own thread to discuss my x264 builds if you don't want it here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |