New submission from aviad rozenhek <avia...@gmail.com>: sometimes the input TS we need to process gets a little bogus and unusable. in this case, it makes sense the decoding produces error messages instead of actual frames. the problem is that in some cases ffplay/ffmpeg simply crashes, whereas other stacks such as windows media player or mainconcept simply skip the problematic parts.
sample will be uploaded to incoming [30mb] ---------- messages: 13758 priority: normal status: new substatus: new title: ffplay crashes on TS file with bogus data type: bug ________________________________________________ FFmpeg issue tracker <iss...@roundup.ffmpeg.org> <https://roundup.ffmpeg.org/issue2625> ________________________________________________
