- 22 Apr, 2013 3 commits
-
-
John Koleszar authored
Removes the redundant dst pointers from vp9_build_inter_predictors_sb{y,uv} and the remaining mb specific functions. Change-Id: I7b6bf439d9394b85ea79b4fe61a3ffc1025720da
-
Paul Wilkins authored
-
Sami Pietilä authored
-
- 20 Apr, 2013 3 commits
-
-
Dmitry Kovalev authored
Merge "Removing get_segment_id function and using existing vp9_get_pred_mb_segid." into experimental
-
Dmitry Kovalev authored
-
Dmitry Kovalev authored
-
- 19 Apr, 2013 34 commits
-
-
John Koleszar authored
-
John Koleszar authored
-
Yaowu Xu authored
Wherever there are real pixels available before falling back to use assumed values 127 and 129. This also make DC_PRED for i4x4 consistent with DC_PRED for larger blocks. Change-Id: I54372924826118da023f402c802ac6ce0caa70c3
-
John Koleszar authored
-
John Koleszar authored
First in a series of commits moving the framebuffers pointers to per-plane data, so that they can be indexed numerically rather than by name. Change-Id: I6e0d60fd4d51e6375c384eb7321776564df21775
-
Paul Wilkins authored
-
Dmitry Kovalev authored
Change-Id: Iff35d4b2f8f65511f80c594958c01fb4673fa033
-
Paul Wilkins authored
Removed some unused legacy code relating to GF activity. Change-Id: I0b0fe90a1a5208aaa81d7393ba6cf75ab412dbda
-
Yunqing Wang authored
-
Paul Wilkins authored
-
John Koleszar authored
Use the common sb functions instead. Change-Id: I4fa0a8ee3c6ada56271dd09bf895b97642f55858
-
John Koleszar authored
Remove the unnecessary _s_ from their names, and add a new vp9_recon_sb() that calls the y and uv variants. Change-Id: I7ffaa5ff5605a8472cac2a53de8cf889353039a6
-
John Koleszar authored
-
Dmitry Kovalev authored
Change-Id: I55c2688e06ae5d7dfccc1b1983f233ab1c7978db
-
Dmitry Kovalev authored
Change-Id: Ie4713da125e954c1d30e1d4cbeb38666fce90ccc
-
John Koleszar authored
Change-Id: Ic27af09e38af8317ac4743241883d577a44f1490
-
Dmitry Kovalev authored
Change-Id: I03d5b6f22f0930893709c6db5f1b06762ad3354e
-
John Koleszar authored
All build_inter_predictors can now be serviced by the same inner function. Change-Id: I40b08bee8f047286db4b1aad9dcae37b879c3f2a
-
John Koleszar authored
Similar to the prior change that removed the rounding from non-SPLITMV modes. Improves quality by a similar amount (Additional +0.087% on derf) Change-Id: I39d80b4a3037a3aa7e285eb2320346ddaf646f52
-
John Koleszar authored
-
John Koleszar authored
-
Dmitry Kovalev authored
-
Dmitry Kovalev authored
-
Jim Bankoski authored
-
John Koleszar authored
The C code was being used as a fallback for the >16 case, but only for 2D. Change-Id: I1e2e6da9e4b28bd88bde9ba4dd32724ce466cf6f
-
Jim Bankoski authored
Just make sure we don't stop them from testing in speed 1. Change-Id: Iec9b3dba0a32616ff7a451207e0f54b81bb72575
-
Jim Bankoski authored
-
Paul Wilkins authored
Further simplification of mvref search to return only the top two candidates. Distance weights removed as the test order reflects distance anyway. Change-Id: I0518cab7280258fec2058670add4f853fab7b855
-
Jim Bankoski authored
slightly worse results for faster encodes Change-Id: I25ea82a18ce20635dbcd328808c1d05ac1f58fd7
-
Paul Wilkins authored
This experiment has failed to give much benefit but does add complexity so deprecated. Change-Id: Ic7b929ba706390b9907ef0b4f965bd401ca799a4
-
Paul Wilkins authored
void __attribute__((noinline)) hi(void) { } Causes build failure in VS2008 Change-Id: Ie2f2a09d90bd5502c492e4d9f4983532a0edbc01
-
Paul Wilkins authored
As we are no longer able to sort the candidate mvrefs in both encoder and decode and given that the cost of explicit signalling has proved prohibitive, it no longer makes sense to find more than 2 candidates. This patch: Modifies and simplifies add_candidate_mv() Removes the forced addition of a 0 vector in the MAX_MV_REF_CANDIDATES-1 position (in preparation to reducing MAX_MV_REF_CANDIDATES to 2). Re-orders the addition of candidates slightly. This actually gives small gains (circa 0.2% on std-hd) A subsequent patch will remove NEW_MVREF experiment, reduce MAX_MV_REF_CANDIDATES to 2 and remove distance weights as these are implicit now in the order. Change-Id: I3dbe1a6f8a1a18b3c108257069c22a1141a207a4
-
Paul Wilkins authored
-
Paul Wilkins authored
Adjustments take heavier account of the frame near a kf in deciding boost and limit the total number that can contribute. Also adjusted the minq calculations such that in most cases we generate a smaller key frame. Modified the code that accounts for how static the sequence is and added some adjustment based on image size. This is still very crude but smaller images tend to behave better with a larger delta between KF Q and other frames than larger image formats. Changes give sizable gains in overall PSNR on all the test sets but the biggest gains (~3%) were on the std-hd set. The gains were smaller for SSIM but still significant. Average PSNR results are mixed because this metric can very easily be altered by having a very good / lossless coding of one or two frames. Some of the YT and YT-HD clips in particular have blank lead ins and allowing lossless coding of these appears to make a big difference to average PSNR but it reality does not help much at all. Change-Id: I6bfe485a1d330b47c783832f1717c95c535464ec
-