search

w3c / media-source

Media Source Extensions
https://w3c.github.io/media-source/
Other
268 stars 58 forks source link

Does MSE ISO-BMFF bytestream spec need updates to include vp09... codec string? #183

Closed wolenetz closed 7 years ago

wolenetz commented 7 years ago

See https://github.com/w3c/media-source/issues/180#issuecomment-303812167, copied here:

@kqyang, FYI, we probably need a similar issue for MP4. Will leave that to you.

The MP4 registry currently reads:

"MIME-types for this specification must conform to the rules outlined for "audio/mp4" and "video/mp4" in RFC 6381."

wolenetz commented 7 years ago

Following the current spec links, RFC 6381 refers video/mp4 to www.mp4ra.org, which includes "vp09" as VPxx "as defined in/by" https://github.com/Netflix/vp9-dash/blob/master/VPCodecISOMediaFileFormatBinding.docx

However, that link appears out of date, and doesn't contain the necessary information to describe a compliant "vp09" codec parameter string for use in MSE spec/API. I've generated a PR to fix the WebM bytestream spec similarly to directly reference http://www.webmproject.org/vp9/mp4/#codecs-parameter-string (which appears to be a more complete/newer version of the doc than the one referenced by mp4ra).

@kqyang, @FrankGalligan: What is the route forward to make the MSE ISOBMFF byte stream spec allow vp09.xx.xx... codec parameter strings (in isTypeSupported/addSourceBuffer portions of the API)? Does mp4ra simply need an updated reference to a doc, or is there something I'm missing? Who is doing such updates?

-- edited to fix the @ for kqyang

kqyang commented 7 years ago

Updating www.mp4ra.org should be sufficient, i.e. update it to refer to the v1 spec or the Github page. A request has already been submitted to mp4ra. It should be reflected on mp4ra website soon.

wolenetz commented 7 years ago

OK. ISTM this issue is thus external, unless mp4ra rejects the update. If they reject it, please re-activate this issue so we're aware of the change of plans.