Web Codecs #209

Activity

1. adamroach

   added

   venue: W3C CGSpecifications in W3C Community Groups (e.g., WICG, Privacy CG)Specifications in W3C Community Groups (e.g., WICG, Privacy CG)

   on Nov 16, 2019
2. dbaron commented on Mar 20, 2020

   

   dbaron

   on Mar 20, 2020

   Contributor

   More actions

   So I think we've used under consideration as "we're currently discussing what position to take" (sometimes for too long!), whereas defer means that we want to wait for further information in order to take a position. But perhaps (given that I'm responding 5 months later!) we now have more information?

   @padenot , what do you think of it these days?
3. dbaron

   added

   awaiting feedbackAwaiting feedback from other Mozillians (request must have either been emailed or acknowledged)Awaiting feedback from other Mozillians (request must have either been emailed or acknowledged)

   on Apr 3, 2020
4. dbaron

   added

   ready to addAppears ready to add to the table of positions.Appears ready to add to the table of positions.

   and removed

   awaiting feedbackAwaiting feedback from other Mozillians (request must have either been emailed or acknowledged)Awaiting feedback from other Mozillians (request must have either been emailed or acknowledged)

   on Apr 10, 2020
5. padenot commented on Apr 14, 2020

   

   padenot

   on Apr 14, 2020

   CollaboratorAuthor

   More actions

   This is worth prototyping (and we're following closely and participating to the design discussions), for the following reasons:

   • this steers away from the accidental design of all the APIs around encoding and decoding of media on the web (that have been designed to solve use-cases in an ad hoc way, over the years), and designs a system instead of solving a use-case, which is what we should do in general, and haven't done in this particular domain
   • this proposes a path that is not only designed carefully to be composable with existing APIs, but also extensible by authors in JS and WASM, and to allow solving all use-cases possible when it comes to media (including really re-implementing higher-level constructs such as HTMLMediaElement or MediaRecorder, without real loss of performance)
   • this solves real problems that developers have, judging by the issues opened on media-related specs, stackoverflow questions asked, and generally the apps that are not available on the web but available on other platforms

   Additionally, it's been decided in the W3C Audio Working Group that further development of the Web Audio API standard will not include encoding and decoding capabilities, to focus on on processing. Encoding and decoding is better served by its own API.
6. dbaron

   added a commit that references this issue on Apr 14, 2020

   Add Web Codecs (worth prototyping).

   ...

   This issue will close once commit 8937d29 is merged into the 'master' branch.

   8937d29
7. martinthomson commented on Apr 15, 2020

   

   martinthomson

   on Apr 15, 2020

   Member

   More actions

   There is a view of this that less rosy in that this design is likely incompatible with our strategy for confidential calling in WebRTC. But that doesn't need to change this outcome.
8. dbaron

   closed this as completedin #312on Apr 15, 2020
9. dbaron

   added a commit that references this issue on Apr 15, 2020

   Add Web Codecs (worth prototyping). (#312)

   ...

   This issue will close once commit de55fdb is merged into the 'main' branch.

   de55fdb
10. zcorpan

    added

    position: positive

    and removed

    ready to addAppears ready to add to the table of positions.Appears ready to add to the table of positions.

    on Sep 13, 2024