Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
2nd July 2009, 01:15 | #1 | Link |
x264 developer
Join Date: Sep 2005
Posts: 8,666
|
x264 defaults changing
A lot of patches are going to be pushed soon. And among other things, the x264 defaults are changing. We will also be adding presets to the CLI interface (but not the library interface).
New defaults (suggestions welcome): --subme 7 --bframes 3 --weightb --8x8dct --ref 3 --mixed-refs --trellis 1 --crf 23 --threads auto --no-psnr --no-ssim Logic behind this change: x264 should be by default High Profile and generate relatively high quality, but not entirely max itself out; it should be a reasonable speed/quality tradeoff. UMH is probably a bit too costly speed-wise to set as the default. Logic behind the CRF: x264 should, by default, encode with a reasonable quality that isn't overkill but isn't low quality. This means a user can generate a good encode simply by doing "x264 inputfile -o outputfile". Also, out of respect to goddess Eris of Discord. The intention here is that you can simply use x264 with defaults and it will give Very Good Results that nobody can complain about. I will announce quality/profile presets soon as well. GUI designers: have fun
__________________
Follow x264 development progress | akupenguin quotes | x264 git status ffmpeg and x264-related consulting/coding contracts | Doom10 Last edited by Dark Shikari; 5th July 2009 at 21:44. |
2nd July 2009, 01:28 | #2 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Now I'm curious. What patches? ^^
Quote:
What about b-adapt 2? Still too slow at 3 b-frames? And what about b-pyramid?
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
|
2nd July 2009, 01:31 | #3 | Link | |
x264 developer
Join Date: Sep 2005
Posts: 8,666
|
Quote:
B-adapt 2 is too slow, it'll be in a slower preset (which will also use me=umh). |
|
2nd July 2009, 03:27 | #6 | Link |
x264aholic
Join Date: Jul 2007
Location: New York
Posts: 1,752
|
It's implied that the old defaults hold true still except where specified up there:
Code:
--partitions <string> Partitions to consider ["p8x8,b8x8,i8x8,i4x4"] - p8x8, p4x4, b8x8, i8x8, i4x4 - none, all
__________________
You can't call your encoding speed slow until you start measuring in seconds per frame. |
2nd July 2009, 05:39 | #8 | Link | ||
Registered User
Join Date: Jan 2002
Location: France
Posts: 2,856
|
Quote:
Quote:
__________________
|
||
2nd July 2009, 06:05 | #9 | Link | |
x264 developer
Join Date: Sep 2005
Posts: 8,666
|
Quote:
If the issue is ever fixed, I'll make it default.x264 (with the changes announced in the presets thread) automatically changes ref to match level as long as you don't force --ref yourself. |
|
2nd July 2009, 06:17 | #10 | Link | |
Registered User
Join Date: Feb 2008
Posts: 733
|
K, so lets go.
Autovaq and open gop will be added ? Quote:
Last edited by juGGaKNot; 2nd July 2009 at 06:19. |
|
2nd July 2009, 07:20 | #13 | Link | |
Registered User
Join Date: Jan 2002
Location: France
Posts: 2,856
|
Quote:
__________________
|
|
2nd July 2009, 08:12 | #16 | Link |
Registered User
Join Date: Aug 2004
Posts: 65
|
I was wondering if you could give quality profiles for both first pass and second pass encoding? I am always confisued about which settings have an effect on each pass and which you can specifiy values for that speed up the first pass encoding but have an effect on second pass. I think that first pass is just to determine the frame types, so I assume that settings that can affect this are ones that must be present in both passes, but things like estimating the motion vectors are not important in the first pass?
Thanks. |
2nd July 2009, 08:52 | #17 | Link |
HDConvertToX author
Join Date: Nov 2003
Location: Cesena,Italy
Posts: 6,552
|
would by handy a "--turbo" switch that will disable/lower some values (subme/ref/...)
so users will be using a standard "slow" profile in two pass mode, BUT simply adding "--turbo" (and not removing other options) to first pass string , will got a huge first pass speed boost (as xvid option) about preset: you surely know x264 better (and a lot!) then me, but you could take a look at HDConvertToX or MeGui profiles in hdc i have build profiles based on your suggestions last one: +1 for crf 21 BHH
__________________
HDConvertToX: your tool for BD backup MultiX264: The quick gui for x264 AutoMen: The Mencoder GUI AutoWebM: supporting WebM/VP8 |
2nd July 2009, 09:24 | #18 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,806
|
I would suggest something like this:
Code:
--crf 22 --aud --ref 3 --mixed-refs --bframes 3 --b-adapt 1 --weightb --direct auto --subme 7 --trellis 1 --partitions all --8x8dct --me umh --threads auto --thread-input --progress --no-psnr --no-ssim
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
2nd July 2009, 09:27 | #19 | Link | ||
Registered User
Join Date: Feb 2008
Posts: 733
|
Quote:
+1 for default profile 3 pass Quote:
Why is --no-mixed-refs replaces --mixed-refs --no-8x8dct replaces --8x8dct --no-weightb replaces --weightb Replaced ? enabled by default now ? Doesn't that add huge encoding time vs default megui partitions ? with maximum 0.5% compression gain ? Last edited by juGGaKNot; 2nd July 2009 at 09:31. |
||
2nd July 2009, 09:33 | #20 | Link | |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,806
|
Quote:
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|