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

[Michael Niedermayer]

Hi

On Tue, Feb 28, 2006 at 06:17:09AM +0200, Oded Shimon wrote:
[...]

>  chapter_len
>      Length of chapter in same timebase of chapter_start.
> +    In info streams, if chapter_len is zero, chapter_len is the pts of
> +    the first EOR or info frame with a different chapter_id in the same
> +    info stream, minus chapter_start.

iam not happy with this rule


[...]
> +The pts of an info frame MUST be >=chapter_start and <=chapter_start+len
> +(Compared using compare_ts)

not acceptable, as it totally defeats the idea of updating info frames later


> +
> +Info frames with a different chapter_id (or EOR) MUST NOT appear between
> +chapter_start and chapter_start+len. For overlapping chapters several info
> +streams can be used.

not acceptable, same reason as above


> +
> +If an info stream contains an info frame for chapter X then it MUST contain
> +an info frame with pts==chapter_start. Due to this restriction, the only
> +legal timebase for chapter_start (and chapter_len) is the info stream
> +timebase.

not acceptable, as it makes remuxing from info streams to info packets
impossible (yeah the timebases might not match ...)


> +
> +Info frames with the same chapter_id and stream_id MUST have the same
> +chapter_start and chapter_len if it is non zero. The last info frame with
> +the same chapter_id and stream_id is the most correct one, and SHOULD have
> +chapter_len filled.

iam weakly against this restriction, the last packet should be used otherwise
errors in chapter_start/len cannot be fixed in realtime streams

[...]

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

-- 
Michael