Issue metadata
Sign in to add a comment
|
The video elements 'currentTime' property gives wrong time
Reported by
vinesh...@gmail.com,
Feb 12 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Steps to reproduce the problem: 1. play an mp4 generated from ffmpeg 2. pause video at every frame based on the MSE currentTime property (i.e. 40ms for a 25 fps clip) What is the expected behavior? Time 0ms should always show frame 0 and time 40ms should show frame 2 etc.. (for a 25fps clip) What went wrong? The same frame (frame:0) is being displayed for at least 1 extra frame period and up to a maximum of 4. all while the currentTime property is incorrectly incremented. Did this work before? No Chrome version: 64.0.3282.140 Channel: stable OS Version: 10.0 Flash Version:
,
Feb 12 2018
,
Feb 12 2018
This bug can be seen when playing but not limited to ffmpeg generated fmp4's both. the command used to generate the stream: ffmpeg.exe \ -y \ -ss 00:00:00 \ -s 1920x1080 \ -pix_fmt yuv420p \ -vcodec rawvideo \ -r 25 \ -i TestReel_1080p25_raw.yuv \ -vcodec libx264 \ -b:v 4M \ -g 75 \ -map 0 \ -f hls \ -hls_segment_type fmp4 \ -hls_fmp4_init_filename "init.mp4" \ -hls_segment_filename "segment%d.mp4" \ -hls_time 2 \ -hls_init_time 2 \ -hls_playlist_type vod \ "index.m3u8"
,
Feb 12 2018
,
Feb 12 2018
This sounds like a duplicate of Issue 555376 . +Dan, +Dale to confirm.
,
Feb 12 2018
Yeah looks like dupe.
,
Feb 12 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Feb 12 2018