Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(29)

Unified Diff: media/base/video_frame.h

Issue 1265433003: Preliminary change for new rtc rendering algorithm (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 5 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: media/base/video_frame.h
diff --git a/media/base/video_frame.h b/media/base/video_frame.h
index bc92b9a0fcaee3c460ee2cf493b2629cae7c2fc7..b03c9c6120d13b7cbd90bd25ad7797f5e577c5b9 100644
--- a/media/base/video_frame.h
+++ b/media/base/video_frame.h
@@ -376,6 +376,10 @@ class MEDIA_EXPORT VideoFrame : public base::RefCountedThreadSafe<VideoFrame> {
// This method is thread safe. Both blink and compositor threads can call it.
void UpdateReleaseSyncPoint(SyncPointClient* client);
+ // Record the ideal time instant to render this frame.
DaleCurtis 2015/07/30 05:55:24 VideoFrame is already in a crufty situation so we
qiangchen 2015/07/30 17:40:26 I'll consider using VideoFrameMetadata. Should I a
DaleCurtis 2015/07/30 17:52:33 Before you go the metadata approach, I would see i
+ base::TimeTicks render_time();
+ void set_render_time(base::TimeTicks render_time);
+
private:
friend class base::RefCountedThreadSafe<VideoFrame>;
@@ -478,6 +482,8 @@ class MEDIA_EXPORT VideoFrame : public base::RefCountedThreadSafe<VideoFrame> {
VideoFrameMetadata metadata_;
+ base::TimeTicks render_time_;
+
DISALLOW_IMPLICIT_CONSTRUCTORS(VideoFrame);
};

Powered by Google App Engine
This is Rietveld 408576698