New issue
Advanced search Search tips

Issue 661246 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Video playback not functioning on Samsung Chromebook XE550C22-A01US

Reported by qatest...@wevideo.com, Nov 1 2016

Issue description

Chrome Version       : 54.0.2840.79 (Official Build) (64-bit)
URLs (if applicable) : https://www.instagram.com/p/BMQ5Vr8A2Zm/?taken-by=marutaro
Other browsers tested:
Chrome on OSX/Win10: OK
Chrome on other chromebooks: OK
Safari: OK
Firefox: OK
IE: OK

What steps will reproduce the problem?
(1) Try to play the video https://www.instagram.com/p/BMQ5Vr8A2Zm/?taken-by=marutaro


What is the expected result?
Video plays properly

What happens instead?
Player disappears


Video playback seems to be having issues on this model of chromebook. We have a client on XE550C21 that is having the same issue. 

This issue was originally found because video playback was displaying a black screen on our video editing tool www.wevideo.com and after extensive troubleshooting, it seems to be caused by something else beyond our control.

If you want to test that specific case, you can go to https://www.wevideo.com/hub#editor/772279497
login is chromebug@testing.wevideo.com password chromebug
Click on the play button toward the middle right of the screen. You'll get a black screen on samsung chromebook, and the video on any other device in chrome.



 
Screen-Shot-2016-11-01-at-11.28.59.jpg
82.0 KB View Download
Screenshot 2016-11-01 at 11.26.05 AM.png
117 KB View Download
chrome___gpu.pdf
77.0 KB Download
About Version.pdf
73.1 KB Download
Screen-Shot-2016-11-01-at-11.41.02.jpg
66.6 KB View Download
Screenshot 2016-11-01 at 11.42.10 AM.png
185 KB View Download
I should note that playing videos via HTML5 video tag works without any issue. This can be seen within the WeVideo editor by clicking on the clip near the top of the screen and pressing the play button to preview.
Labels: OS-Chrome

Comment 3 Deleted

We found a workaround for this issue in WeVideo by changing the texture format for non transparent videos. 

Comment 5 by twreid@chromium.org, Jan 31 2017

Components: OS>Kernel>Video
Status: Untriaged (was: Unconfirmed)

Comment 6 by twreid@chromium.org, Jan 31 2017

Components: -OS>Kernel>Video Blink>Media>Video
Components: -Blink>Media>Video Internals>Media>Hardware
Cc: posciak@chromium.org
Can you provide a direct link to the clip in question? Generally these type of issues are due to a corrupt bitstream that some hardware is less forgiving of than others.
Indeed, I may have filed the bug incorrectly as we are seeing different behavior on different older Samsung chromebooks. The original case in the issue description was fixed for this particular model but some in the same family are reporting the same problem still by our users. That test case is still valid

Navigate to https://www.wevideo.com/hub#editor/772279497
login is chromebug@testing.wevideo.com password chromebug
Click on the play button toward the middle right of the screen.

The Instagram video we thought may have had the same cause as it was the same symptom But it is good to know about the corrupt bitstream case.

For what it is worth, the users are reporting that the Instagram video plays without issue but they are still having issue with video playback within WeVideo.
Sorry I meant can you provide a download link for the clip in question that doesn't use your site? I.e. if you just try to play the video directly in Chrome, do you see the issue?
Directly playing the video has no issue
14946968_608281232706327_482536783976857600_n.mp4
895 KB View Download
Looks like your app is playing the video back through media source extensions? I don't have one of the failing devices, but if you play the video what does chrome://media-internals say about the failure?
We've reached out to our user experiencing the issue to make a comment here with the details needed, and we are expecting a response soon.
Our user is reporting that Chrome 56 resolved this issue.
Status: Fixed (was: Untriaged)
Great :)

Comment 16 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 17 by dchan@google.com, May 30 2017

Labels: VerifyIn-60
Labels: VerifyIn-61

Comment 19 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment