Closed GoogleCodeExporter closed 9 years ago
Attached is a screencap of the glitch
Original comment by CantStop...@gmail.com
on 22 Mar 2013 at 6:24
Attachments:
thanks for the report! i can repro and will have a look...
Original comment by pascal.m...@gmail.com
on 22 Mar 2013 at 8:18
https://gerrit.chromium.org/gerrit/46374 should fix this.
Thanks for noticing! This was a long-standing bug where the saturation of
quantized coeffs was
done at the wrong place. Normally, one wouldn't see the difference, and just
wrongly assess the score
for a mode. But for low methods (-m 0 or -m 1) we don't change the decision and
force some
mode without possibly changing them. Hence these 'wrong' mode were picked
nevertheless, using
wrong saturation.
Original comment by pascal.m...@gmail.com
on 24 Mar 2013 at 3:57
This fix:
3c8eb9a fix bad saturation order in QuantizeBlock
is available in 0.3.0.
Original comment by jz...@google.com
on 3 Apr 2013 at 6:49
Original issue reported on code.google.com by
CantStop...@gmail.com
on 22 Mar 2013 at 6:22Attachments: