Re: [x265] [Bug]reconstruction yuv picture diff with HM decoder out

2014-02-19 Thread Deepthi Nandakumar
Hi,

We've checked out for hash mismatch for all our hash clips with --rd 2. Can
you share the source that caused a mismatch? That will help us identify the
issue.

Thanks,
Deepthi


On Mon, Feb 17, 2014 at 12:38 PM, z...@rock-chips.com 
z...@rock-chips.comwrote:

  hi, x265 members
 1. [Bug report]
 We found that x265 (version 0.7+2-4b8901ae94ece1ac ) recon yuv data diff
 with HM decode out when config CQP mode with QP=34 and set rd=0 or 1 or 2,I 
 think it's a serious bug!

 with command like this


 --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


 --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

 --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


 2. [Proprose]
  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.


 I'm looking forward to you
 thks
  z...@rock-chips.com

 ___
 x265-devel mailing list
 x265-devel@videolan.org
 https://mailman.videolan.org/listinfo/x265-devel


___
x265-devel mailing list
x265-devel@videolan.org
https://mailman.videolan.org/listinfo/x265-devel


Re: [x265] [Bug]reconstruction yuv picture diff with HM decoder out

2014-02-17 Thread Deepthi Nandakumar
Hi,


On Mon, Feb 17, 2014 at 12:38 PM, z...@rock-chips.com 
z...@rock-chips.comwrote:

  hi, x265 members
 1. [Bug report]
 We found that x265 (version 0.7+2-4b8901ae94ece1ac ) recon yuv data diff
 with HM decode out when config CQP mode with QP=34 and set rd=0 or 1 or 2,I 
 think it's a serious bug!

 with command like this


 --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


 --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

 --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


rd 0 and 1 are not finalised yet. We are investigating the hash mismatch in
rd 2 clip with our clips; would be good if you can share the source.


 2. [Proprose]
  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.


Adaptive Quantization is already implemented. You may use --aq-mode 1
(enabled by default in the medium preset).


 I'm looking forward to you
 thks
  z...@rock-chips.com

 ___
 x265-devel mailing list
 x265-devel@videolan.org
 https://mailman.videolan.org/listinfo/x265-devel


___
x265-devel mailing list
x265-devel@videolan.org
https://mailman.videolan.org/listinfo/x265-devel