1. 18 Jul, 2011 1 commit
    • Tero Rintaluoma's avatar
      Fixed rate histogram calculation · fd41cb84
      Tero Rintaluoma authored
      Using small values for --buf-sz= in command line causes
      floating point exception due to division by zero.
      
      Change-Id: Ibfe2d44db922993a78ebc9a4a1087d9625de48ae
      fd41cb84
  2. 14 Jul, 2011 2 commits
  3. 13 Jul, 2011 10 commits
  4. 12 Jul, 2011 3 commits
  5. 11 Jul, 2011 1 commit
  6. 08 Jul, 2011 6 commits
  7. 07 Jul, 2011 2 commits
  8. 01 Jul, 2011 1 commit
  9. 30 Jun, 2011 5 commits
  10. 29 Jun, 2011 8 commits
    • John Koleszar's avatar
      034cea5e
    • Johann's avatar
      guard against space/time distortion · bb0ca87a
      Johann authored
      and divide by 0 errors
      
      Change-Id: I8af5ca3d0913cb6f278fff754f8772bcb62e674a
      bb0ca87a
    • Paul Wilkins's avatar
      Merge "Change to arf boost calculation." · eacaabc5
      Paul Wilkins authored
      eacaabc5
    • Paul Wilkins's avatar
      Change to arf boost calculation. · 11694aab
      Paul Wilkins authored
      In this commit I have added an experimental function
      that tests prediction quality either side of a central position
      to calculate a suggested boost number for an ARF frame.
      
      The function is passed an offset from the current position and
      a number of frames to search forwards and backwards.
      It returns a forward, backward and compound boost number.
      
      The new code can be deactivated using #define NEW_BOOST 0
      
      In its current default state the code searches forwards and backwards
      from the proposed  position of the next alt ref.
      
      The the old code used a boost number calculated by scanning forward
      from the previous GF up to the proposed alt ref frame position.
      
      I have also added some code to try and prevent placement of a gf/arf
      where there is a brief flash.
      
      Change-Id: I98af789a5181148659f10dd5dd2ff2d4250cd51c
      11694aab
    • Johann's avatar
      remove incorrect initialization · fe53107f
      Johann authored
      Values were set, then reset. Only set them once.
      
      Change-Id: Iaf43c8467129f2f261f04fa9188b603aa46216b5
      fe53107f
    • Johann's avatar
      clean up warnings when building arm with rtcd · 6611f669
      Johann authored
      Change-Id: I3683cb87e9cb7c36fc22c1d70f0799c7c46a21df
      6611f669
    • John Koleszar's avatar
      vpxenc: prevent wraparound in the --rate-hist ringbuffer · 05239f0c
      John Koleszar authored
      For clips that are near 60fps and have a lot of alt refs, it's possible
      that the ring buffer holding the previous frames sizes/pts could wrap
      around, leading to a division by zero.
      
      In addition to checking for this condition in the ring buffer loop,
      the buffer size is made dependent on the actual frame rate in use,
      rather than defaulting to 60, which should improve accuracy at frame
      rates >= ~60.
      
      Change-Id: If5a04d6e847316dc5f7504f25c01164cf9332be8
      05239f0c
    • John Koleszar's avatar
  11. 28 Jun, 2011 1 commit