[NUT-devel] [nut]: r507 - docs/draft-niedermayer-nut-00.xml

[Rich Felker]

On Sun, Oct 28, 2007 at 03:44:31AM +0100, Michael Niedermayer wrote:
> On Sun, Oct 28, 2007 at 02:34:36AM +0200, lu_zero wrote:
> > Author: lu_zero
> > Date: Sun Oct 28 02:34:35 2007
> > New Revision: 507
> > 
> > Log:
> > yet another update
> 
> this is not a acceptable svn log message

:)

> > Modified:
> >    docs/draft-niedermayer-nut-00.xml
> > 
> > Modified: docs/draft-niedermayer-nut-00.xml
> > ==============================================================================
> > --- docs/draft-niedermayer-nut-00.xml	(original)
> > +++ docs/draft-niedermayer-nut-00.xml	Sun Oct 28 02:34:35 2007
> > @@ -101,8 +101,8 @@ providing citations here. -->
> >              synchronous 1-in-1-out decoder.
> >              </t>
> >              <t hangText="frame"> Minimal unit of information that can be
> > -            decoded completely, it is usually holds a full frame video frame,
> > -            a group of audio samples or a subtitle line.
> > +            decoded, it is usually holds a part of video frame, a group of
> > +            audio samples or a subtitle line.
> 
> huh? a frame is part of a (video) frame ?

A frame is exactly one video frame. Less or more is not allowed.

> > -      <t></t>
> > -    
> > +      <t>Every NUT file starts with an identification string, main (global)
> > +      headers and per stream headers follow, frame data is interleaved with
> > +      syncpoint packets. Optional info packets and index packet MAY be present,
> > +      in multiple copies, in order to improve resilience</t>
> 
> this is unclear if not outright wrong
> it makes it look as if only index and info packets may be repeated
> also the "may" is not correct headers at least have strict repeation rules

Agree.

Rich