[MPlayer-dev-eng] NUT cleanup

[Michael Niedermayer]

Hi

On Sun, Sep 11, 2005 at 03:40:47PM -0400, Rich Felker wrote:
[...]
> > 2. Info packet position? Presumably now they can go anywhere, but this
> >    doesn't seem useful since we have info streams.. Can we restrict
> >    them to go at the beginning right after the main headers, so that
> >    the demuxer can actually find them? And at most one info packet per
> >    stream, plus at most one global info packet?
> 
> Michael, you said you don't like what I said here, but can you explain
> why? IMO info packets are useless if the player can't find them.

ok there are several things i think are problematic
we have info streams? do you mean the metadata stream type? what is
its format? entirely user defined?
there are too many rules and restrictions with no analysis of the 
consequnces
info packets must be at the start, the muxer must not require seeking back
how is this supposed to work? and if you now suggest to put them at the end
well you also said truncated files must be valid IIRC ...
furthermore you completely ignore that various metadata might not be constant
for example a nut file with all the LOTR films, the title isnt constant
the start and stop times of each might or might not be known when
encoding starts, ok the obvious solution is to place that in the info stream
its just that the player is probably not going to find these how should it?
if we could have multiple packets at the start then the parts could be
described at least if the info is available ...


> 
> > 3. Info fields table:
> ...
> 
> My idea for this seems to have been rejected. IMO it's not a big deal
> as long as there's a safe way to add new values without breaking
> parsability of the table.

why do we need to add new fields to the table? i see no sense in this

[...]
-- 
Michael