21373 2013-03-22 10:22:57 +0000 Improve Coded Frame Processing and Segment Parser Loop algorithms 2013-04-04 20:40: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 pal public-html-media public-html-bugzilla oldest_to_newest 84834 0 cyril.concolato 2013-03-22 10:22:57 +0000 I think the descriptions of the Coded Frame Processing (CFP) and the Segment Parser Loop (SPL) algorithms should be improved. The CFP algorithm starts with: "When complete coded frames have been parsed by the segment parser loop then the following steps are run:" While the CFP algorithm is invoke from the SPL algo after the step: "If the input buffer does not contain a complete media segment header yet, then jump to the need more data step below." The CFP assumes that SPL has actually detected coded frame boundaries (not just the header), which is not obvious from reading the SPL algo only. To clarify that, I'd suggest moving the first sentence of CFP and including it in step 6.3 of SPL. I'd suggest also moving and rephrasing the note about progressive parsing after step 6.3. The result would be as follows: "3. If the input buffer contains one or more complete coded frames, run the coded frame processing algorithm. NOTE: The frequency at which the coded frame processing algorithm is run is implementation-specific. The coded frame processing algorithm may be called when the input buffer contains the complete media segment or only some complete coded frames." 85021 1 acolwell 2013-03-26 18:00:09 +0000 Changes committed. https://dvcs.w3.org/hg/html-media/rev/1e6898152c5b