)]}'
{
  "commit": "1f8fc29cab44dfbd305211bf79b958a5add9634f",
  "tree": "bfed4c66841cb34c03f89cfc56a1a8589d3a8668",
  "parents": [
    "009126128737eddcb8be55ed7f22ec12a1e744f6"
  ],
  "author": {
    "name": "Jingning Han",
    "email": "jingning@google.com",
    "time": "Fri Mar 16 08:54:11 2018 -0700"
  },
  "committer": {
    "name": "Jingning Han",
    "email": "jingning@google.com",
    "time": "Fri Mar 16 20:23:09 2018 +0000"
  },
  "message": "[NORMATIVE] Clear frame distance parse in explicit_order_hint\n\nWhen the explicit_order_hint is turned on, the frame index will\ntake cyclic count between 0 - 127. The frame distance computation\nwill interpret distance (80 - 0) as (80 - 128) -\u003e -48. For many\n1-pass video conferencing settings, one might for example keep\na golden or arf frame for a long time, which would result a frame\ndistance computation from 80 to 0 as -48 and causing codec failure\nin mfmv projection.\n\nTo solve such potential mis-interpretation, we always drop the\nnegative frame distance in the denominator part of the motion vector\nprojection.\n\nBUG\u003daomedia:1593\nBUG\u003daomedia:1599\n\nChange-Id: I6a6fe32c2d9398c12195cf1648ccabdc56dab6d5\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "02834e017ae90a422e7fc7fe8794f12dddea2511",
      "old_mode": 33188,
      "old_path": "av1/common/mvref_common.c",
      "new_id": "89f4d29cf8cd91ff9e73826e53c1ef5db44c7365",
      "new_mode": 33188,
      "new_path": "av1/common/mvref_common.c"
    }
  ]
}