<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<STYLE>
BLOCKQUOTE {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
LINE-HEIGHT: 1.5; FONT-FAMILY: Tahoma; COLOR: #000000; FONT-SIZE: 12pt
}
</STYLE>
<META name=GENERATOR content="MSHTML 8.00.7600.16968"></HEAD>
<BODY style="MARGIN: 10px">
<DIV>hi,x265-devel@videolan.org</DIV>
<DIV> </DIV>
<DIV>I have test the case for foreman.yuv with paras</DIV>
<DIV style="TEXT-INDENT: 2em">1. --no-wpp --psnr --ssim --rc-lookahead 0
--bframes 0 --b-adapt 1 --ref 1 --no-weightp --aq-mode 1 --no-cutree
--threads 1 --output foreman_test1.h265 --input-res 352x288 --fps 25
--frame-skip 0 --frames 0 --input-depth 8 --input foreman.yuv --log 3 -f
20</DIV>
<DIV style="TEXT-INDENT: 2em">2. --no-wpp --psnr --ssim --rc-lookahead 1
--bframes 0 --b-adapt 1 --ref 1 --no-weightp --aq-mode 1 --no-cutree
--threads 1 --output foreman_test2.h265 --input-res 352x288 --fps 25
--frame-skip 0 --frames 0 --input-depth 8 --input foreman.yuv --log 3 -f
20</DIV>
<DIV style="TEXT-INDENT: 2em"> </DIV>
<DIV>when set "rc-lookhead" to 0 ,the QP is too low then bitrate is too
large.[<SPAN style="FONT-STYLE: italic; COLOR: #ff0000">1146.33 kb/s vs <SPAN
style="FONT-STYLE: italic; COLOR: #ff0000">186.31 kb/s</SPAN></SPAN>]</DIV>
<DIV>I think it's better to <SPAN class=def sizcache04656532571199502="1"
sizset="2"><A href="app:ds:initialize" target="">initialize</A> the QP with
proper value with last frame QP, it can avoid the bitrate peak and keep PNSR to
be acceptable.</SPAN></DIV>
<DIV> </DIV>
<DIV>the result log just below.</DIV>
<DIV style="FONT-STYLE: italic"> </DIV>
<DIV style="FONT-STYLE: normal">Thanks for you reply.</DIV>
<DIV style="FONT-STYLE: italic"> </DIV>
<DIV>
<DIV style="FONT-STYLE: italic">zxy@AlgorithmServer65:~/hevc/x265/test$
./x265_exe --no-wpp --psnr --ssim --rc-lookahead 0 --bframes 0 --b-adapt 1 --ref
1 --no-weightp --aq-mode 1 --no-cutree --threads 1 --output
foreman_test1.h265 --input-res 352x288 --fps 25 --frame-skip 0 --frames 0
--input-depth 8 --input foreman.yuv --log 3 -f 20</DIV>
<DIV style="FONT-STYLE: italic">yuv [info]: 352x288 25Hz C420, frames 0 -
19 of 300</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: using cpu capabilities: MMX2 SSE
SSE2Fast SSSE3 SSE4.2</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: HEVC encoder version
0.7+74-1776b9a58585</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: build info [Linux][GCC 4.4.3][64
bit] 8bpp</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: Main profile, Level-2 (Main
tier)</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: Parallelism disabled, single thread
mode</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: CU
size
: 64</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: Max RQT depth inter /
intra : 1 / 1</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: ME / range / subpel /
merge : hex / 57 / 2 / 2</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: Keyframe min / max /
scenecut : 25 / 250 / 40</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: Lookahead / bframes /
badapt : 0 / 0 / 1</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: b-pyramid / weightp /
refs : 0 / 0 / 1</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: Rate Control / AQ-Strength / CUTree
: CRF-28.0 / 1.0 / 0</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: tools: rect amp rd=3 lft sao-lcu
sign-hide </DIV>
<DIV style="FONT-STYLE: italic">POC 0 ( I-SLICE, nQP 25 QP
25) 63576 bits [Y: 39.60 U: 42.91 V: 45.11][SSIM:
0.955]</DIV>
<DIV style="FONT-STYLE: italic">POC 1 ( P-SLICE, nQP 30 QP
30) 2808 bits [Y: 36.79 U: 42.57 V:
44.62][SSIM: 0.940] [L0 0 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 2 ( P-SLICE, nQP 27 QP
27) 8976 bits [Y: 37.13 U: 42.52 V:
44.51][SSIM: 0.940] [L0 1 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 3 ( P-SLICE, nQP 25 QP
25) 13136 bits [Y: 37.63 U: 42.42 V: 44.36][SSIM:
0.942] [L0 2 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 4 ( P-SLICE, nQP 22 QP
22) 29816 bits [Y: 39.01 U: 43.01 V: 45.25][SSIM:
0.951] [L0 3 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 5 ( P-SLICE, nQP 21 QP
21) 27744 bits [Y: 39.22 U: 43.07 V: 45.37][SSIM:
0.954] [L0 4 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 6 ( P-SLICE, nQP 19 QP
19) 49280 bits [Y: 40.98 U: 43.87 V: 46.50][SSIM:
0.953] [L0 5 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 7 ( P-SLICE, nQP 18 QP
18) 60680 bits [Y: 41.72 U: 44.56 V: 47.09][SSIM:
0.955] [L0 6 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 8 ( P-SLICE, nQP 18 QP
18) 45232 bits [Y: 41.66 U: 44.71 V: 47.10][SSIM:
0.956] [L0 7 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 9 ( P-SLICE, nQP 17 QP
17) 56856 bits [Y: 41.82 U: 44.77 V: 47.10][SSIM:
0.961] [L0 8 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 10 ( P-SLICE, nQP 17 QP
17) 56272 bits [Y: 41.90 U: 44.82 V: 47.18][SSIM:
0.959] [L0 9 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 11 ( P-SLICE, nQP 17 QP
17) 51240 bits [Y: 41.82 U: 44.78 V: 47.39][SSIM:
0.959] [L0 10 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 12 ( P-SLICE, nQP 17 QP
17) 61392 bits [Y: 41.99 U: 44.82 V: 47.33][SSIM:
0.961] [L0 11 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 13 ( P-SLICE, nQP 17 QP
17) 63944 bits [Y: 41.95 U: 44.81 V: 47.52][SSIM:
0.961] [L0 12 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 14 ( P-SLICE, nQP 17 QP
17) 59936 bits [Y: 41.86 U: 44.87 V: 47.37][SSIM:
0.964] [L0 13 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 15 ( P-SLICE, nQP 17 QP
17) 59024 bits [Y: 41.84 U: 44.78 V: 47.42][SSIM:
0.962] [L0 14 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 16 ( P-SLICE, nQP 17 QP
17) 54680 bits [Y: 41.67 U: 44.63 V: 47.33][SSIM:
0.961] [L0 15 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 17 ( P-SLICE, nQP 17 QP
17) 52816 bits [Y: 41.63 U: 44.58 V: 47.29][SSIM:
0.963] [L0 16 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 18 ( P-SLICE, nQP 17 QP
17) 50056 bits [Y: 41.57 U: 44.57 V: 47.33][SSIM:
0.963] [L0 17 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 19 ( P-SLICE, nQP 17 QP
17) 49600 bits [Y: 41.65 U: 44.61 V: 47.35][SSIM:
0.965] [L0 18 ]</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: frame I:
1 kb/s: 1589.40 PSNR Mean: Y:39.601 U:42.914
V:45.110 SSIM Mean: 0.955334</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: frame P: 19
kb/s: 1123.01 PSNR Mean: Y:40.728 U:44.147 V:46.600 SSIM Mean:
0.956271</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: global : 20
kb/s: 1146.33 PSNR Mean: Y:40.672 U:44.085 V:46.526 SSIM Mean:
0.956224</DIV>
<DIV style="FONT-STYLE: italic"> </DIV>
<DIV style="FONT-STYLE: italic">encoded 20 frames in 3.08s (6.50 fps), <SPAN
style="FONT-STYLE: italic; COLOR: #ff0000">1146.33 kb/s</SPAN>, Global PSNR:
41.830, SSIM Mean Y: 0.9562239 (13.588 dB)</DIV>
<DIV style="FONT-STYLE: italic">zxy@AlgorithmServer65:~/hevc/x265/test$
./x265_exe --no-wpp --psnr --ssim --rc-lookahead 1 --bframes 0 --b-adapt 1 --ref
1 --no-weightp --aq-mode 1 --no-cutree --threads 1 --output
foreman_test2.h265 --input-res 352x288 --fps 25 --frame-skip 0 --frames 0
--input-depth 8 --input foreman.yuv --log 3 -f 20 </DIV>
<DIV style="FONT-STYLE: italic">yuv [info]: 352x288 25Hz C420, frames 0 -
19 of 300</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: using cpu capabilities: MMX2 SSE
SSE2Fast SSSE3 SSE4.2</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: HEVC encoder version
0.7+74-1776b9a58585</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: build info [Linux][GCC 4.4.3][64
bit] 8bpp</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: Main profile, Level-2 (Main
tier)</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: Parallelism disabled, single thread
mode</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: CU
size
: 64</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: Max RQT depth inter /
intra : 1 / 1</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: ME / range / subpel /
merge : hex / 57 / 2 / 2</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: Keyframe min / max /
scenecut : 25 / 250 / 40</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: Lookahead / bframes /
badapt : 1 / 0 / 1</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: b-pyramid / weightp /
refs : 0 / 0 / 1</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: Rate Control / AQ-Strength / CUTree
: CRF-28.0 / 1.0 / 0</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: tools: rect amp rd=3 lft sao-lcu
sign-hide </DIV>
<DIV style="FONT-STYLE: italic">POC 0 ( I-SLICE, nQP 25 QP
25) 63576 bits [Y: 39.60 U: 42.91 V: 45.11][SSIM:
0.955]</DIV>
<DIV style="FONT-STYLE: italic">POC 1 ( P-SLICE, nQP 32 QP
32) 2176 bits [Y: 36.46 U: 42.55 V:
44.60][SSIM: 0.938] [L0 0 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 2 ( P-SLICE, nQP 31 QP
31) 4232 bits [Y: 35.89 U: 42.33 V:
44.00][SSIM: 0.931] [L0 1 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 3 ( P-SLICE, nQP 31 QP
31) 4160 bits [Y: 35.22 U: 41.98 V:
43.42][SSIM: 0.924] [L0 2 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 4 ( P-SLICE, nQP 31 QP
31) 4968 bits [Y: 35.36 U: 41.77 V:
43.44][SSIM: 0.924] [L0 3 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 5 ( P-SLICE, nQP 31 QP
31) 4304 bits [Y: 35.04 U: 41.46 V:
43.03][SSIM: 0.938] [L0 4 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 6 ( P-SLICE, nQP 30 QP
30) 5264 bits [Y: 35.19 U: 41.38 V:
43.24][SSIM: 0.929] [L0 5 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 7 ( P-SLICE, nQP 30 QP
30) 4592 bits [Y: 34.96 U: 41.31 V:
43.08][SSIM: 0.925] [L0 6 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 8 ( P-SLICE, nQP 30 QP
30) 5312 bits [Y: 35.01 U: 41.17 V:
43.00][SSIM: 0.921] [L0 7 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 9 ( P-SLICE, nQP 30 QP
30) 5240 bits [Y: 34.75 U: 41.11 V:
43.08][SSIM: 0.917] [L0 8 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 10 ( P-SLICE, nQP 30 QP
30) 5392 bits [Y: 34.72 U: 40.99 V:
42.93][SSIM: 0.929] [L0 9 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 11 ( P-SLICE, nQP 30 QP
30) 5232 bits [Y: 34.68 U: 41.06 V:
42.93][SSIM: 0.923] [L0 10 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 12 ( P-SLICE, nQP 31 QP
31) 4400 bits [Y: 34.20 U: 40.93 V:
42.87][SSIM: 0.919] [L0 11 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 13 ( P-SLICE, nQP 31 QP
31) 5568 bits [Y: 34.05 U: 40.79 V:
42.75][SSIM: 0.916] [L0 12 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 14 ( P-SLICE, nQP 31 QP
31) 5608 bits [Y: 33.90 U: 40.51 V:
42.54][SSIM: 0.913] [L0 13 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 15 ( P-SLICE, nQP 31 QP
31) 5216 bits [Y: 33.89 U: 40.54 V:
42.62][SSIM: 0.922] [L0 14 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 16 ( P-SLICE, nQP 31 QP
31) 3408 bits [Y: 33.29 U: 40.42 V:
42.63][SSIM: 0.916] [L0 15 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 17 ( P-SLICE, nQP 31 QP
31) 3272 bits [Y: 33.09 U: 40.31 V:
42.45][SSIM: 0.912] [L0 16 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 18 ( P-SLICE, nQP 30 QP
30) 3976 bits [Y: 33.26 U: 40.38 V:
42.47][SSIM: 0.910] [L0 17 ]</DIV>
<DIV style="FONT-STYLE: italic">POC 19 ( P-SLICE, nQP 30 QP
30) 3152 bits [Y: 33.07 U: 40.32 V:
42.32][SSIM: 0.906] [L0 18 ]</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: frame I:
1 kb/s: 1589.40 PSNR Mean: Y:39.601 U:42.914
V:45.110 SSIM Mean: 0.955334</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: frame P: 19
kb/s: 112.46 PSNR Mean: Y:34.528 U:41.122 V:43.021 SSIM Mean:
0.921697</DIV>
<DIV style="FONT-STYLE: italic">x265 [info]: global : 20
kb/s: 186.31 PSNR Mean: Y:34.782 U:41.212 V:43.126 SSIM Mean:
0.923379</DIV>
<DIV style="FONT-STYLE: italic"> </DIV>
<DIV style="FONT-STYLE: italic">encoded 20 frames in 1.54s (12.95 fps), <SPAN
style="FONT-STYLE: italic; COLOR: #ff0000">186.31 kb/s</SPAN>, Global PSNR:
36.629, SSIM Mean Y: 0.9233790 (11.157 dB)</DIV>
<DIV>zxy@AlgorithmServer65:~/hevc/x265/test$</DIV></DIV>
<DIV> </DIV>
<HR style="WIDTH: 210px; HEIGHT: 1px" align=left color=#b5c4df SIZE=1>
<DIV><SPAN>
<DIV style="FONT-FAMILY: verdana; FONT-SIZE: 10pt">
<DIV><A href="mailto:zxy@rock-chips.com"><SPAN
style="FONT-SIZE: 12pt"></SPAN><SPAN style="FONT-SIZE: 20pt"></SPAN><SPAN
style="FONT-SIZE: 8pt"></SPAN><SPAN
style="FONT-SIZE: 8pt"></SPAN>zxy@rock-chips.com</A></DIV></DIV></SPAN></DIV>
<DIV> </DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV
style="PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; FONT-FAMILY: tahoma; BACKGROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B> <A
href="mailto:x265-devel-request@videolan.org">x265-devel-request</A></DIV>
<DIV><B>Date:</B> 2014-02-11 11:02</DIV>
<DIV><B>To:</B> <A
href="mailto:x265-devel@videolan.org">x265-devel</A></DIV>
<DIV><B>Subject:</B> x265-devel Digest, Vol 9, Issue 39</DIV></DIV></DIV>
<DIV>
<DIV>Send x265-devel mailing list submissions to</DIV>
<DIV>x265-devel@videolan.org</DIV>
<DIV> </DIV>
<DIV>To subscribe or unsubscribe via the World Wide Web, visit</DIV>
<DIV>https://mailman.videolan.org/listinfo/x265-devel</DIV>
<DIV>or, via email, send a message with subject or body 'help' to</DIV>
<DIV>x265-devel-request@videolan.org</DIV>
<DIV> </DIV>
<DIV>You can reach the person managing the list at</DIV>
<DIV>x265-devel-owner@videolan.org</DIV>
<DIV> </DIV>
<DIV>When replying, please edit your Subject line so it is more specific</DIV>
<DIV>than "Re: Contents of x265-devel digest..."</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Today's Topics:</DIV>
<DIV> </DIV>
<DIV> 1. Re: I would like to contribute to x265 (dave)</DIV>
<DIV> 2. Re: I would like to contribute to x265 (Deepthi
Nandakumar)</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>----------------------------------------------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 1</DIV>
<DIV>Date: Mon, 10 Feb 2014 17:44:06 -0800</DIV>
<DIV>From: dave <dtyx265@gmail.com></DIV>
<DIV>To: Development for x265 <x265-devel@videolan.org></DIV>
<DIV>Subject: Re: [x265] I would like to contribute to x265</DIV>
<DIV>Message-ID: <52F98066.7010105@gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"</DIV>
<DIV> </DIV>
<DIV>On 02/10/2014 01:41 PM, Steve Borho wrote:</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> On Mon, Feb 10, 2014 at 1:46 PM, dave <dtyx265@gmail.com </DIV>
<DIV>> <mailto:dtyx265@gmail.com>> wrote:</DIV>
<DIV>></DIV>
<DIV>> On 02/10/2014 10:41 AM, Steve Borho
wrote:</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> On Thu, Jan 30, 2014 at 12:31 PM, Steve
Borho <steve@borho.org</DIV>
<DIV>>> <mailto:steve@borho.org>>
wrote:</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> On Wed, Jan 29,
2014 at 5:13 PM, dave <dtyx265@gmail.com</DIV>
<DIV>>>
<mailto:dtyx265@gmail.com>> wrote:</DIV>
<DIV>>></DIV>
<DIV>>>
Hi All,</DIV>
<DIV>>></DIV>
<DIV>>>
I would like to offer my services and contribute to x265</DIV>
<DIV>>>
development. From the wiki it looks like there are</DIV>
<DIV>>>
plenty things to do but I don't want to duplicate or</DIV>
<DIV>>>
interfere with the work of anyone else so if someone can</DIV>
<DIV>>>
give me something to do I would appreciate it. I am open</DIV>
<DIV>>>
to anything needed by x265, both c/c++ and assembly work</DIV>
<DIV>>>
though I don't mind being given something simple just to</DIV>
<DIV>>>
get started. You can find me in the x265 irc channel as</DIV>
<DIV>>>
dtyx265.</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> Hi Dave.</DIV>
<DIV>>></DIV>
<DIV>>> I've been
collecting the more pressing TODO items in the</DIV>
<DIV>>> bitbucket
repository's issue tracker:</DIV>
<DIV>>>
https://bitbucket.org/multicoreware/x265/issues?status=new&status=open</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> #21 (enabling the
VUI message) is the most pressing of the</DIV>
<DIV>>> "simple"
problems. That would be a great place to start.</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> Hi Dave,</DIV>
<DIV>>></DIV>
<DIV>>> How are things going on this front?</DIV>
<DIV>>></DIV>
<DIV>>> -- </DIV>
<DIV>>> Steve Borho</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>>
_______________________________________________</DIV>
<DIV>>> x265-devel mailing list</DIV>
<DIV>>> x265-devel@videolan.org
<mailto:x265-devel@videolan.org></DIV>
<DIV>>>
https://mailman.videolan.org/listinfo/x265-devel</DIV>
<DIV>> I studied the VUI in the h265 spec, appendix E
and have been</DIV>
<DIV>> studying the x265 code from your suggested
starting point,</DIV>
<DIV>> setVuiParametersPresentFlag(). It looks
like most fields are set</DIV>
<DIV>> to spec defaults. Some look like values
that can be options</DIV>
<DIV>> specified by the user, others look like values
that are calculated</DIV>
<DIV>> from encoding a video.</DIV>
<DIV>></DIV>
<DIV>> Can you tell me more about just what pts and
dts are? I</DIV>
<DIV>> understand generally what they are but it
seems like there are a</DIV>
<DIV>> few places in the VUI where they might play a
role in calculating</DIV>
<DIV>> values. I haven't had a chance yet to
compare to x264 code yet so</DIV>
<DIV>> if it all becomes obvious there then I will
get it.</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> pts is the presentation time stamp of a frame, the point at which it
</DIV>
<DIV>> is supposed to be displayed by the decoder.</DIV>
<DIV>></DIV>
<DIV>> dts is the decode time stamp of a frame, the point when the decoder is
</DIV>
<DIV>> supposed to begin decoding it.</DIV>
<DIV>></DIV>
<DIV>> Both are usually specified in units of the frame rate. Since the
pts </DIV>
<DIV>> & dts are frame parameters and the VUI is a stream parameter, I
don't </DIV>
<DIV>> they are directly related, except that the denominator is likely
</DIV>
<DIV>> signaled in some way.</DIV>
<DIV>></DIV>
<DIV>> I tried to create a user account on bitbucket
so I could have</DIV>
<DIV>> issue 21 assigned to me but I keep
getting</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> BB might not allow issues to be assigned to users who don't have push
</DIV>
<DIV>> access anyway, so don't be too concerned about this. You can add
a </DIV>
<DIV>> comment to the issue stating you are working on it. Patches
should go </DIV>
<DIV>> through this mailing list anyway.</DIV>
<DIV>></DIV>
<DIV>> --</DIV>
<DIV>> Steve</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> x265-devel mailing list</DIV>
<DIV>> x265-devel@videolan.org</DIV>
<DIV>> https://mailman.videolan.org/listinfo/x265-devel</DIV>
<DIV>I think the denominator that you are looking for is already set in class
</DIV>
<DIV>TimingInfo. vui_num_units_in_tick(confusingly named, if I understand
it </DIV>
<DIV>correctly) and vui_time_scale are set based on frame rate. The other
</DIV>
<DIV>TimingInfo members that are not set depend on the consistency of timing
</DIV>
<DIV>of the frames.</DIV>
<DIV> </DIV>
<DIV>One other possibility is the hrd parameter m_tickDivisorMinus2. It is
</DIV>
<DIV>set to 100 - 2 in TComSPS::setHrdParameters though given the description
</DIV>
<DIV>of tic_divisor_minus2 in the spec I am not sure if this is an accurate
</DIV>
<DIV>or useful value.</DIV>
<DIV> </DIV>
<DIV>Since it looks like currently no VUI is generated, perhaps I should just
</DIV>
<DIV>add what's needed so a VUI can optionally be added to an encoded video
</DIV>
<DIV>along with filling out the rest of the VUI's fields.</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL:
<http://mailman.videolan.org/pipermail/x265-devel/attachments/20140210/de2e0d61/attachment-0001.html></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 2</DIV>
<DIV>Date: Tue, 11 Feb 2014 08:32:39 +0530</DIV>
<DIV>From: Deepthi Nandakumar <deepthi@multicorewareinc.com></DIV>
<DIV>To: Development for x265 <x265-devel@videolan.org></DIV>
<DIV>Subject: Re: [x265] I would like to contribute to x265</DIV>
<DIV>Message-ID:</DIV>
<DIV><CAAEo3uiSdFneptWqs8b01UxWUm5fzMGp4t-Jr0uxjDYqr36_6w@mail.gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"</DIV>
<DIV> </DIV>
<DIV>Hi,</DIV>
<DIV> </DIV>
<DIV>Can you take a look at what the following does? Does the decoder
actually</DIV>
<DIV>detect HRD parameters?</DIV>
<DIV> </DIV>
<DIV># HG changeset patch</DIV>
<DIV># User Deepthi Nandakumar <deepthi@multicorewareinc.com></DIV>
<DIV># Date 1387524067 -19800</DIV>
<DIV># Node ID 3e794e059f7ffe0edaaf5432df5297631a0f44f6</DIV>
<DIV># Parent 8133378e225020dbdd747d42a021588bef679ec3</DIV>
<DIV>Enable VUI</DIV>
<DIV> </DIV>
<DIV>diff -r 8133378e2250 -r 3e794e059f7f source/encoder/encoder.cpp</DIV>
<DIV>--- a/source/encoder/encoder.cpp Thu Dec 19 17:47:16 2013
+0530</DIV>
<DIV>+++ b/source/encoder/encoder.cpp Fri Dec 20 12:51:07 2013
+0530</DIV>
<DIV>@@ -1367,13 +1367,13 @@</DIV>
<DIV> m_bUseASR = false; // adapt search range based on
temporal distances</DIV>
<DIV> m_recoveryPointSEIEnabled = 0;</DIV>
<DIV> m_bufferingPeriodSEIEnabled = 0;</DIV>
<DIV>- m_pictureTimingSEIEnabled = 0;</DIV>
<DIV>+ m_pictureTimingSEIEnabled = 1;</DIV>
<DIV> m_displayOrientationSEIAngle = 0;</DIV>
<DIV> m_gradualDecodingRefreshInfoEnabled = 0;</DIV>
<DIV> m_decodingUnitInfoSEIEnabled = 0;</DIV>
<DIV> m_useScalingListId = 0;</DIV>
<DIV> m_activeParameterSetsSEIEnabled = 0;</DIV>
<DIV>- m_vuiParametersPresentFlag = false;</DIV>
<DIV>+ m_vuiParametersPresentFlag = true;</DIV>
<DIV> m_minSpatialSegmentationIdc = 0;</DIV>
<DIV> m_aspectRatioIdc = 0;</DIV>
<DIV> m_sarWidth = 0;</DIV>
<DIV>diff -r 8133378e2250 -r 3e794e059f7f source/encoder/frameencoder.cpp</DIV>
<DIV>--- a/source/encoder/frameencoder.cpp Thu Dec 19 17:47:16
2013 +0530</DIV>
<DIV>+++ b/source/encoder/frameencoder.cpp Fri Dec 20 12:51:07
2013 +0530</DIV>
<DIV>@@ -136,7 +136,7 @@</DIV>
<DIV> m_sps.setNumLongTermRefPicSPS(0);</DIV>
<DIV> if (m_cfg->getPictureTimingSEIEnabled()
||</DIV>
<DIV>m_cfg->getDecodingUnitInfoSEIEnabled())</DIV>
<DIV> {</DIV>
<DIV>-
m_sps.setHrdParameters(m_cfg->param.frameRate, 0,</DIV>
<DIV>m_cfg->param.rc.bitrate, m_cfg->param.bframes > 0);</DIV>
<DIV>+
m_sps.setHrdParameters(m_cfg->param.frameRate, 1,</DIV>
<DIV>m_cfg->param.rc.bitrate, m_cfg->param.bframes > 0);</DIV>
<DIV> }</DIV>
<DIV> if (m_cfg->getBufferingPeriodSEIEnabled()
||</DIV>
<DIV>m_cfg->getPictureTimingSEIEnabled() ||</DIV>
<DIV>m_cfg->getDecodingUnitInfoSEIEnabled())</DIV>
<DIV> {</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>Deepthi</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>On Tue, Feb 11, 2014 at 7:14 AM, dave <dtyx265@gmail.com>
wrote:</DIV>
<DIV> </DIV>
<DIV>> On 02/10/2014 01:41 PM, Steve Borho wrote:</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> On Mon, Feb 10, 2014 at 1:46 PM, dave <dtyx265@gmail.com>
wrote:</DIV>
<DIV>></DIV>
<DIV>>> On 02/10/2014 10:41 AM, Steve Borho wrote:</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> On Thu, Jan 30, 2014 at 12:31 PM, Steve Borho
<steve@borho.org> wrote:</DIV>
<DIV>>></DIV>
<DIV>>>></DIV>
<DIV>>>></DIV>
<DIV>>>></DIV>
<DIV>>>> On Wed, Jan 29, 2014 at 5:13 PM, dave
<dtyx265@gmail.com> wrote:</DIV>
<DIV>>>></DIV>
<DIV>>>>> Hi All,</DIV>
<DIV>>>>></DIV>
<DIV>>>>> I would like to offer my services and contribute to x265
development.</DIV>
<DIV>>>>> From the wiki it looks like there are plenty things
to do but I don't want</DIV>
<DIV>>>>> to duplicate or interfere with the work of anyone else so
if someone can</DIV>
<DIV>>>>> give me something to do I would appreciate it. I am
open to anything</DIV>
<DIV>>>>> needed by x265, both c/c++ and assembly work though I
don't mind being</DIV>
<DIV>>>>> given something simple just to get started. You can
find me in the x265</DIV>
<DIV>>>>> irc channel as dtyx265.</DIV>
<DIV>>>></DIV>
<DIV>>>></DIV>
<DIV>>>> Hi Dave.</DIV>
<DIV>>>></DIV>
<DIV>>>> I've been collecting the more pressing TODO items in the
bitbucket</DIV>
<DIV>>>> repository's issue tracker:</DIV>
<DIV>>>>
https://bitbucket.org/multicoreware/x265/issues?status=new&status=open</DIV>
<DIV>>>></DIV>
<DIV>>>> #21 (enabling the VUI message) is the most pressing of
the "simple"</DIV>
<DIV>>>> problems. That would be a great place to start.</DIV>
<DIV>>>></DIV>
<DIV>>></DIV>
<DIV>>> Hi Dave,</DIV>
<DIV>>></DIV>
<DIV>>> How are things going on this front?</DIV>
<DIV>>></DIV>
<DIV>>> --</DIV>
<DIV>>> Steve Borho</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> x265-devel mailing
listx265-devel@videolan.orghttps://mailman.videolan.org/listinfo/x265-devel</DIV>
<DIV>>></DIV>
<DIV>>> I studied the VUI in the h265 spec, appendix E and have been
studying</DIV>
<DIV>>> the x265 code from your suggested starting point,</DIV>
<DIV>>> setVuiParametersPresentFlag(). It looks like most fields are
set to spec</DIV>
<DIV>>> defaults. Some look like values that can be options
specified by the user,</DIV>
<DIV>>> others look like values that are calculated from encoding a
video.</DIV>
<DIV>>></DIV>
<DIV>>> Can you tell me more about just what pts and dts are? I
understand</DIV>
<DIV>>> generally what they are but it seems like there are a few places
in the VUI</DIV>
<DIV>>> where they might play a role in calculating values. I
haven't had a chance</DIV>
<DIV>>> yet to compare to x264 code yet so if it all becomes obvious there
then I</DIV>
<DIV>>> will get it.</DIV>
<DIV>>></DIV>
<DIV>></DIV>
<DIV>> pts is the presentation time stamp of a frame, the point at
which it is</DIV>
<DIV>> supposed to be displayed by the decoder.</DIV>
<DIV>></DIV>
<DIV>> dts is the decode time stamp of a frame, the point when the
decoder is</DIV>
<DIV>> supposed to begin decoding it.</DIV>
<DIV>></DIV>
<DIV>> Both are usually specified in units of the frame rate.
Since the pts &</DIV>
<DIV>> dts are frame parameters and the VUI is a stream parameter, I don't
they</DIV>
<DIV>> are directly related, except that the denominator is likely signaled
in</DIV>
<DIV>> some way.</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>>> I tried to create a user account on bitbucket so I could
have issue 21</DIV>
<DIV>>> assigned to me but I keep getting</DIV>
<DIV>>></DIV>
<DIV>></DIV>
<DIV>> BB might not allow issues to be assigned to users who don't have
push</DIV>
<DIV>> access anyway, so don't be too concerned about this. You can add
a comment</DIV>
<DIV>> to the issue stating you are working on it. Patches should go
through this</DIV>
<DIV>> mailing list anyway.</DIV>
<DIV>></DIV>
<DIV>> --</DIV>
<DIV>> Steve</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> x265-devel mailing
listx265-devel@videolan.orghttps://mailman.videolan.org/listinfo/x265-devel</DIV>
<DIV>></DIV>
<DIV>> I think the denominator that you are looking for is already set
in class</DIV>
<DIV>> TimingInfo. vui_num_units_in_tick(confusingly named, if I
understand it</DIV>
<DIV>> correctly) and vui_time_scale are set based on frame rate. The
other</DIV>
<DIV>> TimingInfo members that are not set depend on the consistency of
timing of</DIV>
<DIV>> the frames.</DIV>
<DIV>></DIV>
<DIV>> One other possibility is the hrd parameter m_tickDivisorMinus2.
It is set</DIV>
<DIV>> to 100 - 2 in TComSPS::setHrdParameters though given the description
of</DIV>
<DIV>> tic_divisor_minus2 in the spec I am not sure if this is an accurate
or</DIV>
<DIV>> useful value.</DIV>
<DIV>></DIV>
<DIV>> Since it looks like currently no VUI is generated, perhaps I should
just</DIV>
<DIV>> add what's needed so a VUI can optionally be added to an encoded
video</DIV>
<DIV>> along with filling out the rest of the VUI's fields.</DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> x265-devel mailing list</DIV>
<DIV>> x265-devel@videolan.org</DIV>
<DIV>> https://mailman.videolan.org/listinfo/x265-devel</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL:
<http://mailman.videolan.org/pipermail/x265-devel/attachments/20140211/eee98c0b/attachment.html></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Subject: Digest Footer</DIV>
<DIV> </DIV>
<DIV>_______________________________________________</DIV>
<DIV>x265-devel mailing list</DIV>
<DIV>x265-devel@videolan.org</DIV>
<DIV>https://mailman.videolan.org/listinfo/x265-devel</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>End of x265-devel Digest, Vol 9, Issue 39</DIV>
<DIV>*****************************************</DIV>
<DIV> </DIV>
<DIV> </DIV></DIV></BODY></HTML>