Thank you, it's doable with showinfo although not perfect if you want filter out only errors (because you are batch testing many files). But I managed to get corrupted frame.
I will explore also other testing tools inside ffmpeg for different approaches. Miha Peče On Thu, Dec 22, 2016 at 6:03 PM, <[email protected]> wrote: > > > On Dec 22, 2016, at 11:52 AM, Carl Eugen Hoyos <[email protected]> > wrote: > > > > 2016-12-22 16:50 GMT+01:00 Miha Pece <[email protected]>: > >> Hi to all, > >> > >> I was recently started to check our archive of video files. In many of > them > >> ffmpeg found some errors. For instance: > >> > >> [dvvideo @ 0x7fcc21816000] Concealing bitstream errors > >> > >> My question is, how can I find position (time location) where error > occurs? > >> Is 0x7fcc21816000 some kind of hex marker? > > > > It's a pointer into memory that does not help you. > > > >> If not, is a way to get that info from ffmpeg? > > > > Doesn't -report help? > > > To access a timestamp near the decoder's log, I suggest inserting `-vf > showinfo` so that you can find the timestamp expressed before the error. > Note this thread is related: http://ffmpeg.org/pipermail/ > ffmpeg-devel/2016-June/194949.html > > [...] > > Dave Rice > > _______________________________________________ > ffmpeg-user mailing list > [email protected] > http://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > [email protected] with subject "unsubscribe". > _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
