January 2008 - NUT-devel - lists.mplayerhq.hu

NUT website
by Diego Biurrun 02 Feb '08

02 Feb '08

Guys, http://nut-container.org/ is in a sorry state. Two of the four links ("Download and SVN" and "Documentation") do not work. Is anybody going to create pages? Otherwise I am going to disable the links for now. The topic came up on the FOMS 2008 [1] mailing list. When talk came to an Ogg successor, I mentioned NUT. Also, can we bump the version number of the spec? It still carries a 2006 timestamp. Diego [1] http://www.annodex.org/events/foms2008/

2 1

[nut]: r519 - homepage/index.html
by diego 01 Feb '08

01 Feb '08

Author: diego Date: Thu Jan 31 09:55:42 2008 New Revision: 519 Log: slight wording improvement Modified: homepage/index.html Modified: homepage/index.html ============================================================================== --- homepage/index.html (original) +++ homepage/index.html Thu Jan 31 09:55:42 2008 @@ -36,9 +36,9 @@ conceived by a few MPlayer and FFmpeg developers that were dissatisfied with the limitations of all currently available multimedia container formats such as AVI, Ogg or Matroska. It aims to be simple, flexible, -extensible, compact and error resistant (resilience to errors), thus +extensible, compact and error resistant (error resilient), thus addressing most if not all of the shortcomings present in alternative -formats, like excessive CPU and size overhead, file size limit, inability +formats, like excessive CPU and size overhead, file size limits, inability to allow fine grained seeking or restrictions on the type of data they can contain. </p>

3 2

[nut]: r521 - homepage/index.html
by diego 31 Jan '08

31 Jan '08

Author: diego Date: Thu Jan 31 10:03:36 2008 New Revision: 521 Log: markup fixes/cosmetics Modified: homepage/index.html Modified: homepage/index.html ============================================================================== --- homepage/index.html (original) +++ homepage/index.html Thu Jan 31 10:03:36 2008 @@ -16,18 +16,19 @@ <center> - [<a href=index.html>Main Page and News</a>] + [<a href="index.html">Main Page and News</a>] [<a href="http://svn.mplayerhq.hu/nut/docs/nut.txt?view=co">Specification</a>] - [<a href=download.html>Download and SVN</a>] - [<a href=documentation.html>Documentation</a>] + [<a href="download.html">Download and SVN</a>] + [<a href="documentation.html">Documentation</a>] [<a href="http://lists.mplayerhq.hu/mailman/listinfo/nut-devel">Mailing List</a>] </center> -<br> <h2>News</h2> +<p> <strong>(February 24, 2007)</strong> This page was written! +</p> <h2>Project Description</h2> @@ -50,12 +51,11 @@ and dynamic index generation during play </p> <center> - [<a href=index.html>Main Page and News</a>] + [<a href="index.html">Main Page and News</a>] [<a href="http://svn.mplayerhq.hu/nut/docs/nut.txt?view=co">Specification</a>] - [<a href=download.html>Download and SVN</a>] - [<a href=documentation.html>Documentation</a>] + [<a href="download.html">Download and SVN</a>] + [<a href="documentation.html">Documentation</a>] [<a href="http://lists.mplayerhq.hu/mailman/listinfo/nut-devel">Mailing List</a>] </center> -<br> </body></html>

1 0

[nut]: r520 - homepage/index.html
by diego 31 Jan '08

31 Jan '08

Author: diego Date: Thu Jan 31 09:57:15 2008 New Revision: 520 Log: This is the 21st century, the charset should be UTF-8. Modified: homepage/index.html Modified: homepage/index.html ============================================================================== --- homepage/index.html (original) +++ homepage/index.html Thu Jan 31 09:57:15 2008 @@ -2,7 +2,7 @@ <html> <head> - <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <title>NUT Open Container Format</title> </head>

1 0

[nut]: r518 - docs/nut.txt
by diego 31 Jan '08

31 Jan '08

Author: diego Date: Thu Jan 31 09:54:54 2008 New Revision: 518 Log: spelling/wording Modified: docs/nut.txt Modified: docs/nut.txt ============================================================================== --- docs/nut.txt (original) +++ docs/nut.txt Thu Jan 31 09:54:54 2008 @@ -863,9 +863,9 @@ info packet types Note: MUST be less than 64 bytes long. "Replaces" v (stream id) - This stream is a supperior alternative (higher resolution or - otherwise) of the given stream. And it should be preferred over it if - the decoder is capable of decoding it. + This stream is a superior alternative (higher resolution or otherwise) + of the given stream. It should be preferred if the decoder is capable + of decoding it. "UsesFont" "Times New Roman", "Arial", ... FIXME should we use the filename instead? is there some other unique way to identify fonts?

