[FFmpeg-trac] #8014(ffmpeg:closed): Piping mjpeg drops frames

[FFmpeg]

#8014: Piping mjpeg drops frames
-------------------------------------+-------------------------------------
             Reporter:  sig          |                    Owner:
                 Type:  defect       |                   Status:  closed
             Priority:  normal       |                Component:  ffmpeg
              Version:  git-master   |               Resolution:  invalid
             Keywords:  h264 mjpeg   |               Blocked By:
  pipe dropped frames                |
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Changes (by mkver):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 1. Your video actually contains 101 frames.
 2. You have not really shown that this is a bug in FFmpeg. It could also
 be in your other software or in your handling of the other software.
 3. It is actually your handling of the other software. The output of xxd
 looks like this:
 {{
 00000000: ffd8 ffe0 0010 4a46 4946 0001 0200 0001  ......JFIF......
 00000010: 0001 0000 fffe 0010 4c61 7663 3538 2e35  ........Lavc58.5
 00000020: 332e 3130 3100 ffdb 0043 0008 0808 0908  3.101....C......
 }}
 The ffd8 at the beginning will of course be found by grep. But this non-
 word-aligned occurence will not:
 {{
 0000bf90: 0c88 bad3 4591 65bf ebd6 0b42 e188 5865  ....E.e....B..Xe
 0000bfa0: 6e9f 0877 4dd7 a2ff d9ff d8ff e000 104a  n..wM..........J
 0000bfb0: 4649 4600 0102 0000 0100 0100 00ff fe00  FIF.............
 }}
 This happens 41 times; and there are a further eight times where ff and d8
 are in different lines. 41 + 8 + 52 = 101; notice that one of your 53
 matches is actually a false match:
 {{
 000ffd80: 19a1 1985 04e0 8ad4 d3c5 4944 7074 0386  ..........IDpt..
 }}

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