#958: matroska seek problem file (3 bugs)
-------------------------------------+-------------------------------------
Reporter: DonMoir | Owner:
Type: defect | Status: closed
Priority: normal | Component:
Version: git-master | undetermined
Keywords: mkv h264 | Resolution: fixed
seek | Blocked By:
Blocking: | Reproduced by developer: 1
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by reimar):
> I am assuming that your recent patches for matroska have not changed
this
Seeking should be working perfectly fine since those (though a bit slow,
since it involves scanning the whole file). The only thing I was
disagreeing with is that there is a bug at the point you pointed out and I
also think that the index should not be used even if that means slower
seeking that what might be possible when using anything from the non-
broken index parts.
I admit I am not completely sure about that last one. I seem to remember
discussion about tricks where you would reserve a few kB at the start of a
file for an index and then there put as many entries as fit (from all over
the file) and put the rest at the end.
This would then allow rather nice seeking even over http without having to
ever jump to the index at the end. If such a thing is actually done it
might be worth trying to support it over the current all-or-nothing
handling.
I also proposed a patch that introduces a resync function which would
allow implementing a read_timestamp function which should speed up seeking
without an index a lot.
So there's lots that could be done, but that should all be on the
"optimizing", not "bug fixing" level.
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/958#comment:10>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac
