New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 807652 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
█ charulat...@intel.com
dalecur...@chromium.org
avkodipelli@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

H.264 Decoder, MP (Main Profile) MP4 video is not playing properly

Reported by shiva.ku...@intel.com, Jan 31 2018 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
Platform: 9627.0.0-17.06.07

Steps to reproduce the problem:

1. Boot into Chromebook and enter credentials to login into user account.
2. Play H.264 Decoder, MP (Main Profile) MP4 video through default video player.

What is the expected behavior?
MP (Main Profile) MP4 videoVideo should open and play smooth.

What went wrong?
MP (Main Profile) MP4 video playback is not smooth.

Did this work before? N/A 

Chrome version: 61.0.3123.0  Channel: n/a
OS Version: 61.0.3123.0
Flash Version:

Comment 1 by conradlo@chromium.org, Feb 1 2018

Cc: charulat...@intel.com
Labels: Proj-Poppy
Owner: posciak@chromium.org
Charulatha, can you please provide the video stream tested?

Comment 2 by posciak@chromium.org, Feb 1 2018

Components: -UI OS>Kernel>Video

Comment 3 by vsu...@chromium.org, Feb 1 2018

Cc: avkodipelli@chromium.org

Comment 4 by charulat...@intel.com, Feb 26 2018 

Attached the video used for testing
AVC_Main@L3.2_176x144_25fps_325Kbps_12s800ms_overtime_qcif_hq.26l.264.mp4
511 KB View Download

Comment 5 by posciak@chromium.org, Feb 26 2018

Cc: dalecur...@chromium.org
Components: -OS>Kernel>Video Internals>Media>Video
Owner: ----
Status: Untriaged (was: Unconfirmed)
Thank you for the sample. This reproduces on desktop Linux, so does not appear to be ChromeOS or hardware accelerator-specific.

The raw stream extracted from it appears to be fine though, perhaps some issue related to the container?

Comment 6 by dalecur...@chromium.org, Feb 26 2018

Status: WontFix (was: Untriaged)
Timestamps in the file are wrong. It's using out of order frames during decoding, but both pts and dts timestamps are all in order:

0	0 - 0:00:00.000	0 - 0:00:00.000	36	9214	true	0	0	0	0	0
1	1 - 0:00:00.040	1 - 0:00:00.040	9250	2560	true	0	0	0	0	0
2	2 - 0:00:00.080	2 - 0:00:00.080	11810	763	true	0	0	0	0	0
3	3 - 0:00:00.120	3 - 0:00:00.120	12573	2437	true	0	0	0	0	0
4	4 - 0:00:00.160	4 - 0:00:00.160	15010	709	true	0	0	0	0	0
5	5 - 0:00:00.200	5 - 0:00:00.200	15719	2120	true	0	0	0	0	0
6	6 - 0:00:00.240	6 - 0:00:00.240	17839	433	true	0	0	0	0	0
7	7 - 0:00:00.280	7 - 0:00:00.280	18272	2049	true	0	0	0	0	0
8	8 - 0:00:00.320	8 - 0:00:00.320	20321	409	true	0	0	0	0	0
9	9 - 0:00:00.360	9 - 0:00:00.360	20730	2012	true	0	0	0	0	0
10	10 - 0:00:00.400	10 - 0:00:00.400	22742

dts should always be monotonically increasing, but pts should be out of order since that's what's in the bitstream.

Comment 7 by dalecur...@chromium.org, Feb 26 2018 

dts is first timestamp, pts is second timestamp; the output is from mp4box.js:

http://download.tsi.telecom-paristech.fr/gpac/mp4box.js/filereader.html
►

Sign in to add a comment