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.

 

Go Back   Doom9's Forum > Video Encoding > High Efficiency Video Coding (HEVC)

Reply
 
Thread Tools Search this Thread Display Modes
Old 17th August 2014, 13:57   #1201  |  Link
a5180007
Registered User
 
Join Date: Jun 2014
Location: Marrakech, Morocco
Posts: 253
Quote:
Originally Posted by LoRd_MuldeR View Post
To my understanding, the range for these options will remain 0.0 to 2.0.
As stated above (post #1196), rdoq range has been changed to 0.0..10.0 so that 1.0 is the recommended value.


EDIT : also, psy-rd/psy-rdoq are not written to the SEI:

x265 --rd 4 --psy-rd 1.0 --psy-rdoq 1.0 park_joy_1080p50.y4m -o park_joy.hevc
Code:
x265 (build 31) - 1.2+555-866f21378d94:[Windows][MSVC 1800][32 bit] 8bpp - H.265/HEVC codec - Copyright 2013-2014 (c) Multicoreware
Inc - http://x265.org - options: 1920x1080 fps=50/1 bitdepth=8 wpp ctu=64 tu-intra-depth=1 tu-inter-depth=1 me=1 subme=2 merange=57
no-rect no-amp max-merge=2 no-early-skip no-fast-cbf rdpenalty=0 no-tskip no-tskip-fast strong-intra-smoothing no-lossless
no-cu-lossless no-constrained-intra no-fast-intra open-gop interlace=0 keyint=250 min-keyint=25 scenecut=40 rc-lookahead=20 bframes=4
bframe-bias=0 b-adapt=2 ref=3 weightp no-weightb aq-mode=2 aq-strength=1.00 cbqpoffs=0 crqpoffs=0 rd=4 signhide lft sao
sao-lcu-bounds=0 sao-lcu-opt=1 b-pyramid cutree rc=crf crf=28.0 qcomp=0.60 qpmin=0 qpmax=51 qpstep=4 ipratio=1.40 pbratio=1.30
Otherwise, much less ugly artefacts in 32 and 64 CTUs!

Last edited by a5180007; 17th August 2014 at 15:36.
a5180007 is offline   Reply With Quote
Old 17th August 2014, 18:34   #1202  |  Link
x265_Project
Guest
 
Posts: n/a
Quote:
Originally Posted by a5180007 View Post
As stated above (post #1196), rdoq range has been changed to 0.0..10.0 so that 1.0 is the recommended value.

EDIT : also, psy-rd/psy-rdoq are not written to the SEI:
Thanks for the feedback. We'll take care of this.
  Reply With Quote
Old 18th August 2014, 10:06   #1203  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,752
Because it is "stable" now, x265 1.2+557-87400d5c90aa.
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid
LigH is offline   Reply With Quote
Old 18th August 2014, 23:22   #1204  |  Link
Blue_MiSfit
Derek Prestegard IRL
 
Blue_MiSfit's Avatar
 
Join Date: Nov 2003
Location: Los Angeles
Posts: 5,988
I'm using the build that LigH just posted above ^^ 1.2+557-87400d5c90aa - the 8 bit variety on x64.

I thought I'd do some PSNR and speed tests just for fun, and got some odd behavior. See how it's warning be about setting --tune psnr even though I already have it set?

Code:
G:\>x265.exe --input parkjoy.y4m --preset medium --tune psnr --psnr --bitrate 80
00 --vbv-maxrate 8000 --vbv-bufsize 8000 --output parkjoy_x265_8000_medium.h265

y4m  [info]: 1920x1080 fps 50/1 i420p8 sar 1:1 frames 0 - 207 of 208
x265 [info]: HEVC encoder version 1.2+557-87400d5c90aa
x265 [info]: build info [Windows][GCC 4.8.2][64 bit] 8bpp
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
x265 [info]: WPP streams / pool / frames         : 17 / 8 / 3
x265 [warning]: --psnr used with AQ on: results will be invalid!
x265 [warning]: --tune psnr should be used if attempting to benchmark psnr!
x265 [info]: Main profile, Level-4.1 (Main tier)
x265 [info]: CU size                             : 64
x265 [info]: Max RQT depth inter / intra         : 1 / 1
x265 [info]: ME / range / subpel / merge         : hex / 57 / 2 / 2
x265 [info]: Keyframe min / max / scenecut       : 25 / 250 / 40
x265 [info]: Lookahead / bframes / badapt        : 20 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb / refs: 1 / 1 / 0 / 3
x265 [info]: Rate Control / AQ-Strength / CUTree : ABR-8000 kbps / 0.0 / 1
x265 [info]: VBV/HRD buffer / max-rate / init    : 8000 / 8000 / 0.900
x265 [info]: tools: rd=3 lft sao-lcu signhide

x265 [info]: frame I:      1, Avg QP:36.74  kb/s: 32723.60  PSNR Mean: Y:32.379
U:35.246 V:37.691
x265 [info]: frame P:     52, Avg QP:36.80  kb/s: 26042.37  PSNR Mean: Y:28.665
U:31.432 V:35.047
x265 [info]: frame B:    155, Avg QP:41.61  kb/s: 2187.03   PSNR Mean: Y:27.569
U:31.301 V:35.014
x265 [info]: global :    208, Avg QP:40.39  kb/s: 8297.68   PSNR Mean: Y:27.866
U:31.353 V:35.035
x265 [info]: Weighted P-Frames: Y:1.9% UV:1.9%
x265 [info]: consecutive B-frames: 1.9% 0.0% 1.9% 96.2% 0.0%

encoded 208 frames in 26.58s (7.82 fps), 8297.68 kb/s, Global PSNR: 29.198
__________________
These are all my personal statements, not those of my employer :)

Last edited by Blue_MiSfit; 18th August 2014 at 23:24.
Blue_MiSfit is offline   Reply With Quote
Old 19th August 2014, 03:13   #1205  |  Link
x265_Project
Guest
 
Posts: n/a
Quote:
Originally Posted by Blue_MiSfit View Post
I'm using the build that LigH just posted above ^^ 1.2+557-87400d5c90aa - the 8 bit variety on x64.

I thought I'd do some PSNR and speed tests just for fun, and got some odd behavior. See how it's warning be about setting --tune psnr even though I already have it set?
Good point. I'll have the team take a look at this.

Should be fixed with this patch... https://bitbucket.org/multicoreware/...34de996742d5e8

Last edited by x265_Project; 19th August 2014 at 03:58. Reason: Status update
  Reply With Quote
Old 20th August 2014, 06:57   #1206  |  Link
Blue_MiSfit
Derek Prestegard IRL
 
Blue_MiSfit's Avatar
 
Join Date: Nov 2003
Location: Los Angeles
Posts: 5,988
Hooray I contributed
__________________
These are all my personal statements, not those of my employer :)
Blue_MiSfit is offline   Reply With Quote
Old 20th August 2014, 11:50   #1207  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,752
Because many stable and much fixes, wow - x265 1.2+575-80129b1b6260
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid
LigH is offline   Reply With Quote
Old 21st August 2014, 20:55   #1208  |  Link
benwaggoner
Moderator
 
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
Quote:
Originally Posted by a5180007 View Post
@x265_Project, before 1.3 tagging, it would be better to change the --help (1.2+555-866f213 below) :

