summaryrefslogtreecommitdiffstats
path: root/remoting/resources/remoting_strings_hi.xtb
diff options
context:
space:
mode:
authorhclam@chromium.org <hclam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2014-05-09 00:01:50 +0000
committerhclam@chromium.org <hclam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2014-05-09 00:01:50 +0000
commit88f73bd643e264b2df0b5ec8199263f09b368159 (patch)
treed3642f3560550829e0a84acc235092dd097fe839 /remoting/resources/remoting_strings_hi.xtb
parentf77fa3681f4e11bdb2650269764b3bd4386be929 (diff)
downloadchromium_src-88f73bd643e264b2df0b5ec8199263f09b368159.zip
chromium_src-88f73bd643e264b2df0b5ec8199263f09b368159.tar.gz
chromium_src-88f73bd643e264b2df0b5ec8199263f09b368159.tar.bz2
Cast: Improve AV sync slightly
This is an interim solution before we can pass TimeTicks associated with a video frame to the cast library. We use base::TimeTicks::Now() when a frame is delivered to the render process as the timestamp of the frame. This improves AV sync slightly according to the performance test. Before *RESULT CastV2Performance_gpu_24fps: av_sync= {15.520811,10.694887} ms *RESULT CastV2Performance_gpu_30fps: av_sync= {7.877492,14.865763} ms *RESULT CastV2Performance_gpu_60fps: av_sync= {-15.974133,10.762621} ms After *RESULT CastV2Performance_gpu_24fps: av_sync= {9.231218,10.886808} ms *RESULT CastV2Performance_gpu_30fps: av_sync= {10.161435,10.176140} ms *RESULT CastV2Performance_gpu_60fps: av_sync= {-10.761692,12.102184} ms R=hubbe@chromium.org Review URL: https://codereview.chromium.org/273753003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269112 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'remoting/resources/remoting_strings_hi.xtb')
0 files changed, 0 insertions, 0 deletions