[NUT-devel] [nut]: r636 - docs/nut.txt
Måns Rullgård
mans at mansr.com
Thu Feb 14 02:28:22 CET 2008
Diego Biurrun <diego at biurrun.de> writes:
> On Thu, Feb 14, 2008 at 12:31:48AM +0000, Måns Rullgård wrote:
>> Michael Niedermayer <michaelni at gmx.at> writes:
>>
>> > On Wed, Feb 13, 2008 at 08:11:58PM +0000, Måns Rullgård wrote:
>> >> michael <subversion at mplayerhq.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
mans at mansr.com
More information about the NUT-devel
mailing list