#2667: console spamming when decoding a h264 / mp4 stream
------------------------------------+-----------------------------------
Reporter: gjdfgh | Owner:
Type: defect | Status: open
Priority: minor | Component: avcodec
Version: git-master | Resolution:
Keywords: h264 mov | Blocked By:
Blocking: | Reproduced by developer: 1
Analyzed by developer: 0 |
------------------------------------+-----------------------------------
Comment (by cehoyos):
Replying to [comment:10 ubitux]:
> Replying to [comment:9 cehoyos]:
> > Replying to [comment:8 ubitux]:
> > > > Priority changed from normal to minor
> > > > Summary changed from can't decode some mp4/h264 streams to console
spamming when decoding a h264 / mp4 stream
> > >
> > > Well broken playback is the issue
> >
> > Please elaborate!
> > (I was unable to reproduce / decoding works - perfectly - fine here,
of course it is very possible that I am wrong but without any explanation
this is extremely difficult to guess / understand.)
> >
>
> The video is not supposed to be stalled like it is currently
That brings me back to my original question:
Which application does not ''stall''?
(Before you answer: Note that afaict most frames in the sample only
consist of "0" and "1" making decoding extra difficult imo if we do not
assume 1bit ppm or bmp.)
Or in other words: To the best of my knowledge the sample is broken and
FFmpeg decodes it *extremely* well (spamming the console).
(It is still not unlikely that I am completely wrong, that the sample can
be decoded much better / not ''stalled'' but that would imo need at least
some indication.)
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2667#comment:11>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac
