- From: <bugzilla@jessica.w3.org>
- Date: Wed, 15 May 2013 19:59:51 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22052 Bug ID: 22052 Summary: Report statistics on errored video frames Classification: Unclassified Product: HTML WG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: Media Source Extensions Assignee: adrianba@microsoft.com Reporter: watsonm@netflix.com QA Contact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-media@w3.org We have found that in a system which is sufficiently large scale, things which "cannot possibly happen", do happen. For example, media data which has been checksummed at the server and delivered over reliable connections sometimes suffers from data corruption, causing errors in the video decoder. Another possibility is that a media file is not in fact compliant to the codec profile that it claims to be, although in our system this is either less common or doesn't cause errors. We would like to be able to detect and report on these cases. One proposal would be to add an 'erroredFrames' counter to the MediaPlaybackQuality object. Errored frames may either be rendered (with errors) or dropped based on the media player implementation. We should discuss whether dropped errored frames (where the error is due to the input data, not lack of time to complete decoding) should be included in the dropped frames counter. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 15 May 2013 19:59:56 UTC