Hey Carl, thanks for the reply. We have an older version of the library (with some unrelated changes) and no ffmpeg executable to match it. Is it possible this was an issue at some point or are we not processing the file properly? Besides reading frames when playing is there another way of populating the index table from the Cues on demand (when a seek is requested) or when opening the file?
On Thu, Sep 6, 2018 at 12:17 PM, Carl Eugen Hoyos <[email protected]> wrote: > 2018-09-06 17:17 GMT+02:00, Bob Kirnum <[email protected]>: > > We use the libavformat APIs to open and read frames from various > > containers. The basics work fine for MKV. However, we have encountered > an > > issue seeking forward. It seems the index table is populated as the file > > is played. As such, the index entries beyond the current frame are not > > available. Seeking forward results in seeking to a non-key-frame. > > Is this reproducible with ffmpeg (the application)? > (Why not?) > > Carl Eugen > _______________________________________________ > Libav-user mailing list > [email protected] > http://ffmpeg.org/mailman/listinfo/libav-user >
_______________________________________________ Libav-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/libav-user
