On Sun, Sep 23, 2012 at 11:37 PM, Andrey Utkin <[email protected]> wrote: > 2012/9/19 Thomas Worth <[email protected]>: >> Ok, fine. BUT, once these errors occur, if I try to seek to the >> beginning again the DTS and PTS values are ALWAYS >> -9223372036854775808. It doesn't matter how many times I flush >> buffers, or close and reopen the codec, I am stuck with never being >> able to read the correct DTS and PTS ever again for that file (unless >> I quit and restart the app)! It's like something internal to avcodec >> is botched and can't be recovered. If these decode errors are >> encountered in the middle of a loop, the DTS/PTS are still shown >> correctly until the end of the loop but once I issue the >> av_seek_frame() and flush buffers to rewind the stream, the timestamps >> are always -9223372036854775808 from that point on. >> >> Has anyone encountered this? Is there something else I need to do to >> restore proper DTS/PTS after a decode error? > > Sounds serious. Could you please supply us with sample media file, and > simple app that reproduces the issue? > And first ensure you reproduce it with latest revision from git.
I just tried it with latest git (ff58480) and the problem remains. I'll send you the sample code and MTS file. I would post here, but the video belongs to a client so I probably shouldn't make it publicly available. _______________________________________________ Libav-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/libav-user
