[NUT-devel] Re: FINALIZE NUT SPEC!!

[Oded Shimon]

On Tue, Feb 28, 2006 at 08:15:13PM +0100, Michael Niedermayer wrote:
[...]
> i really start to loose interrest in fighting against these arbitrary
> restrictions, you shouldnt add a restriction without a REASON!!!!
> not add one based on philosophical ideas and then wait until some very
> serious consequences are found

My intent was generally to reduce complexity. The general idea I have in my 
head is a console player that dumps an info frame/packet to stdout upon 
recieval. This gets trickier when you have info frame repetition, and this 
was what I was generally working for. But bleh, I guess I sucked at it. 

And _please_, I am not fighting with anyone here, especially not you.. I'm 
trying my best to actually accomplish the wishes of everyone, this includes 
writing and committing patches which so far very few of you seem to do. 
This includes sending (bad) patches, recieving reviews, and fixing the 
patches.
So please try not to flame me. :(

About patch, I consider change to "Info frames MUST have chapter_id < 0".

- ods15
-------------- next part --------------
Index: DOCS/tech/mpcf.txt
===================================================================
RCS file: /cvsroot/mplayer/main/DOCS/tech/mpcf.txt,v
retrieving revision 1.113
diff -u -r1.113 mpcf.txt
--- DOCS/tech/mpcf.txt	25 Feb 2006 18:51:46 -0000	1.113
+++ DOCS/tech/mpcf.txt	28 Feb 2006 20:07:33 -0000
@@ -640,6 +640,7 @@
 
 chapter_len
     Length of chapter in same timebase of chapter_start.
+    In info streams, chapter_len may be zero to indicate unknown length.
 
 type
     for example: "UTF8" -> string or "JPEG" -> JPEG image
@@ -734,13 +735,21 @@
 -----
 
 All info packets with the same chapter_id and stream_id are repeated info
-packets and MUST be binary identical.
+packets and MUST be binary identical. This does not apply to info streams.
 
 All info packets MUST appear after main headers at begginning of file, and
 SHOULD be repeated after all main headers unless they are very large.
 
 Info frames can be used to describe the file or some part of it (chapters)
 
+The last info frame with the same chapter_id and stream_id is the most 
+correct one, and SHOULD have chapter_len filled. (and no fields ommitted 
+unless they were incorrect)
+
+Info frames MUST have chapter_id != 0 .
+
+chapter_start and chapter_len MUST NOT use info stream timebase.
+
 Info SHOULD be stored in global packets instead of info streams/frames if
 possible, and the amount of data is not large.