: r636 - docs/nut.txt

Author: michael
Date: Wed Feb 13 20:26:30 2008
New Revision: 636

Log:
maybe better?


Modified:
   docs/nut.txt

Modified: docs/nut.txt
============================================================
==================
--- docs/nut.txt	(original)
+++ docs/nut.txt	Wed Feb 13 20:26:30 2008
 -1073,7
+1073,7  single codec frame. A muxer MUST NOT sto
 codec frame per NUT frame.
 For RAW audio up to 4096 samples shall be considered 1
codec frame, the actual
 number of samples MAY vary between NUT frames.
-For RAW video a single frame shall be 1 codec frame.
+For RAW video a single picture shall be 1 codec frame.
 
 
 Sample code (Public Domain, & untested):
_______________________________________________
NUT-devel mailing list
NUT-develmplayerhq.hu
https://lists.mplayerhq.hu/mailman/listinfo/nut-devel

michael <subversionmplayerhq.hu> writes:

> Author: michael
> Date: Wed Feb 13 20:26:30 2008
> New Revision: 636
>
> Log:
> maybe better?
>
> Modified:
>    docs/nut.txt
>
> Modified: docs/nut.txt
>
============================================================
==================
> --- docs/nut.txt	(original)
> +++ docs/nut.txt	Wed Feb 13 20:26:30 2008
>  -1073,7 +1073,7  single codec frame. A
muxer MUST NOT sto
>  codec frame per NUT frame.
>  For RAW audio up to 4096 samples shall be considered 1
codec frame, the actual
>  number of samples MAY vary between NUT frames.
> -For RAW video a single frame shall be 1 codec frame.
> +For RAW video a single picture shall be 1 codec
frame.

That doesn't make sense to me.  Do you mean something like
"For raw
video one NUT frame shall contain exactly one video
picture"?

-- 
Måns Rullgård
mansmansr.com
_______________________________________________
NUT-devel mailing list
NUT-develmplayerhq.hu
https://lists.mplayerhq.hu/mailman/listinfo/nut-devel

On Wed, Feb 13, 2008 at 08:11:58PM +0000, Måns Rullgård
wrote:
> michael <subversionmplayerhq.hu> writes:
> 
> > Author: michael
> > Date: Wed Feb 13 20:26:30 2008
> > New Revision: 636
> >
> > Log:
> > maybe better?
> >
> > Modified:
> >    docs/nut.txt
> >
> > Modified: docs/nut.txt
> >
============================================================
==================
> > --- docs/nut.txt	(original)
> > +++ docs/nut.txt	Wed Feb 13 20:26:30 2008
> >  -1073,7 +1073,7  single codec frame. A
muxer MUST NOT sto
> >  codec frame per NUT frame.
> >  For RAW audio up to 4096 samples shall be
considered 1 codec frame, the actual
> >  number of samples MAY vary between NUT frames.
> > -For RAW video a single frame shall be 1 codec
frame.
> > +For RAW video a single picture shall be 1 codec
frame.
> 
> That doesn't make sense to me.  Do you mean something
like "For raw
> video one NUT frame shall contain exactly one video
picture"?

yes

And it does make sense if you consider the previous rule:
A muxer MUST NOT store anything except exactly 1 single
codec frame per NUT frame.

The sentance about RAW video just clarifies what a codec
frame is.
Feel free to change the wording if you think its not good
...

[...]
-- 
Michael     GnuPG fingerprint:
9FF2128B147EF6730BADF133611EC787040B0FAB

No snowflake in an avalanche ever feels responsible. --
Voltaire

_______________________________________________
NUT-devel mailing list
NUT-develmplayerhq.hu
https://lists.mplayerhq.hu/mailman/listinfo/nut-devel

Michael Niedermayer <michaelnigmx.at> writes:

> On Wed, Feb 13, 2008 at 08:11:58PM +0000, Måns Rullgård
wrote:
>> michael <subversionmplayerhq.hu> writes:
>> 
>> > Author: michael
>> > Date: Wed Feb 13 20:26:30 2008
>> > New Revision: 636
>> >
>> > Log:
>> > maybe better?
>> >
>> > Modified:
>> >    docs/nut.txt
>> >
>> > Modified: docs/nut.txt
>> >
============================================================
==================
>> > --- docs/nut.txt	(original)
>> > +++ docs/nut.txt	Wed Feb 13 20:26:30 2008
>> >  -1073,7 +1073,7  single codec frame. A
muxer MUST NOT sto
>> >  codec frame per NUT frame.
>> >  For RAW audio up to 4096 samples shall be
considered 1 codec frame, the actual
>> >  number of samples MAY vary between NUT
frames.
>> > -For RAW video a single frame shall be 1 codec
frame.
>> > +For RAW video a single picture shall be 1
codec frame.
>> 
>> That doesn't make sense to me.  Do you mean
something like "For raw
>> video one NUT frame shall contain exactly one video
picture"?
>
> yes
>
> And it does make sense if you consider the previous
rule:
> A muxer MUST NOT store anything except exactly 1
single
> codec frame per NUT frame.
>
> The sentance about RAW video just clarifies what a
codec frame is.

