HW accelerated playback shows black screen on every keyframe if h264 video was encoded by Cisco OpenH264 encoder.
Reported by
a...@splitmedialabs.com,
Jul 12 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36 Example URL: Steps to reproduce the problem: 1. switch on HW accelerated playback. 2. drag attached mp4 file to chrome. 3. What is the expected behavior? correct playback without black blinking. What went wrong? playback shows black screen on every keyframe. Did this work before? N/A Is it a problem with Flash or HTML5? N/A Does this work in other browsers? N/A Chrome version: 51.0.2704.106 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0 here are the sample files encoded by OpenH264 1.5.0 baseline and main h264 profile. https://drive.google.com/file/d/0B9sYP9zM0ZVTMk1qWVpTbjN2ZDg/view?usp=sharing https://drive.google.com/file/d/0B9sYP9zM0ZVTeFFGdnJQSEVCNkk/view?usp=sharing I tried OpenH264 of 1.5.0 and 1.6.0 versions. here are the OpenH264 settings I used, but the problem is not in the settings because all other players (VLC, WMP, Movies & TV, MPC-HC) can play these files. ProfileIdc:66 RCMode:0 EnableFrameCroppingFlag:0 TargetBitrate:3000000 MaxBitrate:3000000 SpatialBitrate:3000000 EnableFrameSkip:0 MaxFrameRate:30 FrameRate:30 SliceMode:0 TemporalLayerNum:1 SpatialLayerNum:1 EnableBackgroundDetection:1 EnableAdaptiveQuant:1 EnableLongTermReference:0 LtrMarkPeriod:10 IntraPeriod:10 MultipleThreadIdc:0 ComplexityMode:0 SpsPpsIdStrategy:6 NumRefFrame:2 EntropyCodingModeFlag:1 EnableDenoise:0
,
Jul 12 2016
re #1: there are links to files in the report.
,
Jul 12 2016
I am unable to reproduce this with Canary or Stable. Some things that could help: - Is it the screen or the video element which blinks? - Please test again with Chrome Canary and let us know the result. - Attach the contents of chrome://gpu, and if possible test on a machine with a different manufacturer's GPU.
,
Jul 13 2016
Hi. thank you for quick reply. I unable reproduce it in Canary. It is replicable in my stable Version 51.0.2704.106 m It is not replicable with same version on other machine. so it depends of GPU. I attached chrome://gpu from affected machine and not affected.
,
Jul 13 2016
Thank you for providing more feedback. Adding requester "sandersd@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 14 2016
The main thing that stands out to me is that this machine is dual-GPU (Intel + NVidia), but Stable is only seeing one GPU. Can you tell us more about your setup, specifically: - Which GPU device is the display connected to? - Do you have Optimus or other GPU switching enabled? If so, does forcing Chrome to one GPU or the other fix anything? Thanks again! (Note though that since Canary is working the conclusion will probably be WontFix at this point unless there turn out to be many affected users, since a working version of Chrome is likely to reach users relatively soon anyway.)
,
Jul 21 2016
,
Jul 22 2016
the problem is fixed in latest chrome update 52.0.2743.82 m.
,
Jul 28 2016
Thanks for updating us! |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by yini...@chromium.org
, Jul 12 2016