1 0

attachments
by Michael Niedermayer 17 Jan '08

17 Jan '08

Hi How are attachments (cd cover image, fonts for subtitles, ...) supposed to be stored in nut? As i originally designed things, info packets should have been used. But after changes upon which some fanatically insisted info packets no longer are flexible enough. They are required to be repeated after every header and they can only apply to a single stream. Neither of these limitations was in the original design. So for 10 subtitle streams, we would need a minimum of 30 copies of all fonts. My original design could have stored a version of the font and still kept proper references so that it was known to the demuxer which streams the attachment applied to. -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB I do not agree with what you have to say, but I'll defend to the death your right to say it. -- Voltaire

6 14

[PATCH][RFC] keyframes
by Michael Niedermayer 17 Jan '08

17 Jan '08

Hi attached patch would change nut.txt to the alternative keyframe definition this would allow files with no classic keyframes but instead things like P frames where each would have 10% intra blocks to be muxed in nut and still allow seeking without this seeking is not possible, the seek to non keyframe hack would only work if all streams would allow seeking to any frame as back ptrs would not be meaningfull in such a file it would also fix cases where B frames with a PTS after the previous I frame would use frames prior to the I frame for prediction and it could be used to allow decoding B frames with a PTS prior to the last I frame, that is IPBBIBB ^^ if they dont use previous frames for prediction this would fix a missing feature relative to mpeg1/2/4 which allow that and provide enough information to make this odd case easily detectable Compatibility effects: new demuxers can always demux old files old demuxers can demux new files as long as they only contain normal keyframes otherwise they fail to demux the specific keyframes Effects on optimal seeking: unknown -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB No human being will ever know the Truth, for even if they happen to say it by chance, they would not even known they had done so. -- Xenophanes

3 5

[nut]: r517 - docs/nut.txt
by michael 17 Jan '08

17 Jan '08

Author: michael Date: Thu Jan 17 02:31:37 2008 New Revision: 517 Log: UsesFont info tag This is orthogonal to the question of where or how to store the font. It is usefull on its own, that is even if the font is not in the movie, this tag can keep track of which fonts are used by a stream. Modified: docs/nut.txt Modified: docs/nut.txt ============================================================================== --- docs/nut.txt (original) +++ docs/nut.txt Thu Jan 17 02:31:37 2008 @@ -866,6 +866,11 @@ info packet types This stream is a supperior alternative (higher resolution or otherwise) of the given stream. And it should be preferred over it if the decoder is capable of decoding it. + "UsesFont" + "Times New Roman", "Arial", ... FIXME should we use the filename + instead? is there some other unique way to identify fonts? + This stream uses the specified font, if it is unavailable presentation + might be less pretty. value value of this name/type pair

1 0

[nut]: r516 - docs/nut.txt
by michael 16 Jan '08

16 Jan '08

Author: michael Date: Wed Jan 16 21:08:03 2008 New Revision: 516 Log: "SourceFilename" info tag Modified: docs/nut.txt Modified: docs/nut.txt ============================================================================== --- docs/nut.txt (original) +++ docs/nut.txt Wed Jan 16 21:08:03 2008 @@ -835,6 +835,8 @@ info packet types "SourceCodecTag" The source codec ID like a FourCC which was used to store a specific stream in its SourceContainer. + "SourceFilename" + The filename of the source. "CaptureDevice" "BT878", "BT848", "webcam", ... (or more precise names) "CreationTime"

1 0

[nut]: r515 - docs/nut.txt
by michael 16 Jan '08

16 Jan '08

Author: michael Date: Wed Jan 16 21:02:15 2008 New Revision: 515 Log: "Replaces" tag Comments welcome Modified: docs/nut.txt Modified: docs/nut.txt ============================================================================== --- docs/nut.txt (original) +++ docs/nut.txt Wed Jan 16 21:02:15 2008 @@ -859,6 +859,11 @@ info packet types Note: Names of fields SHOULD be in English if a word with the same meaning exists in English. Note: MUST be less than 64 bytes long. + "Replaces" + v (stream id) + This stream is a supperior alternative (higher resolution or + otherwise) of the given stream. And it should be preferred over it if + the decoder is capable of decoding it. value value of this name/type pair

1 0