[FFmpeg-user] weird behavior with segmented files

[Shaya Potter]

and as a followup, while I said ffplay seemed to work fine, that was when I
played it just as ffplay out003.mp4

however when run with run -flags output_corrupt (ffplay -flags
output_corrupt out003.mp4) I see them same exact initial gray screen that I
see in totem and similar to vlc behavior (though there its black).

On Thu, Jul 14, 2016 at 9:34 AM, Shaya Potter <spotter at gmail.com> wrote:

> thanks for the reply, it helps (ffplay also seems to play it fine).  On a
> related note I tried outputting 100 frames and see errors like
>
> [h264 @ 0x122ad20] no frame!
> [h264 @ 0x123f040] no frame!
> Error while decoding stream #0:1: Invalid data found when processing input
> [h264 @ 0x12162e0] no frame!
> Error while decoding stream #0:1: Invalid data found when processing input
>
> but 100 jpg files are still produced.  md5sum seems to show that some
> frame sare duplicated so I'm guessing that is what happens in these errors
> case instead of not producing a file at all?
>
>
> On Thu, Jul 14, 2016 at 6:19 AM, Carl Eugen Hoyos <cehoyos at ag.or.at>
> wrote:
>
>> Shaya Potter <spotter <at> gmail.com> writes:
>>
>> > However, while the saved original file plays correctly, it
>> > seems the segmented files do not (in vlc and totem).
>>
>> I tested the following with the file you uploaded:
>> $ ffmpeg -i out003.mp4 -vframes 3 out%d.jpg
>>
>> out1.jpg looks fine, so I suspect an issue in vlc and totem.
>>
>> Carl Eugen
>>
>> _______________________________________________
>> ffmpeg-user mailing list
>> ffmpeg-user at ffmpeg.org
>> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>>
>> To unsubscribe, visit link above, or email
>> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
>
>
>