- 03 Jan, 2014 - 3 commits
-
-
Dmitry Kovalev authored
Change-Id: I1d50f8701d9c9dedb84387a773a3e9b4daaad720
-
Dmitry Kovalev authored
* changes: Removing CONFIG_MD5. Using VP9_FRAME_MARKER instead of raw number.
-
Dmitry Kovalev authored
Change-Id: Ic0345622115941f49b6a568c7b8154ba892cbf0d
-
- 02 Jan, 2014 - 3 commits
-
-
Christian Duvivier authored
-
Christian Duvivier authored
Change-Id: I951abd4ad0078f78949f3cb79453ac334fb82a7e
-
Yaowu Xu authored
-
- 28 Dec, 2013 - 1 commit
-
-
Dmitry Kovalev authored
We don't need compile time md5 configuration because --md5 is a runtime option. Change-Id: Ic0a2427ae5de5a18f31e5ee60c3732481b377ca1
-
- 27 Dec, 2013 - 6 commits
-
-
Jingning Han authored
-
Dmitry Kovalev authored
Change-Id: I3addbf6d89a86a707c8df1a463da3e9e367910df
-
Dmitry Kovalev authored
-
Yunqing Wang authored
-
Dmitry Kovalev authored
vpx_codec_vp9x_cx is not used internally. Experimental flag from vp9_extracfg is also not really used. YUV 4:4:4 just works after these changes (you have to specify --profile=1 for the encoder). Change-Id: Ib1c8461d0d19d159827e005efe868f891eea0140
-
Jingning Han authored
This commit takes a preliminary attempt to refine the motion search control. It detects the SAD associated with mv predictor per reference frame, and based on which to determine whether the encoder wants to reduce the motion search range (if the predicted mv provides fairly small SAD), or to skip the current reference frame (if there exists another ref frame that gives much smaller SAD cost). This feature is turned on in the settings of speed 1 and above. In speed 1, compression performance changed derf -0.018% yt -0.043% hd -0.045% stdhd -0.281% speed-up pedestrian_area_1080p at 4000 kbps 100 frames 199651ms -> 188846ms (5.5% speed-up) blue_sky_1080p at 6000 kbps 443531ms -> 415239ms (6.3% speed-up) In speed 2, compression performance changed derf -0.026% yt -0.090% hd -0.055% stdhd -0.210% speed-up pedstrian 113949ms -> 108855ms (4.5% speed-up) blue_sky 271057ms -> 257322ms (5% speed-up) Change-Id: I1b74ea28278c94fea329d971d706d573983d...
-
- 26 Dec, 2013 - 2 commits
-
-
Dmitry Kovalev authored
-
Dmitry Kovalev authored
-
- 20 Dec, 2013 - 16 commits
-
-
Dmitry Kovalev authored
Change-Id: I07470ad1b7a0344d088911428ffab8ba9a0d8708
-
Dmitry Kovalev authored
Change-Id: I50c009ff8108bda1c57427f23d63a79c04f7e776
-
Dmitry Kovalev authored
-
Dmitry Kovalev authored
-
Dmitry Kovalev authored
Change-Id: I9b9a5fcce8530284df0f270706ee060a0edc1517
-
Dmitry Kovalev authored
-
Jingning Han authored
-
Marco Paniconi authored
-
Yaowu Xu authored
-
Yunqing Wang authored
-
Paul Wilkins authored
-
James Zern authored
-
Jingning Han authored
Buffer the SSE of prediction residuals in the rate-distortion optimization loop of a given block. This information would be used for later encoding control. Change-Id: If4e63f3462490513c48be9407d3327c8dd438367
-
Dmitry Kovalev authored
Moving all code from that files to vp9_mvref_common.{h, c}. Change-Id: Ibc4afcb8cea6847166ff411130e93611ebe63b20
-
Dmitry Kovalev authored
Moving back to scale_factors struct. We don't need anymore x_offset_q4 and y_offset_q4 because both values are calculated locally inside vp9_scale_mv function. Change-Id: I78a2122ba253c428a14558bda0e78ece738d2b5b
-
- 19 Dec, 2013 - 9 commits
-
-
Dmitry Kovalev authored
-
Marco Paniconi authored
Change-Id: I535bde16c8fc4c2cd263bbbbaed46ead4c776090
-
Dmitry Kovalev authored
Before mv scaling it is required to calculate x_offset_q4/y_offset_q4 by calling set_scaled_offsets(). Now offset configuration can not be missed because it happens just before scale_mv(). Change-Id: I7dd1a85b85811a6cc67c46c9b01e6ccbbb06ce3a
-
Dmitry Kovalev authored
-
Dmitry Kovalev authored
-
Dmitry Kovalev authored
Change-Id: I82ecbe7fe0baa890ce251043f3c7159188c00665
-
Dmitry Kovalev authored
Change-Id: I67d934b6af899ffd4bcad2d913a650685fa64abd
-
Dmitry Kovalev authored
Change-Id: Iba91ff1e797a83517e2cd7c3ab86cba39f39415b
-
Deb Mukherjee authored
-