On Sat, Feb 25, 2006 at 02:29:52PM -0500, Rich Felker wrote:
On Sat, Feb 25, 2006 at 09:03:49PM +0200, Oded Shimon wrote:
+If an info stream contains an info frame for chapter X then it MUST contain +an info frame with pts==chapter_start
1. If chapter_start is coded, then a copy of the info frame must appear at the timestamp coded in chapter_start.
10l to Rich.
2. No frame with a different chapter_id (or EOR) may appear between chapter_start and chapter_start+len.
I'm OK with that. Michael?
With the addition of these constraints, it's always possible to decode with the stream-style behavior, but when chapter_len is known it provides extra information in advance (and may improve error recovery in case a frame is lost).
BTW, one more thing: chapter_start==0 is a weird way to omit the field since 0 is also a valid pts. 0 is not a valid value for chapter_start unless pts==0 as well, so this may be ok, but there may be problems if a packet is lost.. What about just always requiring chapter_start to be coded (and equal to the pts of the first copy) and making chapter_len the only optional field?
chapter_start never implicit, chapter_len zero means implicit. OK. - ods15