1. 05 Dec, 2018 1 commit
  2. 03 Dec, 2018 1 commit
  3. 28 Nov, 2018 2 commits
  4. 25 Nov, 2018 12 commits
  5. 23 Nov, 2018 2 commits
  6. 22 Nov, 2018 1 commit
  7. 21 Nov, 2018 1 commit
  8. 20 Nov, 2018 3 commits
  9. 19 Nov, 2018 1 commit
  10. 18 Nov, 2018 3 commits
  11. 16 Nov, 2018 1 commit
  12. 15 Nov, 2018 1 commit
  13. 14 Nov, 2018 3 commits
    • boyuanxiao-argondesign's avatar
      Segmentation map reference logic · 066b02c2
      boyuanxiao-argondesign authored
      The previous code raised an error if !segmentation.update_map but the
      reference frame didn't yield any segmentation data. (The first "goto
      error" that the patch removes happens if the reference frame was the
      right size but had no segmentation data; the second happens if the
      reference frame was the wrong size).
      
      This doesn't match the logic in the description of
      load_previous_segment_ids in section 6.8.2 of the spec.
      
      This patch allows such streams, allocating and zeroing cur_segmap in
      this case. It is still an error for a stream to signal a temporal
      update but not to have valid segmentation data from the ref frame -
      that's the error case that the patch puts back in.
      066b02c2
    • Ronald S. Bultje's avatar
      Fix segmentation map size check · 0bf59f09
      Ronald S. Bultje authored
      Fixes #166.
      0bf59f09
    • Ronald S. Bultje's avatar
      3fdb6cc9
  14. 13 Nov, 2018 1 commit
  15. 12 Nov, 2018 2 commits
  16. 09 Nov, 2018 1 commit
  17. 08 Nov, 2018 4 commits