[FFmpeg-trac] #731(undetermined:new): h264 video frames inside m2ts container get altered after commit 13b7781ec8d475513c1ee40a6e481763b728a71e
FFmpeg
trac at avcodec.org
Sat Dec 10 16:16:05 CET 2011
#731: h264 video frames inside m2ts container get altered after commit
13b7781ec8d475513c1ee40a6e481763b728a71e
-------------------------------------+-------------------------------------
Reporter: Andrea3000 | Owner:
Type: defect | Status: new
Priority: important | Component:
Version: git-master | undetermined
Keywords: h264 m2ts | Resolution:
Blocking: | Blocked By:
Analyzed by developer: 0 | Reproduced by developer: 0
-------------------------------------+-------------------------------------
Comment (by Andrea3000):
Replying to [comment:1 cehoyos]:
> Please provide a sample that allows to reproduce the problem (images are
nearly always unneeded).
> If the sample is larger than 2.5MB, please see
http://ffmpeg.org/bugreports.html or upload to
http://www.datafilehost.com/ (and provide the download link).
>
> For all problem reports on this tracker, please provide a (failing)
command line and complete, uncut console output.
It happens with every h264 movie file inside m2ts container, anyway I have
uploaded a short sample here: [http://www.datafilehost.com/download-
902f38c6.html]
I'm not able to provide the failing command line because I use FFmepg
library as API inside my OSX app.
The strange thing is that it seems to be a parsing issue rather then a
decoding issue. I have tried using FFmpeg first only as a parser (decoding
frames with the GPU) and later even as a decoder and this black border
appears in both of the case. Prior to that commit, both software (FFmpeg)
and hardware decoding wasn't giving any black border.
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/731#comment:2>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list