| commit | 3c80d5d4956550075b3606c8c8683fc79dc32713 | |
| author | imcheng@chromium.org <imcheng@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Wed, 19 Feb 2014 06:36:51 +0000 (19 06:36 +0000) | ||
| committer | imcheng@chromium.org <imcheng@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Wed, 19 Feb 2014 06:36:51 +0000 (19 06:36 +0000) | ||
| tree | 69c4b9cd0b77d488d8e4c921361c1fdf086a8310 | treesnapshot (tar.gz zip) |
| parent | b72c7323d961ae81d513500da16265824f79be8a | commitdiff |
Cast: Implemented relative RTP timestamp in EncodingEventSubscriber.
- RTP timestamps in the maps of EncodingEventSubscribers (map keys, rtp timestamp fields in protos) are now relative to the first RTP timestamp seen since last Reset().
- The two GetXXXEventsAndReset() functions have been combined into one. In addition, it will now return the first RTP timestamp seen since the last Reset(). It will also reset the first RTP timestamp seen.
- There are two motivations for this change:
-- 1. RTP timestamps wrap around easily - around every 12 hours or so. If we do not use relative RTP timestamps, the ordering in the map, as well as general order of the events by frame, will be messed up.
-- 2. Using relative values will be more compact in variable-length encoding of the RTP timestamp fields.
Review URL: https://codereview.chromium.org/168933002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251973 0039d316-1c4b-4281-b951-d872f2087c98
- RTP timestamps in the maps of EncodingEventSubscribers (map keys, rtp timestamp fields in protos) are now relative to the first RTP timestamp seen since last Reset().
- The two GetXXXEventsAndReset() functions have been combined into one. In addition, it will now return the first RTP timestamp seen since the last Reset(). It will also reset the first RTP timestamp seen.
- There are two motivations for this change:
-- 1. RTP timestamps wrap around easily - around every 12 hours or so. If we do not use relative RTP timestamps, the ordering in the map, as well as general order of the events by frame, will be messed up.
-- 2. Using relative values will be more compact in variable-length encoding of the RTP timestamp fields.
Review URL: https://codereview.chromium.org/168933002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251973 0039d316-1c4b-4281-b951-d872f2087c98