GNOME Bugzilla – Bug 515237
[avidemux] index optimization
Last modified: 2009-11-16 20:04:16 UTC
I'm profiling avidemux and sorting the index seems to take a considerable amount of time. The patch sorts the index only if it's actually unsorted.
Created attachment 104727 [details] [review] Patch
looks, good. I'll give it a try, but lets apply this after the freeze.
The idea behind the patch is good, but unfortunately it only check for out-of-order when doing the index massaging. And this only happens for streams with one block only and the block being audio. Should probably also be done for gst_avi_demux_stream_scan()
What about using GstIndex for proper index support ? And therefore not have to care about the implementation of storage/ordering/etc.
Do we have any demuxer that uses GstIndex. For me its far from obvious how to use GstIndex.
GstIndex will need much more memory though as it's very very generic :) But by using balanced binary trees it's quite fast. Stefan, flvdemux uses GstIndex (but probably wrong, it should maybe use one writer ID per output stream).
Is this not pretty much handled by the recent avidemux index handling rewrite?
Yep, not needed anymore. No more sort there even :)