On Fri, Mar 21, 2014 at 8:42 PM, chen <[email protected]> wrote:
At 2014-03-21 13:35:30,[email protected] wrote:
># HG changeset patch
># User Murugan Vairavel <[email protected]>
># Date 1395379187 -19800
># Fri Mar 21 10:49:47 2014 +0530
># Node ID 435e50b2b92c83e10fdb2bd86bc8e8df91b7338b
># Parent 0c4fdd43325e6501698a281862b1c027238a9c9d
>testbench: code for testing input pixel upShift/downShift primitives
>
> /* [0] --- Random values
>@@ -79,16 +83,22 @@
> short_test_buff1[0][i] = rand() & PIXEL_MAX; //
> For block copy only
> short_test_buff2[0][i] = rand() % 16383; //
> for addAvg
> int_test_buff[0][i] = rand() % SHORT_MAX;
>+ ushort_test_buff[0][i] = rand() % ((1 << 10) - 1);
>+ uchar_test_buff[0][i] = rand() % ((1 << 8) - 1);
out code include a clip operator, so you can do more dynamic range to verify
that.
Do you mean to increase the Dynamic range of ushort buffer???
Yes, more dynamic range may verify our CLIP code
_______________________________________________
x265-devel mailing list
[email protected]
https://mailman.videolan.org/listinfo/x265-devel