--psy-rd <0..2.0> Strength of psycho-visual rate distortion optimization, 0 to disable. Default 0.000000
--psy-rdoq <0..2.0> Strength of psycho-visual optimization in quantization, 0 to disable. Default 0.000000
Does this mean that --psy-rd has been refactored so that 1.0 should be the "default" now, not ~0.3 as before?
__________________
Ben Waggoner
Principal Video Specialist, Amazon Prime Video

My Compression Book
benwaggoner is offline   Reply With Quote
Old 21st August 2014, 21:04   #1209  |  Link
benwaggoner
Moderator
 
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
And a couple of other questions about settings and presets
  • --rdpenalty defaults to 0, although by the description I'd think 1 (RD-penalty) would be prefereable. Is there a downside or risk to using 1? And what the heck is 2 for?
  • --weightb is off by default everywhere. Does using it have any risks or downsides?
__________________
Ben Waggoner
Principal Video Specialist, Amazon Prime Video

My Compression Book
benwaggoner is offline   Reply With Quote
Old 21st August 2014, 21:32   #1210  |  Link
x265_Project
Guest
 
Posts: n/a
Quote:
Originally Posted by benwaggoner View Post
Does this mean that --psy-rd has been refactored so that 1.0 should be the "default" now, not ~0.3 as before?
Yes it does.
  Reply With Quote
Old 22nd August 2014, 03:31   #1211  |  Link
lotusgg
Registered User
 
Join Date: Apr 2014
Posts: 45
Can someone compile and upload 1.3 stable for me?
For some reason, I just can't get it to work on my encoding ded.
lotusgg is offline   Reply With Quote
Old 22nd August 2014, 04:34   #1212  |  Link
H3
Registered User
 
Join Date: Aug 2014
Posts: 2
Quote:
Originally Posted by lotusgg View Post
Can someone compile and upload 1.3 stable for me?
For some reason, I just can't get it to work on my encoding ded.
I hope this helps you:

http://builds.x265.eu/
H3 is offline   Reply With Quote
Old 22nd August 2014, 04:44   #1213  |  Link
filler56789
SuperVirus
 
filler56789's Avatar
 
