#495: AVIF Decode

Visit on Github.

Opened Apr 7, 2020

Hello TAG!

I'm requesting a TAG review of AVIF Decode.

Further details:

  • I have reviewed the TAG's API Design Principles
  • Relevant time constraints or deadlines: N/A
  • The group where the work on this specification is currently being done:
  • The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): Alliance for Open Media
  • Major unresolved issues with or opposition to this specification: N/A
  • This work is being funded by: N/A

You should also know that...

N/A We'd prefer the TAG provide feedback as (please delete all but the desired option):

💬 leave review feedback as a comment in this issue and @-notify [github usernames]

Discussions

2020-04-13

Minutes

Dan: AVIF decoder -

Ken: I looked through this... left some comments.. on what else we need to change

Peter: seems we're lacking the proper layering...

Tess: that's what the web codecs API is supposed to do...

David: this is just a new image format...

David: web codecs is more centered around audio & video...

[discussion of how this relates to web codecs]

Peter: I would like to see - before we add new black boxes - let's make these things extensible. E.g. with webaudio...

David: other question is - what APIs do you need?

Ken: hardware acceleration - which you don't get with webassembl

2020-04-13

Minutes

Sangwhan: what do they want? I'm looking at the chrome issue tracker - this is transparent decoding.

Yves: this is in line with the crypto one - depends on the buy-in and patent related issue... not really technical.

Sangwhan: they are adding a new image format ... it's a browser feature. From a greater perspective, it should be "is the web going to add a new image format"?

Ken: too early to do a recommendation for that.

Sangwhan: this doesn't ask for any of that.

Dan: shall we propose close, summarily, and just say "it's not in TAG's wheelhouse"?

Ken: better format than web-p...

Dan: is this related to HEIC?

Sangwhan: No. Related to AV1. Key frame format for AV1.

Ken: supported by Netflix - much better quality than JPEG

Sangwhan: no hardware support. WebP has some level of hardware decoding.

Sangwhan: as a recommended format, I think we need to consider it, but as a pure technical perspective, let's not consider.

Ken: this is really good for the web because it's much more open....

Sangwhan: we should look at this in the sense of : is this an official format for the web? The web platform does definitely need a better image format.

Dan: other dependencies?

Sangwhan: clipboard

Ken: canvas API

Sangwhan: another API: Web codecs

Ken: also multiple file extensions... why? That's gonna be a pain.

2020-04-20

Minutes

Sangwhan: i don't know what they want reviewed

Ken: AOM - AV1 - for image format - these are from mpeg... heif - this is related to patents

Sangwhan: policy wise we do not discuss patents

Dan: Agree

Yves: from what I've heard - avif is believed to be RF. But not proven. And HEIF has patents.

Ken: if you read the spec, the container is based on heif .. what is inside the container is av1 based. this is based on isobmff ...

Ken: how should we ask that question... will write it.

[bumped]

2020-04-27

Minutes

Ken: No update yet.

Yves: mark as pending external feedback...

Ken: if we're not getting answers ... we should ping them...

Yves: Chris Lilley is looking into it.

[bumped]

2020-05-11

Minutes

Ken: [researches ship status in Chromium]

Sangwhan: they wanted to check with Blink owners ... was that thread updated?

Ken: no, not mentioned here...