21376 2013-03-22 17:35:40 +0000 Use of last decode timestamp 2013-04-08 21:21:45 +0000 1 1 1 Unclassified HTML WG Media Source Extensions unspecified PC Windows NT RESOLVED FIXED P2 normal --- 1 cyril.concolato acolwell acolwell mike public-html-media public-html-bugzilla oldest_to_newest 84852 0 cyril.concolato 2013-03-22 17:35:40 +0000 It is not clear why appending a coded frame whose decode timestamp is between the last decode timestamp and last decode timestamp + 100ms should trigger an error. What is the rationale for '100 ms' ? Also, since the tests are made in decode order, maybe the Append Sequence definition should be clarified to say "monotonically increasing in *decode* time". 84939 1 acolwell 2013-03-25 19:25:53 +0000 (In reply to comment #0) > It is not clear why appending a coded frame whose decode timestamp is > between the last decode timestamp and last decode timestamp + 100ms should > trigger an error. What is the rationale for '100 ms' ? Like the note states, this is to detect out of order appends. 100ms seemed like a reasonable default that allows a little bit of flexibility on how far apart coded frames are. > > Also, since the tests are made in decode order, maybe the Append Sequence > definition should be clarified to say "monotonically increasing in *decode* > time". I'll add this in the next spec update. 85001 2 cyril.concolato 2013-03-26 08:09:48 +0000 (In reply to comment #1) > (In reply to comment #0) > > It is not clear why appending a coded frame whose decode timestamp is > > between the last decode timestamp and last decode timestamp + 100ms should > > trigger an error. What is the rationale for '100 ms' ? > > Like the note states, this is to detect out of order appends. 100ms seemed > like a reasonable default that allows a little bit of flexibility on how far > apart coded frames are. I thought the note was about the first part (decode timestamp < last decode timestamp). It's a bit akward to me to have to rely on hard-coded numbers to detect out-of-order appends. What if you have very low frame rates? Why not have a gap-threshold attribute or use something like last decode timestamp + 2xduration of the previous frame? > > > > Also, since the tests are made in decode order, maybe the Append Sequence > > definition should be clarified to say "monotonically increasing in *decode* > > time". > > I'll add this in the next spec update. Thanks. 85018 3 acolwell 2013-03-26 17:58:38 +0000 Changes committed. https://dvcs.w3.org/hg/html-media/rev/1e6898152c5b Decode time clarification to Append Sequence added. 85743 4 acolwell 2013-04-08 21:21:45 +0000 Change committed. https://dvcs.w3.org/hg/html-media/rev/f7f2b7226543 Converted 100ms limit to 2x last frame duration limit.