Join Date: Jun 2012
Location: Antarctic Japan
Posts: 1,351
Quote:
Originally Posted by H3 View Post
I hope this helps you:

http://builds.x265.eu/
Hmmm, according to Windows Explorer, their latest build is version 1.2+580-9461fc801cd2.

Version 1.2.581 (8bpp, both 32-bits and 64-bits) @ http://forum.videohelp.com/threads/3...79#post2341579
filler56789 is offline   Reply With Quote
Old 22nd August 2014, 07:02   #1214  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,752
I'm going to build it, but the stable merge (1.3+2-2e17cb106b17) seems to have a lot of warnings regarding signed/unsigned comparisons etc., will probably prefer the latest development revision for publishing.
__

x26+1.3+18-bad70432b1d3
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid

Last edited by LigH; 22nd August 2014 at 07:56.
LigH is offline   Reply With Quote
Old 22nd August 2014, 07:22   #1215  |  Link
x265_Project
Guest
 
Posts: n/a
We are pleased to announce that we have reached version 1.3.

The primary changes in this release are the completion and tuning of the psycho-visual optimizations and new support for multiple pass encoding.

--psy-rd and --psy-rdoq are now completed and scaled such that their recommended initial values are 1.0.

Multipass encodes are now possible with --pass N and --stats FNAME

As usual, full documentation is at: http://x265.readthedocs.org/en/1.3/

= API Changes =

* param.bEmitInfoSEI, --[no-]info
include an SEI identifying the encoder and encoding options.

* param.bHighTier --high-tier
specify tier (used in conjunction with --level-idc)

* param.bEnableFastIntra --[no-]fast-intra
Use a gradient descent to scan angular intra modes

* param.totalFrames
optional indicator of total frame count, may improve rate control

* param.scalingLists
specify custom quantization matrices, "default" or filename

* param.psyRdoq
Psycho-visual optimizations for quantization

* param.bEnableSlowFirstPass
The first pass of multi-pass encodes will run in *turbo* mode unless this option is enabled.
  Reply With Quote
Old 22nd August 2014, 16:16   #1216  |  Link
a5180007
Registered User
 
Join Date: Jun 2014
Location: Marrakech, Morocco
Posts: 253
Nice improvements with this version !
Although the 2-pass is not a "pure CRF" yet. And there is a fair difference in first frames and I-frames sizes and ssim :

File http://www.diktafon.atw.hu/112.MTS
x265 1.3+18 crf28 (48,756 KB) vs --bitrate 6764 --pass 2 (48,738 KB)



Last edited by a5180007; 22nd August 2014 at 17:49. Reason: added ssim curve
a5180007 is offline   Reply With Quote
Old 22nd August 2014, 18:15   #1217  |  Link
benwaggoner
Moderator
 
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
Quote:
Originally Posted by x265_Project View Post
Yes it does.
Anything you can share about --rdpenalty and --weightb?
__________________
Ben Waggoner
Principal Video Specialist, Amazon Prime Video

My Compression Book
benwaggoner is offline   Reply With Quote
Old 22nd August 2014, 18:22   #1218  |  Link
x265_Project
Guest
 
Posts: n/a
Quote:
Originally Posted by benwaggoner View Post
Anything you can share about --rdpenalty and --weightb?
These algorithms are in the same class... the code is in place, but we haven't spent much time on these functions as we had bigger fish to fry (RDOQ and psy-rdoq, etc.). We'll be turning our attention to these functions, but until we have had a chance to really evaluate how they are working in conjunction with the other changes we recently implemented, we can't recommend using them.
  Reply With Quote
Old 23rd August 2014, 11:46   #1219  |  Link
NikosD
Registered User
 
Join Date: Aug 2010
Location: Athens, Greece
Posts: 2,901
Is there somewhere documented which parts of the code (functions ?) are optimised for AVX2 and which is the speed-up of these specific optimisations ?

Are there any functions using floating point numbers ?

Thanks!
__________________
Win 10 x64 (19042.572) - Core i5-2400 - Radeon RX 470 (20.10.1)
HEVC decoding benchmarks
H.264 DXVA Benchmarks for all
NikosD is offline   Reply With Quote
Old 24th August 2014, 02:34   #1220  |  Link
x265_Project
Guest
 
Posts: n/a
Quote:
Originally Posted by NikosD View Post
Is there somewhere documented which parts of the code (functions ?) are optimised for AVX2 and which is the speed-up of these specific optimisations ?
Thanks!
denoise_dct
pixel_avg
frame_init_lowres_core
mbtree_propagate_cost
cvt32to16_shl
cvt16to32_cnt
pixel_satd
pixel_var
pixel_sad
pixel_ssd

You can turn off AVX2 or any other specific assembly code optimization using --asm to test the performance difference.
  Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 11:48.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.