[MPlayer-dev-eng] A few minor things about NUT

[Michael Niedermayer]

Hi

1. (key)frame repeation
at least in some cases like info streams or subtitles the muxer might wish to
repeat frames
demuxers must know about repeated frames, and should know about repeated
keyframes
should we add a is_redundant flag to the flags in the frame code table? 
IMHO yes otherwise we wont know / be able to discard repeated keyframes during
remuxing


2. split index
if theres a single damaged byte in the index it becomes useless, maybe we
should split it into chunks covering x..x+n syncpoints each?
think about cddrom/dvd these do get damaged, yeah the index can be rebuild and
a new cd burned and it is possible to seek without an index but thats slow
on slow media ...


3. index repeation
why not?


4. 2^x header repeat rule
completely breaks streaming, id say change it to "repeat headers either
often, never, at the end or at positions after 2^x"


5. convert_ts() overflow behavior
_IIRC_ this can overflow if timestamps are > 10 or 50years or so
is that an issue, it could be fixed if it is ...


6. behavior of damaged files on slow media (cdrom/dvd use case)


7. behavior with packet loss (network streaming use case)


8. dropable flag
conventional b frames may be droped should these be optionaly marked in the 
framecode the overhead would be tiny due to delta pts - frametype relations
the advantage? if a packet gets lost and it just contained dropable frames
no need to ask for a retransmit ...

-- 
Michael