summaryrefslogtreecommitdiff
path: root/vp9/encoder/vp9_mcomp.h
diff options
context:
space:
mode:
authorRonald S. Bultje <rbultje@google.com>2012-12-10 12:09:07 -0800
committerRonald S. Bultje <rbultje@google.com>2012-12-12 10:01:19 -0800
commit4d0ec7aacd2227b1b98d1f5100bde64c7797b962 (patch)
tree5e2e16ade1e5a05e66108f43ab992c8632b69fc1 /vp9/encoder/vp9_mcomp.h
parentd1244659757ff64212f7beebc6c8e45909d5113c (diff)
downloadlibvpx-4d0ec7aacd2227b1b98d1f5100bde64c7797b962.tar
libvpx-4d0ec7aacd2227b1b98d1f5100bde64c7797b962.tar.gz
libvpx-4d0ec7aacd2227b1b98d1f5100bde64c7797b962.tar.bz2
libvpx-4d0ec7aacd2227b1b98d1f5100bde64c7797b962.zip
Consistently use get_prob(), clip_prob() and newly added clip_pixel().
Add a function clip_pixel() to clip a pixel value to the [0,255] range of allowed values, and use this where-ever appropriate (e.g. prediction, reconstruction). Likewise, consistently use the recently added function clip_prob(), which calculates a binary probability in the [1,255] range. If possible, try to use get_prob() or its sister get_binary_prob() to calculate binary probabilities, for consistency. Since in some places, this means that binary probability calculations are changed (we use {255,256}*count0/(total) in a range of places, and all of these are now changed to use 256*count0+(total>>1)/total), this changes the encoding result, so this patch warrants some extensive testing. Change-Id: Ibeeff8d886496839b8e0c0ace9ccc552351f7628
Diffstat (limited to 'vp9/encoder/vp9_mcomp.h')
0 files changed, 0 insertions, 0 deletions