[FFmpeg-devel] [PATCH] estimate stream durations using read_timestamp (was: [PATCH] estimate stream durations using read_timestamp

[elupus]

> We also would need benchmarks to see what effect the change has on speed,
> especially with files with many streams (mpeg ts with 20 streams has to be
> not slower ...)
> 
> [...]

Well given that it most likely will be alot slower, do you have any
suggestion as how to proceed? We could keep the old code for mpegs, but as
you say then there will be code duplication. 

Another option could be to change read_timestamp to allow a stream_index
parameter of -1, meaning return the first timestamp you come across,
independent of stream. This would be a quite abit larger patch thou as all
read_timestamp functions must be updated too support this.

In either case, here is an updated patch that ditches the old code.

Joakim
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nuv_timestamp.patch
Type: text/x-patch
Size: 4075 bytes
Desc: Attached file: nuv_timestamp.patch
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20080525/6992d8a2/attachment.bin>