Issue metadata
Sign in to add a comment
|
Software decode fallback not working for VTVDA
Reported by
anto...@tastemade.com,
Jul 27 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 Example URL: https://s3.amazonaws.com/truffle-repro/foo.mp4 Steps to reproduce the problem: 0. Go to chrome://flags to double check if video decode acceleration is enabled (default for my combination of chrome/osx) 1. Load URL directly, notice video doesn't play 2. Load chrome://media-internals - notice and error for this asset It works if I follow these steps 1. Go to chrome://flags 2. Disable hardware accelerated decode 3. Load the video 4. It works What is the expected behavior? The video should play regardless of video acceleration setting. The video plays correctly under Firefox 45.0.2, VLC and Quicktime (OSX 10.11). What went wrong? The video never started playing under hardware acceleration, with the HTML5 video element throwing a MEDIA_ERROR code 3. Did this work before? N/A Is it a problem with Flash or HTML5? HTML5 Does this work in other browsers? Yes Chrome version: 51.0.2704.103 Channel: n/a OS Version: OS X 10.11.3 Flash Version: Shockwave Flash 22.0 r0 Seems acceleration related, but I'm too ignorant about chrome to be able to say more. Here's the ffprobe output for the video: ffprobe version 3.0.2 Copyright (c) 2007-2016 the FFmpeg developers built with Apple LLVM version 7.0.2 (clang-700.1.81) configuration: --prefix=/usr/local/Cellar/ffmpeg/3.0.2 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-opencl --enable-libx264 --enable-libmp3lame --enable-libxvid --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libass --enable-openssl --enable-libx265 --enable-nonfree --enable-vda libavutil 55. 17.103 / 55. 17.103 libavcodec 57. 24.102 / 57. 24.102 libavformat 57. 25.100 / 57. 25.100 libavdevice 57. 0.101 / 57. 0.101 libavfilter 6. 31.100 / 6. 31.100 libavresample 3. 0. 0 / 3. 0. 0 libswscale 4. 0.100 / 4. 0.100 libswresample 2. 0.101 / 2. 0.101 libpostproc 54. 0.100 / 54. 0.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'foo.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 encoder : Lavf57.25.100 Duration: 00:04:38.04, start: 0.000000, bitrate: 10028 kb/s Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1080x1920 [SAR 1:1 DAR 9:16], 10026 kb/s, 25 fps, 25 tbr, 25k tbn, 50 tbc (default) Metadata: handler_name : VideoHandler Let me know anything I can do to help, and I apologize if this is a duplicate - only references I found to hardware accelerated decoding issues were related to VP9 / youtube.
,
Aug 4 2016
Over to sandersd@ for investigation or routing.
,
Aug 4 2016
The fundamental issue is that we do not support interlaced video playback. However, in this case, it should be falling back to software decode automatically, and the software decoder does have the (unsupported but reliable) ability to play interlaced video. While I would recommend re-encoding without interlacing, we'll investigate why the fallback isn't happening.
,
Sep 22 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dalecur...@chromium.org
, Jul 27 2016