- 11 Jun, 2013 - 3 commits
-
-
John Koleszar authored
Don't do the 15 tap filter if there aren't 8 pixels below/right of the edge. Change-Id: I62f16437c1d9ba59b6901a5fe71ddb2f472da344
-
Jingning Han authored
This commit fixed the allowable partition types for bottom-right corner blocks. When a block has over half of its pixels as valid content in both vertical and horizontal directions, allow all the four partition types in the bit-stream. Otherwise, apply partition type constraints. Change-Id: I2252e2de7125a8bfb1c824bf34299a13c81102e3
-
Deb Mukherjee authored
Avoids divide-by-zero when variance is 0. Change-Id: I3c7f526979046ff7d17714ce960fe81d6e1442a0
-
- 10 Jun, 2013 - 28 commits
-
-
John Koleszar authored
-
Deb Mukherjee authored
-
Deb Mukherjee authored
* New probs for subpel filters/tx_count * Makes a change to not reset to defaults for the tx_size probs if an intermediate frame reverts to using a fixed tx_size. * A few updates to the parameters for backward adaptation for mode/mv * some cosmetic cleanups derf300: +0.06% Change-Id: I22994d659bc31ca7a4fc8820fde24001e64a2920
-
John Koleszar authored
-
Dmitry Kovalev authored
This is consistent with uncompressed header encoding. Change-Id: Iccf40a44b493ed36ee085b81ed56f7952cde70a9
-
John Koleszar authored
Remove the bilinear filter mode, and the no-loopfilter mode, and the related vp9_setup_version() function. Change-Id: I32311367812faf37863131df3af37d63d03973d7
-
Jim Bankoski authored
This commit has no impact but to help us debug issues. To Use call like this: vp9_print_modes_and_motion_vectors(cpi->common.mi, cpi->common.mi_rows, cpi->common.mi_cols, cpi->common.current_video_frame, "decode_mi.stt"); Change-Id: I89e27725dae351370eb7f311a20a145ed4f1d041
-
John Koleszar authored
If the codec fails to return a frame on the second frame (as in a VP8 alt-ref, then img will be a null pointer and dereferencing it while trying to write the color format (again) will crash. Change-Id: Ie48710d4c5715f532d453c879c71c20ccdeb81cc
-
John Koleszar authored
Change-Id: I524ba98841f2e1850e3276ac365c501cea31546d
-
John Koleszar authored
-
John Koleszar authored
-
Adrian Grange authored
-
Deb Mukherjee authored
No bitstream change. Removes unused filters and the code for the case of 2 switchable filters; also changes the 8tap-smooth filter coefficients for integer shifts to be interpolating to be consistent with the way it is implemented currently. Change-Id: I96c542fd8c06f4e0df507a645976f58e6de92aae
-
Adrian Grange authored
Implements ability to signal and decode frames that are encoded using only intra coding modes. Only the decode side has been implemented here. Change-Id: I53ac6a8d90422cd08ba389e5236e15b45f9e93de
-
John Koleszar authored
A 32x32 transform should have no internal filtering (check c==4) Change-Id: I7414cf4748ed053208217692ef00cd8b20d49a91
-
John Koleszar authored
Change the argument of get_uv_tx_size() to be an MBMI pointer, so that the correct column's MBMI can be passed to the function. Change-Id: Ied6b8ec33b77cdd353119e8fd2d157811815fc98
-
Paul Wilkins authored
Do not allow the rd code to check compound modes if a segment level reference frame is selected. Change-Id: I95f0c57789e0eaceed7caf227e94b4ba3130a06c
-
Ronald S. Bultje authored
Change-Id: Ib5a95bb6ab643b276df3faa9bf99595e4a69ff18
-
Ronald S. Bultje authored
Change-Id: I3baf93c2fa5c2f7f45c6bc5514d317040975da71
-
John Koleszar authored
-
Ronald S. Bultje authored
-
Jim Bankoski authored
Fixes mvref issue. Change-Id: I07dc1b0682845bc18fe0efa6af5e4f4da3abfa3a
-
Yaowu Xu authored
-
Tero Rintaluoma authored
Fixed point scaling factors are calculated once for each reference frame by using integer division. Otherwise fixed point scaling routines are used in all scaling calculations. This makes it possible to calculate fixed point scaling factors on device driver software and pass them to hardware and thus avoid division on hardware. TODO: - Missing check for maximum frame dimensions (currently scaling uses 14 bits) - Missing check for maximum scaling ratio (upscaling 16:1, downscaling 2:1) Problems: - Straightforward fixed point implementation can cause error +-1 compared to integer division (i.e. in x_step_q4). Should only be an issue for frames larger than 16k. Change-Id: I3cf4dabd610a4dc18da3bdb31ae244ebaf5d579c
-
Janne Salonen authored
Was always using sb_type of first column in a row of 8x8 units when determining decoded block edges as a subcondition for loop filter skipping. Change-Id: Ib17554633a63a90b70cdaa7bed65db035a8ad9d8
-
Yaowu Xu authored
-
Yaowu Xu authored
-
Yaowu Xu authored
-
- 09 Jun, 2013 - 5 commits
-
-
John Koleszar authored
Change-Id: Ifb1ce2bd52147981ca1aec9ec6cfea8738a23e45
-
Ronald S. Bultje authored
-
Ronald S. Bultje authored
-
Ronald S. Bultje authored
-
Ronald S. Bultje authored
-
- 08 Jun, 2013 - 4 commits
-
-
Ronald S. Bultje authored
It seems like I inverted the meaning of the contexts by accident? Change-Id: Iafb2346d9933930949578342b84519b719dd5dd3
-
Ronald S. Bultje authored
Change-Id: Iec41736c2b6140715f90f40de5ae6cf52497a9b8
-
Yaowu Xu authored
-
Ronald S. Bultje authored
Change-Id: Ice8c73a2a843113877b8f8ed78737a1442c25ced
-