x265 UHD-BD compliant "perfect" settings

[CSchmidlapp]

The fact is, I'm aiming toward UHD-BD compliance, hence 422 would not be compliant, so you could go with x264 and get comparable (if not better) quality, almost surely with lower encoding time.

Yes. Sorry I didn't want to hijack your thread
I wanted to get into x265 encoding eventually and testing and adapting your settings seemed like the route to go.

[spoRv]

No problems!

This thread was made to discuss about x265, to get the optimal settings - I mean, it's useless IMHO to spend a whole week of encoding to get a 2.62% better quality than another encoding made in "only" one day; I prefer to use my PC in the spared 6 days to do something else (other 6 encoding, for example).

[spoRv]

Found this:

https://www.elecard.com/benchmarks

could be useful, I guess!

EDIT: I've made some comparison between medium (default) and veryslow, and difference in quality is very tiny, while speed difference is quite huge - up to 10/15x; sure, test clips are only 1080p, but I think 2160p should be the same.

[spoRv]

Is there anybody with an UHD-BD hardware player, that would like to test an UHD-BD homemade disk?

All you need is a BD-R in your computer, and a BD-R disk to "sacrifice" - or, better, a BD-RE that you could reuse.

[Chewtobacca]

Two examples of UHD BDs in which x265 was used for both the main stream and (apparently with the help of supporting software) the DV layer have been posted here on doom9.  They should prove useful references for those of you working (eventually) toward UHD-BD compliance.

[LucasGodzilla]

May sound like a dumb question, but does this work with MOV files? I've been trying to encode a file and the errors I get make me wonder if that's possibly a result of the file format or just me not setting something up properly.

[dark_ripper]

Are people paying attention to this thread still? I currently have settings that I somewhat copied over from bluray encodes. The resulting video plays and seems to work fine with the exception that seeking does not work (fast forward/rewind, chapters still work fine). With standard blurays, that was usually a key frame issue. Below I've compared the settings in this thread with the settings I'm currently using. Note that I'm using a GUI for x265 (RipBot) vs doing this through CLI alone.

x265_x64.exe --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --max-cll "1126,144" --pass 2 --bitrate 56115 --stats "D:\Temp\RipBot264temp\job1\job1.stats" --fps 24  --frames 131171 --sar 1:1 --profile main10 --level 5.1 --output-depth 10 --hrd --vbv-bufsize 50000 --vbv-maxrate 50000 --ref 4 --min-keyint 1 --keyint 24 --bframes 4 --b-adapt 2 --no-b-pyramid --subme 3 --me umh --ctu 64 --merange 57 --y4m --output "D:\Temp\RipBot264temp\job1\video.265"

--transfer smpte2084 Missing in below
--colormatrix Has bt2020nc below
--max-cll "1126,144" vs "1000,400" below
--fps 24  --frames 131171 missing below. May be specific to each encode and/or unnecessary specifications
--sar 1:1 vs sar 1 below (possibly essentially the same)
--level 5.1 vs below --level-idc 51
--vbv-bufsize 50000 --vbv-maxrate 50000 vs --vbv-maxrate 64000 --vbv-bufsize 64000 (possibly just preference on where you want to cap the bitrate and/or what is more appropriate)
--ref 4 vs --ref 5 below
--bframes 4
--b-adapt 2
--no-b-pyramid
--subme 3
--me umh (I believe this is generally considered better and preserving quality)
--ctu 64
--merange 57
--y4m

x265.exe --pass 2 --uhd-bd --bitrate 50000 --vbv-maxrate 64000 --vbv-bufsize 64000 --keyint 24 --min-keyint 1 --preset medium --tune grain --profile main10 --level-idc 51 --high-tier --aud --sar 1 --hrd --repeat-headers --no-open-gop --ref 5 --no-temporal-layers --overscan show --wpp --input-depth 10 --output-depth 10 --no-interlace --range limited --chromaloc 2 --colorprim bt2020 --transfer bt2020-10 --colormatrix bt2020nc --max-cll "1000,400" --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --stats ".stats" --output "Output_File.265" "Input_File.avs"

included in the suggested thread here, but not in mine:
--preset medium
--tune grain
--high-tier
--aud
--repeat-headers
--no-open-gop
--no-temporal-layers
--overscan show
--wpp
--input-depth 10
--no-interlace
--range limited
--chromaloc 2
--transfer bt2020-10
--colormatrix bt2020nc

I've looked up a lot of these arguments at some point, but don't recall what they all mean. If someone more knowledgeable wants to work with things, I can do some test encodes an burns. Some of the arguments suggested here might be unnecessary (like no-interlace). And some of the ones I have appear to be defined under --preset medium (but not necessarily the same).

[markus1970]

I have a 58 min mp4 4k file which is 3840x2160 at 50Fps encoded to x264 AVC and I want to convert this to HEVC 265 as a .265 extension and bluray UHD compatible to import into bludisc studio as it only accepts .265 file extension, I have tried the below script but the file generated is under 100Mb and takes about 30 Minutes to complete which is strange as my input file is 22GB.

Any Ideas.

Code:

.\x265.exe --uhd-bd --bitrate 40000 --vbv-maxrate 80000 --vbv-bufsize 100000 --keyint 50 --min-keyint 1 --preset slow --tune grain --profile main10 --level-idc 51 --high-tier --aud --sar 1 --hrd --repeat-headers --no-open-gop --ref 5 --no-temporal-layers --overscan show --wpp --input-depth 10 --output-depth 10 --no-interlace --range limited --colorprim bt709 --transfer bt709 --colormatrix bt709 --stats ".stats" --input-res 3840x2160 --fps 50000/1001 --output "hevc-4k.265" --input "VTS_4k.mp4"

I get the following results.

Code:

yuv  [info]: 3840x2160 fps 50000/1001 i420p10 sar 1:1 frames 0 - 1009 of 1010 raw  [info]: output file: hevc-4k.265 x265 [info]: HEVC encoder version 3.5+20-17839cc0d x265 [info]: build info [Windows][MSVC 1930][64 bit] 10bit x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2 x265 [info]: Main 10 profile, Level-5.1 (High tier) x265 [info]: Thread pool created using 16 threads x265 [info]: Slices                              : 1 x265 [info]: frame threads / pool features      : 4 / wpp(34 rows) x265 [info]: Coding QT: max CU size, min CU size : 64 / 8 x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra x265 [info]: ME / range / subpel / merge        : star / 57 / 3 / 3 x265 [info]: Keyframe min / max / scenecut / bias  : 1 / 50 / 40 / 5.00 x265 [info]: Lookahead / bframes / badapt        : 25 / 4 / 2 x265 [info]: b-pyramid / weightp / weightb      : 1 / 1 / 0 x265 [info]: References / ref-limit  cu / depth  : 5 / on / on x265 [info]: Rate Control / qCompress            : ABR-40000 kbps / 0.60 x265 [info]: VBV/HRD buffer / max-rate / init    : 100000 / 80000 / 0.900 x265 [info]: tools: rect limit-modes rd=4 psy-rd=4.00 rdoq=2 psy-rdoq=10.00 x265 [info]: tools: signhide tmvp strong-intra-smoothing lslices=4 deblock x265 [info]: frame I:    22, Avg QP:54.96  kb/s: 536126.58 x265 [info]: frame P:    202, Avg QP:54.02  kb/s: 22763.93 x265 [info]: frame B:    786, Avg QP:54.17  kb/s: 26821.69 x265 [info]: Weighted P-Frames: Y:56.4% UV:55.9% x265 [info]: consecutive B-frames: 9.8% 0.0% 0.0% 9.8% 80.4% encoded 1010 frames in 876.76s (1.15 fps), 37103.91 kb/s, Avg QP:54.16

[bronan]

It only sees it as 1000 frames, so it most likely isn't reading your MP4 correctly. What you could do is write an AVS script to open the MP4 with ffmpeg, then add the .avs script as your input file instead of the MP4. You'll need to install AVS Plus and the FFMS2 plugin, then your AVS script just needs the line:

FFVideoSource("c:\VTS_4k.mp4")

[bronan]

I've been working on a little project that requires re-encoding HDR video, so I've been playing around with this a bit. There are a couple changes that are definitely needed to what's in the original post:

- replace "--no-temporal-layers" with "--temporal-layers 0" (original deprecated last year)
- replace "--transfer bt2020-10" with "--transfer smpte2084"

I've gone through most of the settings and they do seem correct, even some suspect ones like "--range limited". I thought it wasn't needed for HDR, but it does appear standard for commercial encodes and it is the default anyway.

A small test clip is now working correctly on my Oppo and triggering HDR as it should. Also, comparing the video stream in MediaInfo to the original from the disc shows the formats as identical. I will check back if I run into anything else.