Opened 13 years ago
Closed 13 years ago
#1595 closed defect (invalid)
Theora video produced by latest ffmpeg fails to load in Google Chrome
Reported by: | Bart | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | undetermined |
Version: | git-master | Keywords: | theora regression |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
Summary of the bug:
When creating a theora video with the latest checkout of ffmpeg (n0.8-12179-g1f68be4), the video fails to load in Google Chrome.
The video loads properly when using the latest stable release 0.11.1.
How to reproduce:
% ffmpeg -i input -qscale 5 -an -vcodec libtheora output
Then try to open the video in Google Chrome (tested on Windows and Linux, v.20.0.1132.57)
FFmpeg version: development branch (git describe: n0.8-12179-g1f68be4), built on 2-8-2012 using libtheora 1.1.0 on RHEL.
Attachments (5)
Change History (9)
comment:1 by , 13 years ago
Component: | FFmpeg → undetermined |
---|---|
Keywords: | regression added |
Version: | unspecified → git-master |
by , 13 years ago
Attachment: | example-input.avi added |
---|
by , 13 years ago
Attachment: | example-theora-master.ogg added |
---|
by , 13 years ago
Attachment: | example-theora-0.11.1.ogg added |
---|
by , 13 years ago
Attachment: | ffmpeg-master.log added |
---|
by , 13 years ago
Attachment: | ffmpeg-0.11.1.log added |
---|
follow-up: 3 comment:2 by , 13 years ago
In your command line, you do not specify a colour space. Older FFmpeg by default degraded colour information by choosing yuv420p even if the input format is rgb, newer FFmpeg chooses an output colour space that allows for maximum compatibility with the input colour space (see tickets #1426 and #1517).
I suspect it will work fine with -pix_fmt yuv420p - please test.
comment:3 by , 13 years ago
Replying to cehoyos:
You are right! Adding -pix_fmt yuv420p produces a working video.
I guess this ticket can be closed. Thanks!
Please post complete, uncut console output together with your command line.
Please consider using git bisect to find the change introducing the regression.