February 2007 - NUT-devel - lists.mplayerhq.hu

Fourcc spec
by Oded Shimon 31 May '07

31 May '07

This specification is normative to demuxers, informative to muxers. It does not need to be actively maintained, because it does NOT list all legal fourcc's, only the ones noted by the specification. I'd like to commit it to nut/docs/fourcc.txt . - ods15

5 39

[PATCH] By Diego - punctuation and other important cosmetics to nut.txt
by Oded Shimon 26 Feb '07

26 Feb '07

It also includes some FIXME's he added... (I'm sending this patch for him due to mail server down...) - ods15

2 5

nut+h264 == kaboom
by Luca Barbato 23 Feb '07

23 Feb '07

Ok, besides jokes, libnut/ffmpeg cannot store h264 is a decent way triggering some strange behaviour (as in not seekable nut) to reproduce simply transcode a file in h264 in nut and see the results ^^ lu

4 5

r22265 - trunk/DOCS/tech/nut.txt
by michael 18 Feb '07

18 Feb '07

Author: michael Date: Sun Feb 18 21:21:19 2007 New Revision: 22265 Modified: trunk/DOCS/tech/nut.txt Log: clarify that language must be a 3 letter code dont clarify the country code 2 vs. 3 issue as there where few comments about that ... Modified: trunk/DOCS/tech/nut.txt ============================================================================== --- trunk/DOCS/tech/nut.txt (original) +++ trunk/DOCS/tech/nut.txt Sun Feb 18 21:21:19 2007 @@ -844,10 +844,11 @@ Note: do not forget the timezone "Keywords" "Language" - ISO 639 and ISO 3166 for language/country code - something like "eng" (US English), can be 0 if unknown - and "multi" if several languages - see http://www.loc.gov/standards/iso639-2/englangn.html + An ISO 639-2 (three-letter) language code, optionally followed by an + ISO 3166-1 country code that is separated from the language + code by a hyphen. All codes defined in ISO 639-2 are allowed, + including "und" (Undetermined), "mul" (Multiple languages) + see http://www.loc.gov/standards/iso639-2/ and http://www.din.de/gremien/nas/nabd/iso3166ma/codlstp1/en_listp1.html the language code a demuxer MUST ignore unknown language and country codes instead of

1 0

questions about "Language" info packets
by Clemens Ladisch 14 Feb '07

14 Feb '07

nut.txt says: | "Language" | ISO 639 and ISO 3166 for language/country code Does "ISO 639" mean ISO 639-1 or ISO 639-2? Are both codes required or allowed? If yes, in what format? | something like "eng" (US English) When using a three-letter code from ISO 639-2, should a nut writer use the bibliographic or the terminology code? Are two-letter codes allowed at all? | can be 0 if unknown Does this mean that there is no Language entry, or that it is an emtpy string, or that it is a string containing a zero byte, or that the string is "0"? | and "multi" if several languages ISO 639-2 already has "mul" for multiple languages. Does this mean that both "mul" and "multi" are allowed? Regards, Clemens

4 12

r22217 - trunk/DOCS/tech/nut.txt
by michael 14 Feb '07

14 Feb '07

Author: michael Date: Wed Feb 14 13:29:09 2007 New Revision: 22217 Modified: trunk/DOCS/tech/nut.txt Log: demuxers must ignore unknown lang/country codes, it seems we all agree that this should be stated clearly it follows from the fact that new language and country codes are added to the ISO standards from time to time and that a compliant demuxer must not reject a valid file which uses such a new code which was not know when the demuxer was written Modified: trunk/DOCS/tech/nut.txt ============================================================================== --- trunk/DOCS/tech/nut.txt (original) +++ trunk/DOCS/tech/nut.txt Wed Feb 14 13:29:09 2007 @@ -850,6 +850,8 @@ see http://www.loc.gov/standards/iso639-2/englangn.html and http://www.din.de/gremien/nas/nabd/iso3166ma/codlstp1/en_listp1.html the language code + a demuxer MUST ignore unknown language and country codes instead of + treating them as an error "Disposition" "original", "dub" (translated), "comment", "lyrics", "karaoke" Note: if someone needs some others, please tell us about them, so we

1 0

fourcc for raw PCM data?
by Clemens Ladisch 13 Feb '07

13 Feb '07

According to the spec, the fourcc for raw PCM data would be the same as in .avi, i.e., 0x0001. However, this fourcc does not specify how many bits the samples have. Raw PCM does not seem to have any codec specific data that could be used for this purpose. Should I use one of the .mov fourccs instead? Regards, Clemens

1 0

r22192 - trunk/DOCS/tech/nut.txt
by michael 10 Feb '07

10 Feb '07

Author: michael Date: Sat Feb 10 18:00:03 2007 New Revision: 22192 Modified: trunk/DOCS/tech/nut.txt Log: clarify description of reserved_count in frame header patch by (Clemens Ladisch cladisch,fastmail,net) Modified: trunk/DOCS/tech/nut.txt ============================================================================== --- trunk/DOCS/tech/nut.txt (original) +++ trunk/DOCS/tech/nut.txt Sat Feb 10 18:00:03 2007 @@ -301,6 +301,7 @@ frame: frame_code f(8) frame_flags= flags[frame_code] + frame_res= reserved_count[frame_code] if(frame_flags&FLAG_CODED){ coded_flags v frame_flags ^= coded_flags @@ -315,8 +316,8 @@ data_size_msb v } if(frame_flags&FLAG_RESERVED) - reserved_count[frame_code] v - for(i=0; i<reserved_count[frame_code]; i++) + frame_res v + for(i=0; i<frame_res; i++) reserved v if(frame_flags&FLAG_CHECKSUM){ checksum u(32)

1 0

[MPlayer-dev-eng] [PATCH] nut.txt: clarify description of reserved_count in frame header
by Clemens Ladisch 09 Feb '07

09 Feb '07

The pseudocode for the coded reserved_count in a frame header says "reserved_count[frame_code]". This could be interpreted as meaning that the coded value resets the value for this frame_code, i.e., that the coded value would also be the default value for all further occurrences of this frame code. The patch introduces a temporary variable to avoid that interpretation.

2 1

[PATCH] libnut muxer: write at least one timebase
by Clemens Ladisch 05 Feb '07

05 Feb '07

This patch adds code to make sure that there is at least one timebase. Otherwise, creating a file without any stream would result in an invalid file, or the muxer would crash when trying to write max_pts in the index.

3 4