In that case, "For raw video a codec frame is one video
picture" or
similar seems more natural.  In English, definitions begin
with the
entity being defined, followed by the explanation.

-- 
Måns Rullgård
mansmansr.com
_______________________________________________
NUT-devel mailing list
NUT-develmplayerhq.hu
https://lists.mplayerhq.hu/mailman/listinfo/nut-devel

On Thu, Feb 14, 2008 at 12:31:48AM +0000, Måns Rullgård
wrote:
> Michael Niedermayer <michaelnigmx.at> writes:
> 
> > On Wed, Feb 13, 2008 at 08:11:58PM +0000, Måns
Rullgård wrote:
> >> michael <subversionmplayerhq.hu> writes:
> >> 
> >> > Log:
> >> > maybe better?
> >> >
> >> > --- docs/nut.txt	(original)
> >> > +++ docs/nut.txt	Wed Feb 13 20:26:30
2008
> >> >  -1073,7 +1073,7  single codec frame. A
muxer MUST NOT sto
> >> >  codec frame per NUT frame.
> >> >  For RAW audio up to 4096 samples shall
be considered 1 codec frame, the actual
> >> >  number of samples MAY vary between NUT
frames.
> >> > -For RAW video a single frame shall be 1
codec frame.
> >> > +For RAW video a single picture shall be
1 codec frame.
> >> 
> >> That doesn't make sense to me.  Do you mean
something like "For raw
> >> video one NUT frame shall contain exactly one
video picture"?
> >
> > yes
> >
> > And it does make sense if you consider the
previous rule:
> > A muxer MUST NOT store anything except exactly 1
single
> > codec frame per NUT frame.
> >
> > The sentance about RAW video just clarifies what a
codec frame is.
> 
> In that case, "For raw video a codec frame is one
video picture" or
> similar seems more natural.  In English, definitions
begin with the
> entity being defined, followed by the explanation.

Just commit ...

Diego
_______________________________________________
NUT-devel mailing list
NUT-develmplayerhq.hu
https://lists.mplayerhq.hu/mailman/listinfo/nut-devel

Diego Biurrun <diegobiurrun.de> writes:

> On Thu, Feb 14, 2008 at 12:31:48AM +0000, Måns Rullgård
wrote:
>> Michael Niedermayer <michaelnigmx.at> writes:
>> 
>> > On Wed, Feb 13, 2008 at 08:11:58PM +0000, Måns
Rullgård wrote:
>> >> michael <subversionmplayerhq.hu> writes:
>> >> 
>> >> > Log:
>> >> > maybe better?
>> >> >
>> >> > --- docs/nut.txt	(original)
>> >> > +++ docs/nut.txt	Wed Feb 13 20:26:30
2008
>> >> >  -1073,7 +1073,7  single codec frame. A
muxer MUST NOT sto
>> >> >  codec frame per NUT frame.
>> >> >  For RAW audio up to 4096 samples
shall be considered 1 codec frame, the actual
>> >> >  number of samples MAY vary between
NUT frames.
>> >> > -For RAW video a single frame shall
be 1 codec frame.
>> >> > +For RAW video a single picture shall
be 1 codec frame.
>> >> 
>> >> That doesn't make sense to me.  Do you
mean something like "For raw
>> >> video one NUT frame shall contain exactly
one video picture"?
>> >
>> > yes
>> >
>> > And it does make sense if you consider the
previous rule:
>> > A muxer MUST NOT store anything except exactly
1 single
>> > codec frame per NUT frame.
>> >
>> > The sentance about RAW video just clarifies
what a codec frame is.
>> 
>> In that case, "For raw video a codec frame is
one video picture" or
>> similar seems more natural.  In English,
definitions begin with the
>> entity being defined, followed by the explanation.
>
> Just commit ...

I don't like committing changes when I'm not sure I've
understood the
intended meaning properly.

-- 
Måns Rullgård
mansmansr.com
_______________________________________________
NUT-devel mailing list
NUT-develmplayerhq.hu
https://lists.mplayerhq.hu/mailman/listinfo/nut-devel