- 25 Feb, 2016 1 commit
-
-
Thomas Davies authored
Change-Id: I080c7449c269054cf441c251acd8930431e94b46
-
- 28 Jan, 2016 1 commit
-
-
Change-Id: Ib8c9eb6263d6eba6b9d7b2e402b7e83a78c86be9
-
- 25 Jan, 2016 1 commit
-
-
Yaowu Xu authored
to vpx_tune_metric and vpx_tune_content. Change-Id: I673aea01075b5241b621af779ca8d3e8d2e6c61c
-
- 08 Dec, 2015 1 commit
-
-
paulwilkins authored
This change has been imported from VP9 and alters the nature and use of exhaustive motion search. Firstly any exhaustive search is preceded by a normal step search. The exhaustive search is only carried out if the distortion resulting from the step search is above a threshold value. Secondly the simple +/- 64 exhaustive search is replaced by a multi stage mesh based search where each stage has a range and step/interval size. Subsequent stages use the best position from the previous stage as the center of the search but use a reduced range and interval size. For example: stage 1: Range +/- 64 interval 4 stage 2: Range +/- 32 interval 2 stage 3: Range +/- 15 interval 1 This process, especially when it follows on from a normal step search, has shown itself to be almost as effective as a full range exhaustive search with step 1 but greatly lowers the computational complexity such that it can be used in some cases for speeds 0-2. This patch also removes a double exhaustive search for sub 8x8 blocks which also contained a bug (the two searches used different distortion metrics). For best quality in my test animation sequence this patch has almost no impact on quality but improves encode speed by more than 5X. Restricted use in good quality speeds 0-2 yields significant quality gains on the animation test of 0.2 - 0.5 db with only a small impact on encode speed. On most natural video clips, however, where the step search is performing well, the quality gain and speed impact are small. Change-Id: Iac24152ae239f42a246f39ee5f00fe62d193cb98
-
- 09 Nov, 2015 1 commit
-
-
Johann authored
Javan Whistling Duck release. Change-Id: If44c9ca16a8188b68759325fbacc771365cb4af8
-
- 10 Sep, 2015 3 commits
-
-
Jingning Han authored
This condition is not effectively in use. The actual reference frame masking is done in other route. Change-Id: Ia59c843bcac7243dada92f0f67658d7ce43df5e8
-
Jingning Han authored
Change-Id: Ic39d4523e78863c816b0fc85f56ea5ae5e0b3310
-
Jingning Han authored
Take out speed features that affect the compression performance to simplify the coding route. This commit removes the motion field mode search used in speed 3. Change-Id: Ifdf6862cb1ece8261125a56d9d89bcef60758c00
-
- 31 Aug, 2015 1 commit
-
-
Johann authored
Change-Id: I2e387a06484a06301f3cd6600c4ba2f4335b61ee
-
- 28 Aug, 2015 1 commit
-
-
Yunqing Wang authored
Spatial/temporal svc code was removed. Verified using Borg test, and the results before and after the change are matching. Change-Id: I4c2ee5cd560428e3e50be02e57e5871ef4246390
-
- 27 Aug, 2015 1 commit
-
-
James Zern authored
prevents redeclaration warnings; vp8 has its own define which will be resolved in a future commit Change-Id: Ic941fef3dd4262fcdce48b73075fe6b375f11c9c
-
- 26 Aug, 2015 1 commit
-
-
Yunqing Wang authored
Code cleanup. Change-Id: I668bd5a4e5fbe96969d51d9ee777fc5f1d8abfe6
-
- 17 Aug, 2015 1 commit
-
-
hui su authored
Change-Id: Id691d8a9d4aa137e8de73fe680016fd4fd070e6e
-
- 13 Aug, 2015 2 commits
- 12 Aug, 2015 2 commits
-
-
Jingning Han authored
Remove the vp9_ prefix from vp10 file names. Change-Id: I513a211b286a57d6126fc1b0fbfd6405120014f1
-
Jingning Han authored
This commit folks the VP9 and VP10 codebase and makes libvpx support VP8, VP9, and VP10. Change-Id: I81782e0b809acb3c9844bee8c8ec8f4d5e8fa356
-
- 11 Aug, 2015 1 commit
-
-
Marco authored
For speed 7, real-time mode: Base layer frames are further apart (for #temporal layers = 3, this is every 4 frames) so worth keeping same motion search parameters (as in speed 6) on the base layer frames. Change-Id: Idebf49dda6ef4f3d9a55aee55129a68253f692fb
-
- 31 Jul, 2015 1 commit
-
-
Alex Converse authored
This got erroneously changed during the refactor. This fixes SvcTest.TwoPassEncode2TemporalLayersWithMultipleFrameContextsAndTiles. Change-Id: Ifa5ab0e098396c5e2d10478db87df256eadfa4c7
-
- 30 Jul, 2015 1 commit
-
-
Alex Converse authored
Change-Id: I8877025e172fff29bc4e270790211463b676b4d7
-
- 16 Jul, 2015 1 commit
-
-
paulwilkins authored
Fix bug in setting this flag for animated content. The bug did cause quality to increase because far more frames are not boosted than boosted. However, the speed trade off to gain is a lot less favorable and the behavior was not as intended. Change-Id: I89fb70419c88b26f40b3534de0481730a1b3fcfa
-
- 08 Jul, 2015 2 commits
-
-
paulwilkins authored
Changes to allow more use of rectangular partitions at speeds 1 and 2 for content classed by the first pass as animation and for blocks near the active image edge. This has quite a big impact in quality for the animated test sequence but also hurts encode speed for speed 2. For other content types the impact on both speed and quality is small. Added some plumbing for detection of internal vertical image edges. Change-Id: I3fc48de2349f8cb87946caaf0b06dbb0ea261a9a
-
paulwilkins authored
Change speed features / behavior for split mode when there is an internal active edge (e.g. formatting bars). Remove some threshold constraints in rd code near the active edge of the image. Add some plumbing for left and right active edge detection. Patch set 5. Limit rd pass through for sub 8x8 to internal active edges. This takes away any speed penalty for most clips but keeps the enhanced edge coding for the more critical case of internal image edges Change-Id: If644e4762874de4fe9cbb0a66211953fa74c13a5
-
- 09 Jun, 2015 1 commit
-
-
Paul Wilkins authored
For content that is identified as likely to contain some animation or graphics content, increase the availability of split modes for good quality speeds 1-3. On a problem test animation clip this improves metrics results by about 0.25 db and makes a noticeable difference visually. It also causes a small drop in file size (~0.5%) but a rise in encode time of about 5-6% at speed 2. For more normal content it should have no effect. Change-Id: Ic4cd9a8de065af9f9402f4477a17442aebf0e439
-
- 05 Jun, 2015 1 commit
-
-
Marco authored
For real-time mode: keep reference_frame masking off for spatial svc. Change-Id: I15e123c06f67ea040172b8d4042a672f3525b9d8
-
- 04 Jun, 2015 1 commit
-
-
Paul Wilkins authored
Adds code to detect dead zone bars at the top and bottom of reformatted letterbox video (note that the code only looks at the top of the image and assumes any dead zone is symmetrical). Use of this to adapt rate control etc. will follow in a subsequent patch. Also counts other blocks (excluding the dead zone) that have no intra signal. The presence of a significant number of such blocks can be used as a identify that the frame may be artificial (e.g. animation, screen capture, graphics). This patch contains plumbing only and does not use the signal. Change-Id: I59bc93529cd4065416cef773e405fda3ae006a20
-
- 15 May, 2015 1 commit
-
-
Marco authored
Use the same settting as in speed >=6. This will use same logic for tx_size selecton as in speed >=6, which limits the transform size and reduces ringing artifact. Also metrics go up on average with this change: ~2% for PSNR, ~10% for SSIM. Change-Id: Ia2d50db236ae1cc72f742bfa6c9ec5ea50ff0e0a
-
- 04 May, 2015 1 commit
-
-
Marco authored
For non-rd mode (speed >=5): use mask based on prediction block size, and (for non-screen content mode) allow for checking horiz and vert intra modes for blocks sizes < 16x16. Avg psnr/ssim metrics go up by about ~0.2%. Only allowing H/V intra on block sizes below 16x16 for now, to keep encoding time increase very small, and also when allowing H/V on 16x16 blocks, metrics went down on a few clips which need to be further examined. Change-Id: I8ae0bc8cb2a964f9709612c76c5661acaab1381e
-
- 01 May, 2015 2 commits
-
-
paulwilkins authored
Impose a limit on the rd auto partition search based on the image format. Smaller formats require that the search includes includes a smaller minimum block size. This change is intended to mitigate the visual impact of ringing in some problem clips, for smaller image formats. Change-Id: Ie039e5f599ee079bbef5d272f3e40e2e27d8f97b
-
paulwilkins authored
Remove one of the auto partition size cases. This case can behaves badly in some types of animated content and was only used for the rd encode path. A subsequent patch will add additional checks to help further improve visual quality. Change-Id: I0ebd8da3d45ab8501afa45d7959ced8c2d60ee4e
-
- 27 Mar, 2015 1 commit
-
-
Marco authored
Metrics on RTC set go down by ~1.5% on average. Key frame encoding time goes down by factor of ~5. Change-Id: Ia83acc55848613870e5ac6efe7f3d904d877febb
-
- 10 Feb, 2015 1 commit
-
-
Adrian Grange authored
Note: This feature is still in development. Add an option for the encoder to decide the resolution at which to encode each frame. Each KF/GF/ARF goup is tested to see if it would be better encoded at a lower resolution. At present, each KF/GF/ARF is coded first at full-size and if the coded size exceeds a threshold (twice target data rate) at the maximum active Q then the entire group is encoded at lower resolution. This feature is enabled in vpxenc by setting: --resize-allowed=1 In addition, if the vpxenc command line also specifies valid frame dimensions using: --resize-width=XXXX & --resize_height=YYYY then *all* frames will be encoded at this resolution. Change-Id: I13f341e0a82512f9e84e144e0f3b5aed8a65402b
-
- 03 Feb, 2015 2 commits
-
-
Jim Bankoski authored
Remove loop filter skip at speed 7+ because of bad visual artifacts and up the postprocessing. Change-Id: Ibdd0bac71aaee232d2bb2e14462733c51517768d
-
Yaowu Xu authored
1. Adjusted the threshold for coef update computation based on counts of tx used, avoid coef update computation when count is low (<20) 2. Move sf->lpf_pick = LPF_PICK_MINIMAL_LPF to speed 8. Change-Id: I02b44309e40fcdbf135c7934ae067a3f42502d30
-
- 23 Jan, 2015 1 commit
-
-
Adrian Grange authored
Change-Id: I78ef7f89586a329787f6bc4c58ec83af210989a3
-
- 17 Dec, 2014 1 commit
-
-
Yaowu Xu authored
This commit removes undefined value options of cpu-used for VP9 and changed vpxenc prompt to reflect the usable range of [-8,8] Change-Id: Ib80fef3dbb6ec9aabac45ed13e8ab6fbaf94f55e
-
- 05 Dec, 2014 2 commits
-
-
Jingning Han authored
These speed-up features for key frame coding are only turned on in the settings of hybrid non-RD and RD mode decision. It provides about 20% speed-up to the hybrid key frame coding at the expense of certain compression performance loss. For vidyo1, the key frame coding statistics are changed 9838F, 35.020 dB, 61677 us -> 9920F, 34.834 dB, 47556 us Overall rtc set compression performance is down by -0.257%. Change-Id: I0025447fda26bb7855e982955642b5f55d71b51f
-
Jingning Han authored
When block size is below 16x16, the encoder swap from non-RD to RD mode for key frame coding. This largely brough back the key frame compression performance. For vidyo1 at 1000 kbps, the key frame coding statistics are changed 9978F, 34.183 dB, 36807 us -> 9838F, 35.020 dB, 61677 us As compared to the full RD case 7187F, 34.930 dB, 214470 us The overall rtc set coding performance (single key frame setting) is improved by 1.5%. Change-Id: I78a4ecf025d7b24ec911e85be94e01da05e77878
-
- 03 Dec, 2014 2 commits
-
-
Marco authored
For key frame at speed 6: enable the non-rd mode selection in speed setting and use the (non-rd) variance_based partition. Adjust some logic/thresholds in variance partition selection for key frame only (no change to delta frames), mainly to bias to selecting smaller prediction blocks, and also set max tx size of 16x16. Loss in key frame quality (~0.6-0.7dB) compared to rd coding, but speeds up key frame encoding by at least 6x. Average PNSR/SSIM metrics over RTC clips go down by ~1-2% for speed 6. Change-Id: Ie4845e0127e876337b9c105aa37e93b286193405
-
Jingning Han authored
This commit reworks the ONE_LOOP_REDUCED coefficient probability model update process. It allows model update for every coefficient across the spectrum at a coarser resolution, instead of performing precise update only for certain subset of probability models. The overall runtime remains nearly same (<1% change) for speed -6. The compression performance is improved by 7.5% in PSNR for speed -5 and 4.57% for speed -6, respectively. Change-Id: Ifb17136382ee7e39a9f34ff4a4f09a753125c8d1
-