[FFmpeg-trac] #4893(undetermined:new): FFmpeg stops outputting frames unexpectedly and indefinitely on "bad" h264 over UDP stream

FFmpeg trac at avcodec.org
Mon Oct 19 20:36:50 CEST 2015


#4893: FFmpeg stops outputting frames unexpectedly and indefinitely on "bad" h264
over UDP stream
-------------------------------------+-------------------------------------
             Reporter:  superware    |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
              Version:  unspecified  |  undetermined
             Keywords:  udp h264     |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------

Comment (by cehoyos):

 Replying to [comment:19 superware]:
 > Just for the record, this stream/file is in very bad quality (every
 other UDP packet, alternately) just in order to reproduce this issue which
 seems to happen even on a brief bad stream of sort.

 Sorry, I do not understand what you are trying to report: The file you
 provide contains 390 broken frames and all can be transcoded: If you cut
 400k (10%) from the end, 361 frames are decoded, if you cut 500k from the
 beginning, 358 frames are decoded indicating that the whole file can be
 read. With a file as broken as this one, you cannot expect that you get a
 decodable stream no matter where you cut it. This could be different if
 the stream were recognisable but this is not the case.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/4893#comment:20>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list