<!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 members</DIV>
<DIV>1. [Bug report]</DIV>
<DIV>We found that x265 (version 0.7+2-4b8901ae94ece1ac ) recon yuv data diff
with HM decode out when config CQP mode with <SPAN style="COLOR: #ff0000">QP=34
and set rd=0 or 1 or 2,</SPAN> I think it's a serious bug!</DIV>
<DIV> </DIV>
<DIV>with command like this </DIV>
<DIV> </DIV>
<DIV><!--StartFragment -->
<DIV>--input F:\yuv\Samsung_1080p_25.yuv --input-res 1920x1080 --fps 24 -q 34 -o E:\out1.bin -r E:\rec1.yuv --psnr --rd 0<BR><BR>--input F:\yuv\Samsung_1080p_25.yuv --input-res 1920x1080 --fps 24 -q 34 -o E:\out1.bin -r E:\rec1.yuv --psnr --rd 1<BR><BR>--input F:\yuv\Samsung_1080p_25.yuv --input-res 1920x1080 --fps 24 -q 34 -o E:\out1.bin -r E:\rec1.yuv --psnr --rd 2
</DIV>
<DIV> </DIV>
<DIV>2. [Proprose]</DIV>
<DIV>
<DIV>The x265 codec encodes video con-tent using a
fixed quantization step, thus leading to a
variable bitrate stream which may not be
suitable for the many multi-media
applications where a constant bandwidth is
required. Therefore, maybe adaptive quantization step may be
better.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>I'm looking forward to you </DIV></DIV>
<DIV>thks</DIV></DIV>
<DIV>
<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></BODY></HTML>