Issue metadata
Sign in to add a comment
|
Tapping video in Chrome Downloads menu plays back in external player, not Chrome |
||||||||||||||||||||||||
Issue descriptionVersion: 55.0.2883.9 OS: Android NDE63T Device: Pixel This may be related to crbug.com/637917 . Also see crbug.com/657590 , which is about the download action being hidden behind a long-press menu. What steps will reproduce the problem? (1) Go to http://pagalworld.co (2) Select one of the "Mp4" links under any of the entries listing a video, and click through to see the page with the download link. For example: http://pagalworld.co/filedownload/11317/102401/Dekh%20Lena%20-%20Tum%20Bin%202%20- %20Arijit%20Singh%20-%20Video%20MP4.html (3) LONG-PRESS on the [Real Download Link] on the page, e.g., http://dl.enjoypur.vc/upload_file/367/382/7491/PagalWorld%20-%20Bollywood%20Mp4%20Video%20Songs%202016/Tum%20Bin%202%20(2016)%20Mp4%20Video%20Songs/Dekh%20Lena%20-%20Tum%20Bin%202%20-%20Arijit%20Singh%20-%20Video%20MP4.mp4 (4) Wait for Chrome to download the file. (5) Go to the Chrome three-dots menu and select "Downloads" (6) Select the video file that was downloaded. Expected results: The video should start playing back from within Chrome, using Chrome's media controls. Observed results: The video starts playing back in MX Player. This happens even after I "reset app preferences" on my device; I have no idea why MX Player would be used as the default without asking me which media player I want. But, I think Chrome should be preferred for media files downloaded in Chrome. Note that this is inconsistent with what happens when you tap the Android download notification (which attempts, but fails, to play the file back in Chrome): crbug.com/657594 tracks that issue.
,
Oct 20 2016
I don't understand why Chrome can't play this file but MX Player and UC Browser can? This is an MP4 file. It is the most common video format on mobile. Are we seriously that far behind in our media support in Chrome? I think we should re-dupe this because that seems to suggest a larger issue that needs to be addressed (feel free to edit the bug title!).
,
Oct 20 2016
This really depends on how media pipeline is implemented. Chrome used to use android MediaPlayer to decode the video stream, and then composite the video frame with the rest of the contents. However, with recent work on media pipeline, Chrome now decodes video with its own parser, demuxer, and Android MediaCodec. As a result of this change, some of the codecs are no longer supported, and the usage of those unsupported codecs should be very low
,
Oct 21 2016
Dale: Can we confirm that the file here is not a supported codec, so this is WAI? Thanks.
,
Oct 21 2016
Per the discussion on 657594: Dale said, "Chrome does not support the mpeg4 codec, so we shouldn't open this file in Chrome...We only support h264 in the mp4 container, not h263. FWIW, even in BRIC h263 rates are ~0.22%." So, intenting out is the right solution and Chrome is WAI. I will close this bug. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dah...@chromium.org
, Oct 19 2016Status: Duplicate (was: Assigned)