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. |
22nd January 2017, 00:44 | #4641 | Link |
Registered User
Join Date: Aug 2006
Posts: 2,229
|
Here's the results of my comparison test. I used pretty much my standard settings for the test, but with SSIM and PSNR stats enabled. I realise that psy-rd etc affects the SSIM and PSNR stats such that they become 'invalid', but I wanted to do a 'real world' encode comparison, not one with settings that I would never use (basically with psy-rd etc turned off). Differences in the motion estimation will affect all things down stream from it, such as AQ, psy-rd etc, by leaving them enabled even though the results are 'inaccurate' it does potentially show how changes in the settings affect these features.
Settings used, apart from the ME, and where applicable the ME range: --crf 20 --output-depth 10 --rd 4 --tu-intra-depth 4 --tu-inter-depth 4 --rdoq-level 2 --b-intra --limit-modes --aq-mode 2 --nr-intra 400 --nr-inter 400 --ipratio 1.38 --pbratio 1.28 --max-merge 4 --weightb --analyze-src-pics --bframes 6 --rc-lookahead 45 --ref 6 --keyint 600 --psy-rdoq 1.28 --no-sao --qg-size 8 --limit-tu 3 --ssim-rd --psy-rd 2.00 --ssim --psnr No avisynth filters were used for the comparison apart from the source filter. HEX Code:
x265 [info]: frame I: 33, Avg QP:17.37 kb/s: 5382.71 PSNR Mean: Y:46.296 U:49.536 V:50.818 SSIM Mean: 0.982813 (17.648dB) x265 [info]: frame P: 474, Avg QP:19.67 kb/s: 1342.77 PSNR Mean: Y:45.543 U:49.001 V:49.778 SSIM Mean: 0.982113 (17.475dB) x265 [info]: frame B: 1493, Avg QP:25.19 kb/s: 225.04 PSNR Mean: Y:45.006 U:48.783 V:49.559 SSIM Mean: 0.980893 (17.188dB) x265 [info]: Weighted P-Frames: Y:1.1% UV:0.0% x265 [info]: Weighted B-Frames: Y:0.4% UV:0.0% x265 [info]: consecutive B-frames: 9.7% 0.6% 7.1% 61.5% 10.5% 10.7% 0.0% STAR Code:
x265 [info]: frame I: 33, Avg QP:17.37 kb/s: 5377.76 PSNR Mean: Y:46.294 U:49.532 V:50.819 SSIM Mean: 0.982812 (17.648dB) x265 [info]: frame P: 474, Avg QP:19.67 kb/s: 1340.51 PSNR Mean: Y:45.545 U:49.001 V:49.772 SSIM Mean: 0.982131 (17.479dB) x265 [info]: frame B: 1493, Avg QP:25.19 kb/s: 225.26 PSNR Mean: Y:45.010 U:48.782 V:49.552 SSIM Mean: 0.980912 (17.192dB) x265 [info]: Weighted P-Frames: Y:1.1% UV:0.0% x265 [info]: Weighted B-Frames: Y:0.4% UV:0.0% x265 [info]: consecutive B-frames: 9.7% 0.6% 7.1% 61.5% 10.5% 10.7% 0.0% STAR24 for interest, me range changed to 24 from default 57 Code:
x265 [info]: frame I: 33, Avg QP:17.37 kb/s: 5374.91 PSNR Mean: Y:46.289 U:49.532 V:50.813 SSIM Mean: 0.982800 (17.645dB) x265 [info]: frame P: 474, Avg QP:19.67 kb/s: 1344.30 PSNR Mean: Y:45.558 U:49.008 V:49.782 SSIM Mean: 0.982175 (17.490dB) x265 [info]: frame B: 1493, Avg QP:25.20 kb/s: 226.28 PSNR Mean: Y:45.018 U:48.789 V:49.563 SSIM Mean: 0.980951 (17.201dB) x265 [info]: Weighted P-Frames: Y:1.1% UV:0.0% x265 [info]: Weighted B-Frames: Y:0.4% UV:0.0% x265 [info]: consecutive B-frames: 9.7% 0.6% 7.1% 61.5% 10.5% 10.7% 0.0% STAR35 as above, but 35 Code:
x265 [info]: frame I: 33, Avg QP:17.37 kb/s: 5380.92 PSNR Mean: Y:46.297 U:49.528 V:50.828 SSIM Mean: 0.982821 (17.650dB) x265 [info]: frame P: 474, Avg QP:19.67 kb/s: 1343.05 PSNR Mean: Y:45.550 U:48.998 V:49.775 SSIM Mean: 0.982151 (17.484dB) x265 [info]: frame B: 1493, Avg QP:25.20 kb/s: 225.62 PSNR Mean: Y:45.014 U:48.781 V:49.559 SSIM Mean: 0.980931 (17.197dB) x265 [info]: Weighted P-Frames: Y:1.1% UV:0.0% x265 [info]: Weighted B-Frames: Y:0.4% UV:0.0% x265 [info]: consecutive B-frames: 9.7% 0.6% 7.1% 61.5% 10.5% 10.7% 0.0% UMH Code:
x265 [info]: frame I: 33, Avg QP:17.37 kb/s: 5374.79 PSNR Mean: Y:46.290 U:49.529 V:50.821 SSIM Mean: 0.982806 (17.646dB) x265 [info]: frame P: 474, Avg QP:19.67 kb/s: 1341.79 PSNR Mean: Y:45.541 U:48.998 V:49.775 SSIM Mean: 0.982107 (17.473dB) x265 [info]: frame B: 1493, Avg QP:25.19 kb/s: 224.90 PSNR Mean: Y:45.007 U:48.781 V:49.558 SSIM Mean: 0.980894 (17.188dB) x265 [info]: Weighted P-Frames: Y:1.1% UV:0.0% x265 [info]: Weighted B-Frames: Y:0.4% UV:0.0% x265 [info]: consecutive B-frames: 9.7% 0.6% 7.1% 61.5% 10.5% 10.7% 0.0% SEA Code:
x265 [info]: frame I: 33, Avg QP:17.37 kb/s: 5378.57 PSNR Mean: Y:46.289 U:49.529 V:50.817 SSIM Mean: 0.982796 (17.644dB) x265 [info]: frame P: 474, Avg QP:19.67 kb/s: 1341.23 PSNR Mean: Y:45.539 U:49.005 V:49.779 SSIM Mean: 0.982106 (17.473dB) x265 [info]: frame B: 1493, Avg QP:25.19 kb/s: 224.58 PSNR Mean: Y:45.005 U:48.785 V:49.561 SSIM Mean: 0.980891 (17.188dB) x265 [info]: Weighted P-Frames: Y:1.1% UV:0.0% x265 [info]: Weighted B-Frames: Y:0.4% UV:0.0% x265 [info]: consecutive B-frames: 9.7% 0.6% 7.1% 61.5% 10.5% 10.7% 0.0% SEA was by far the slowest and also had the lowest rated stats. HEX was the fastest, followed by STAR (and of the ME range settings), and UMH. I thought I'd throw in STAR with different ME ranges to show the difference in speed versus the quality output. I wasn't expecting the lower the ME range the higher the PSNR and SSIM, but there is also a slight increase in bitrate so it make sense. The results for fast motion scenes may be different, and higher resolutions a higher ME range is more important. The video encoded was 712x480, encoding to 2160 the same motion has to travel across significantly more pixels which I would assume would necessitate a higher ME range setting for the same detection. The weight p and b frames are usually different to those from the clip. I guess it depends on what is in the clip. A full encode is like this (from an full encode): x265 [info]: Weighted P-Frames: Y:6.4% UV:4.0% x265 [info]: Weighted B-Frames: Y:4.9% UV:2.5% Of course, with the figures being different in each encode. Last edited by burfadel; 22nd January 2017 at 00:59. |
22nd January 2017, 17:28 | #4642 | Link | |
Registered User
Join Date: May 2015
Posts: 68
|
Quote:
I'll run tests with those checked and report back. |
|
22nd January 2017, 20:04 | #4643 | Link |
Registered User
Join Date: Jan 2007
Posts: 729
|
Seems that next-gen HEVC has been researched for some time: https://forum.doom9.org/showthread.php?t=174245
I wonder if this time, it'll be viable to extend x265 to support the new format instead of starting from scratch (or from the reference encoder), or if the differences will be too big again. |
23rd January 2017, 15:42 | #4644 | Link |
Registered User
Join Date: Feb 2007
Location: Sweden
Posts: 483
|
x265 v2.2+23-58dddcf01b7d (MSYS/MinGW, GCC 6.3.0, 32 & 64bit 8/10/12bit multilib EXEs)
|
23rd January 2017, 22:31 | #4645 | Link | |
Registered User
Join Date: Jan 2010
Posts: 709
|
Quote:
also as it is still an experimental feature I'd not use it in a real encode. nr-intra & nr-inter 400 ? + qg-size 8?? also I suspect analyze-src-pics can do something on how metrics are computed...
__________________
powered by Google Translator Last edited by Motenai Yoda; 23rd January 2017 at 22:39. |
|
24th January 2017, 03:45 | #4647 | Link |
Registered User
Join Date: Aug 2006
Posts: 2,229
|
ssim-rd does disable psy-rd, it does this by using a default of 0.00, at least during testing. If you specify it manually*you can still use it. I use 400 for nr*as it isn't really noticeable but saves bitrate. I can therefore use a lower CRF*so the result is higher quality output.
|
24th January 2017, 07:38 | #4648 | Link | |
Registered User
Join Date: Aug 2013
Posts: 5
|
Quote:
|
|
25th January 2017, 11:02 | #4649 | Link |
Unavailable
Join Date: Mar 2009
Location: offline
Posts: 1,480
|
x265 2.2+25-3737c70c3308
Code:
add support for aq-motion even when aq-mode is disabled |
25th January 2017, 17:03 | #4651 | Link | |
Guest
Posts: n/a
|
Quote:
|
|
26th January 2017, 07:14 | #4652 | Link |
Unavailable
Join Date: Mar 2009
Location: offline
Posts: 1,480
|
x265.exe 2.2+26-d1f6d9b8d6be
Code:
Add filler bits when frame bits < vbv target in strict-cbr |
26th January 2017, 21:08 | #4653 | Link | |
Registered User
Join Date: Sep 2016
Location: New Zealand
Posts: 18
|
Quote:
"high-tier allows the support of high tier at that level. The encoder will first attempt to encode at the specified level, main tier first, turning on high tier only if necessary and available at that level." Pretty self-explanatory => even if you set the flag, it will attempt main tier first and only use high-tier if necessary. |
|
27th January 2017, 14:07 | #4655 | Link | |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,781
|
x265 2.2+29-2f075fe8d4c5
Code:
--complex-analysis <0..4.0> Strength of complex analysis, 0 to disable. Default 0.0 Quote:
|
|
27th January 2017, 15:06 | #4656 | Link | |
Registered User
Join Date: Aug 2006
Posts: 2,229
|
Quote:
I also guess that for non restricted VBV like normal encoding with ABR, the function serves little use. I wonder whether it could be adopted to apply based on complexity rather than stating actual numbers, which would vary from encode to encode. For instance, a particular video might have scenes where there is low complexity, and there is plentiful use of P and B frames. There could be points in the video where the complexity increases such that fewer P and B frame could be utilised, resulting in a higher bitrate. When this occurs a higher complex-analysis seting can be used, 0.5 (variable strength) could be used there and scales upwards further with higher complexity. The setting would therefore be the scaling rate, such that a lower setting would be more constrained in the scaling, and not a fixed rate, based on perceived complexity of the current run of frames. This would make it useful for normal use and not a per-encode use that is required with the existing code due to stating VBV limitations that varies with content, complexity, and resolution. I realise this isn't the purpose of it spefically, it's just an interesting concept that could be repurposed. Just an idea . Last edited by burfadel; 27th January 2017 at 15:28. |
|
27th January 2017, 15:12 | #4657 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,781
|
How do I? TortoiseHg Workbench does not report any changes since. The commit log on bitbucket neither.
Last edited by LigH; 27th January 2017 at 15:15. |
27th January 2017, 16:51 | #4658 | Link |
Registered User
Join Date: Aug 2006
Posts: 2,229
|
Probably not committed to the development branch yet, patches are here:
https://patches.videolan.org/project/x265-devel/list/ |
27th January 2017, 21:25 | #4659 | Link | |
Guest
Posts: n/a
|
Quote:
|
|
27th January 2017, 21:28 | #4660 | Link | |
Guest
Posts: n/a
|
Quote:
|
|
Thread Tools | Search this Thread |
Display Modes | |
|
|