[Ffmpeg-devel] Wrong duration in a nut container

[Måns Rullgård]

Rich Felker <dalias at aerifal.cx> writes:

> On Fri, Aug 12, 2005 at 10:31:00AM +0200, Michael Niedermayer wrote:
>> > > nuts duration field is in a info packet and thats neither stored nor read
>> > > currently, patch welcome
>> > 
>> > IMO using the info field is a very bad idea. For instance people might
>> > framecopy a nut file to make a small excerpt, and keep all the info
>> > headers. Then the total length will be wrong. Instead the demuxer
>> > should seek to the end and read the last timestamps to find total
>> > length.. It will already be seeking to end to read index anyway, and
>> > if there's an index it can just get total length from the index.
>> 
>> and if the file is on something non seekable?
>> its a question which is more important, the validity of the duration
>> field in randomly cut raw pieces or the availabilty of the duration 
>> in non seekable streams
>
> imo duration makes no sense in nonseekable streams. usually they're
> continuous and have infinite/unknown/unspecified duration. there's
> certainly no reason the player needs to know the duration if it can't
> seek..

I can imagine a time-limited live broadcast.  Knowing when it will end
might be useful.  In general, though, I'd agree with you on this one.

-- 
M?ns Rullg?rd
mru at inprovide.com