)]}'
{
  "commit": "982dc791dbdc69fd377bdfeec3d271ee5ccf4f0e",
  "tree": "cbc35154b301821d8ee5b298f5c34666173cb835",
  "parents": [
    "5ce38fff17b332c7bf06a0d582bb233704d2fb21"
  ],
  "author": {
    "name": "Erik Språng",
    "email": "sprang@webrtc.org",
    "time": "Wed Mar 13 15:33:02 2019"
  },
  "committer": {
    "name": "Commit Bot",
    "email": "commit-bot@chromium.org",
    "time": "Wed Mar 13 16:42:38 2019"
  },
  "message": "Preserve legacy behavior for old OveruseFrameDetector\n\nA recent refactoring introduced a subtle difference in how encoded\nframe timing is measured. See\nhttps://webrtc-review.googlesource.com/c/src/+/124122/14/video/video_stream_encoder.cc#b1278\n\nAfter that change, the encode was considered done after encoding was\ndone. The old behavior included the time needed to call stats and\nthe video sink, which might include video quality tests related tasks\nand RTP packetization.\n\nIn order to preserve the old behavior I\u0027m moving timestamping to after\npacketization again.\nNote that the timing frame info still has a separate timestamp that\ndoes explicitly measure encode time. This is used by the experimental\nnew overuse detector, so the effect of this change will be transient\nanyhow.\n\nBug: chromium:941457, webrtc:10164\nChange-Id: Ia990a1ceaeaf2c45d5df2a32d4f017cdb08e3c55\nReviewed-on: https://webrtc-review.googlesource.com/c/src/+/127569\nReviewed-by: Niels Moller \u003cnisse@webrtc.org\u003e\nCommit-Queue: Erik Språng \u003csprang@webrtc.org\u003e\nCr-Commit-Position: refs/heads/master@{#27108}",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c1dac5ee44337e0a5f6dac1344b13fdd401b2c9f",
      "old_mode": 33188,
      "old_path": "video/video_stream_encoder.cc",
      "new_id": "15abc42f1e2ecff583db9a65a5e2f92a8f3b6db9",
      "new_mode": 33188,
      "new_path": "video/video_stream_encoder.cc"
    }
  ]
}