1. 16 Aug, 2017 1 commit
    • paulwilkins's avatar
      Fix for encoder slowdown (for speeds >= 3) · e15be302
      paulwilkins authored
      Some clips in nightly unit test exhibiting significant encoder slowdown which
      appears to bisect to Change-Id: I692311a709ccdb6003e705103de9d05b59bf840a.
      The above change allowed for emergency iterations of the recode loop and
      adjustment of the Q range if there is a large rate miss.
      This patch disables the above adaptation for cases of cpu_speed >= 3 or more
      specifically where cpi->sf.recode_loop >= ALLOW_RECODE_KFARFGF.
      For speeds >= 3 the code does not currently run a dummy bit pack operation
      inside the recode loop. Without this dummy pack operation there is no up to
      date estimate of the current frame's size to use as a basis for assessing the
      requirement for a recode. In practice it was using the previous frames size (or 0
      for the first frame) which could cause odd behavior.
      If we require the emergency rate correction added in  Change-Id: I6923.. for
      the higher speed settings it will be necessary to enable the dummy pack
      which will in turn hurt encode speed.
      Change-Id: I4fb3c6062ca9508325a6f31582f8e80f1a9b126f
  2. 03 Aug, 2017 1 commit
  3. 02 Aug, 2017 7 commits
    • Yunqing Wang's avatar
      Force the bit exactness in the first pass · bfd0f41f
      Yunqing Wang authored
      Originally, for the purpose of keeping a fast first pass, the first-pass
      stats between row_mt_mode = 0 and row_mt_mode = 1 are not bit exact, but
      that difference is very small that doesn't cause a mismatch between the
      final bitstreams. However, if the encoder changes, this minor difference
      may cause a mismatch. Thus, this patch always forces the first pass to
      be bit exact.
      Change-Id: I2b67cf529dee81f660f9d9e7fe9a60ea3c7b12b8
    • Johann Koenig's avatar
    • Marco's avatar
      vp8: Drop due to overshoot for non-screen content. · b9577e07
      Marco authored
      For 1 pass CBR mode:
      Apply the logic for dropping (and re-adjusting rate control)
      due to large overshoot to the case of non-screen content when
      drop_frames_allowed is enabled.
      For the non-screen content case: add additional condition that
      rate correction factor is close to minimum state, and flag to
      constrain the frequency of the dropping.
      Also handle the case of temporal layers and multi-res encoding.
      Add some flags/counters to the layer context for temporal layers.
      For multi-res: drop due to overshoot is checked on lowest stream,
      and if overshoot is detected we force drops on all upper streams
      for that frame.
      This feature is to avoid large frame sizes on big content
      changes following low content period.
      No change in behavior for screen_content_mode = 2.
      Change-Id: I797ab236cbbf3b15cad439e9a227fbebced632e6
    • Scott LaVarnway's avatar
    • Johann's avatar
      quantize test: add speed comparison · 1059b5cc
      Johann authored
      Test some possible scenarios.
      Change-Id: I1a612e7153b31756be66390ceea55877856d5a33
    • Scott LaVarnway's avatar
      vpxdsp: variance_impl_avx2.c cleanup · 632fe828
      Scott LaVarnway authored
      Change-Id: I8d8498009e5ef7bf1137e4ff16ec81738a020b02
    • shiyou yin's avatar
      Merge "loongson mmi configuration patch." · 0e87b160
      shiyou yin authored
  4. 01 Aug, 2017 5 commits
  5. 31 Jul, 2017 7 commits
  6. 30 Jul, 2017 2 commits
  7. 29 Jul, 2017 6 commits
  8. 28 Jul, 2017 7 commits
  9. 27 Jul, 2017 2 commits
  10. 26 Jul, 2017 2 commits