1. 16 Oct, 2018 1 commit
  2. 12 Oct, 2018 1 commit
  3. 11 Oct, 2018 1 commit
  4. 04 Oct, 2018 3 commits
  5. 02 Oct, 2018 3 commits
  6. 01 Oct, 2018 1 commit
  7. 28 Sep, 2018 3 commits
  8. 26 Sep, 2018 1 commit
  9. 20 Sep, 2018 1 commit
  10. 19 Sep, 2018 1 commit
  11. 17 Sep, 2018 1 commit
  12. 14 Sep, 2018 1 commit
  13. 13 Sep, 2018 2 commits
    • Yan Zhang's avatar
      High precision mv storage · f3c52a4a
      Yan Zhang authored
      Motion vecotrs are always stored with 1/16-pel precision; highprec flag,
      setlowPrec() and sethighPrec() functions are removed from the MV class; SPS flag
      indicate whether high precision motion vector is used is also removed.
      The following strategies are followed:
      
      1. Motion vector data in the buffer are always stored in high precision.
      
      2. Motion vector used for motion compensation are always in high
      precision.
      
      3. Motion vector difference data are always in low precision.
      
      4. Encoder side motion estimation always use low precision.
      
      5. Motion vector bits calculation are always performed in low precision.
      
      6. Candidates of motion vector prediction list are always in low
      precision.
      f3c52a4a
    • Karsten Suehring's avatar
      fix maximum ternary split size as reported in issue #87 · acf8643e
      Karsten Suehring authored
      Uses option #1 re-defining the meaning of maxTtSize being the longest side of the partition.
      acf8643e
  14. 11 Sep, 2018 1 commit
  15. 10 Sep, 2018 1 commit
  16. 08 Sep, 2018 2 commits
  17. 07 Sep, 2018 1 commit
    • Yan Zhang's avatar
      1/16-pel motion vector storage · 9dc004f9
      Yan Zhang authored
      Motion vecotrs are always stored with 1/16-pel precision and the High
      precision motion vector SPS flags are removed.
      
      The following strategies are followed:
      
      1. Motion vector data in the buffer are always stored in high precision.
      2. Motion vector used for motion compensation are always in high
      precision.
      3. Motion vector difference data are always in low precision.
      4. Encoder side motion estimation always use low precision.
      5. Motion vector bits calculation are always performed in low precision.
      6. Candidates of motion vector prediction list are always in low
      precision.
      9dc004f9
  18. 05 Sep, 2018 3 commits
  19. 04 Sep, 2018 6 commits
  20. 03 Sep, 2018 5 commits
  21. 02 Sep, 2018 1 commit