- From: <bugzilla@jessica.w3.org>
- Date: Wed, 19 Sep 2012 18:32:39 +0000
- To: public-html-media@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18920 Summary: addSourceBuffer parameter type should be optional Product: HTML WG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Media Source Extensions AssignedTo: adrianba@microsoft.com ReportedBy: whadar@gmail.com QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-media@w3.org In the current spec the initialization of the sourceBuffer requires the developer to specify the exact codec. For example: mediaSource.addSourceBuffer('video/webm; codecs="vorbis,vp8"'); mediaSource.addSourceBuffer('video/mp4; codecs="avc1.42E01E, mp4a.40.2"'); As a developer, it will make the API much more feasible and easier to use. Scenario: A website has a library of various videos in different codecs (as users upload the videos). The video is fetch using XHR and appended with MSE. Determining the mime type can be made by reading the XHR response, which must contain the real mime type and not just the generic octet stream (requirement for the webserver). Knowing the correct codec is even harder in the js level. In ISO-BMFF there are plenty of variations and the developer needs a js parser to detect which codec is used. Auto detection of the initialization segment by the browser would make the API much more accessible and developer friendly. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Wednesday, 19 September 2012 18:32:40 UTC