PiRSquared17 / ffinputdriver

Automatically exported from code.google.com/p/ffinputdriver
GNU General Public License v2.0
0 stars 0 forks source link

h264-in-mkv slow seeking #13

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
To reproduce open h264-in-mkv file and try to seek
h264 stream uses closed gop 24-240 frames. average gop is like ~70 frames
Even if I seek to keyframe - it takes forever before it actually do something. 
It doesn't decodes all the stream of course but it's clearly doing some 
redundant decoding. After seeking to keyframe or recovery point or whatever 
results should be instantly displayed...

Also not sure it it's related, possibly it is so I'll stick it here.

It seems ffinputdriver can't recognize keyframes. After seeking at 1st VDub 
shows [U] in frame indicator. But by going backward or forward 1 frame and then 
returning to keyframe - ten it recognizes is and shows [K]

Original issue reported on code.google.com by Gagaron...@gmail.com on 23 Jun 2013 at 7:22