> On 6 Aug 2018, at 10:30 pm, Boris Zbarsky <bzbar...@mit.edu> wrote: > > On 8/6/18 5:37 AM, Jean-Yves Avenard wrote: >> enable by default changeType method on MediaSource’s Source Buffer > > To be clear, this is enabling by default on all channels, right?
yes > >> The method has been availably since 61 behind the preference >> media.mediasource.experimental.enabled > > But not default-enabled anywhere, so not much tested? We have web-platform-tests for this feature which have landed… We know that YouTube intends to use this new functionality as soon as available. http://w3c-test.org/media-source/mediasource-changetype.html http://w3c-test.org/media-source/mediasource-changetype-play.html As far as test is concerned, limiting the type of codecs used was an artificial limitation to start with. So the core code involved has always been exercised since the MSE rearchitecture (which came with 42) > > How stable is the spec? Stable I believe and unlikely to change again. There’s a few “v2” MSE features in the pipeline, but they typically will require more work. > > What is the status of implementation or interest in other browsers? Chrome has it implemented behind a pref too, we haven’t discussed with others to determine their intention on that… IMHO, it’s the most useful addition made to MSE since it first came out. It will greatly improve adaptative quality streaming. I’m fairly keen to see how AV1 can be used more easily that way (which otherwise would be limited to only the most powerful machines out there) Google’s main interest for this is for ad insertions unfortunately, a bit sad when there’s so much potential. > > What is the status of interest from authors? Media Capabilities and changeType was the 2 most requested features by all content providers we’ve met this year. > > Put another way, if we thought this was a safe change why did we have it off > by default to start with? Were there substantive changes to the code since > 61 that prevented us from enabling by default before now? The implementation behind changeType followed several iterations to reach that point. At which time the Chrome team and us agreed on the current definition. I had put it behind a pref to start with as there were no specs at all defined for it. It was developed as a proof of concept, to show on what could be achieved and how easily it could be done. Our MediaSource implementation and architecture had been conceived from the ground up with this capability in mind… So we were the first to implement it and it was done very quickly. We then had a few back and forth meetings with the Chromium media team until we agreed (with compromises) on the final draft. I hope I answered all your questions. JY
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
