Re: [FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-06-27 Thread James Zern
On Mon, Jun 27, 2022 at 9:48 AM James Almer  wrote:
>
> On 6/27/2022 1:43 PM, Vignesh Venkatasubramanian wrote:
> > On Tue, Jun 21, 2022 at 10:12 AM Vignesh Venkatasubramanian
> >  wrote:
> >>
> >> On Mon, Jun 13, 2022 at 10:17 AM James Zern
> >>  wrote:
> >>>
> >>> On Wed, Jun 1, 2022 at 11:06 AM Vignesh Venkatasubramanian
> >>>  wrote:
> 
>  AVIF specification allows for alpha channel as an auxiliary item (in
>  case of still images) or as an auxiliary track (in case of animated
>  images).  Add support for both of these. The AVIF muxer will take
>  exactly two streams (when alpha is present) as input (first one being
>  the YUV planes and the second one being the alpha plane).
> 
>  The input has to come from two different images (one of it color and
>  the other one being alpha), or it can come from a single file
>  source with the alpha channel extracted using the "alphaextract"
>  filter.
> 
>  Example using alphaextract:
>  ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map 
>  "[a]" -still-picture 1 avif_with_alpha.avif
> 
>  Example using two sources (first source can be in any pixel format and
>  the second source has to be in monochrome grey pixel format):
>  ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy 
>  avif_with_alpha.avif
> 
>  The generated files pass the compliance checks in Compliance Warden:
>  https://github.com/gpac/ComplianceWarden
> 
>  libavif (the reference avif library) is able to decode the files
>  generated using this patch.
> 
>  They also play back properly (with transparent background) in:
>  1) Chrome
>  2) Firefox (only still AVIF, no animation support)
> 
>  Signed-off-by: Vignesh Venkatasubramanian 
>  ---
>    libavformat/movenc.c | 188 +--
>    libavformat/movenc.h |   4 +-
>    2 files changed, 130 insertions(+), 62 deletions(-)
> 
> >>>
> >>> lgtm.
> >>> ___
> >>> ffmpeg-devel mailing list
> >>> ffmpeg-devel@ffmpeg.org
> >>> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> >>>
> >>> To unsubscribe, visit link above, or email
> >>> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
> >>
> >> Any more comments on this? If not can this be merged please? :)
> >>
> >
> > Another ping on this please.
> >
> >> --
> >> Vignesh
>
> I thought James Zern had push access, which is why i didn't apply it as
> soon as he reviewed it. Sorry.
>
> Pushed it now.
>

Sorry for the confusion James. I held off because I'm not a maintainer
of this file, so I wanted to make sure there was another reviewer.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-06-27 Thread Vignesh Venkatasubramanian
On Mon, Jun 27, 2022 at 9:48 AM James Almer  wrote:
>
> On 6/27/2022 1:43 PM, Vignesh Venkatasubramanian wrote:
> > On Tue, Jun 21, 2022 at 10:12 AM Vignesh Venkatasubramanian
> >  wrote:
> >>
> >> On Mon, Jun 13, 2022 at 10:17 AM James Zern
> >>  wrote:
> >>>
> >>> On Wed, Jun 1, 2022 at 11:06 AM Vignesh Venkatasubramanian
> >>>  wrote:
> 
>  AVIF specification allows for alpha channel as an auxiliary item (in
>  case of still images) or as an auxiliary track (in case of animated
>  images).  Add support for both of these. The AVIF muxer will take
>  exactly two streams (when alpha is present) as input (first one being
>  the YUV planes and the second one being the alpha plane).
> 
>  The input has to come from two different images (one of it color and
>  the other one being alpha), or it can come from a single file
>  source with the alpha channel extracted using the "alphaextract"
>  filter.
> 
>  Example using alphaextract:
>  ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map 
>  "[a]" -still-picture 1 avif_with_alpha.avif
> 
>  Example using two sources (first source can be in any pixel format and
>  the second source has to be in monochrome grey pixel format):
>  ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy 
>  avif_with_alpha.avif
> 
>  The generated files pass the compliance checks in Compliance Warden:
>  https://github.com/gpac/ComplianceWarden
> 
>  libavif (the reference avif library) is able to decode the files
>  generated using this patch.
> 
>  They also play back properly (with transparent background) in:
>  1) Chrome
>  2) Firefox (only still AVIF, no animation support)
> 
>  Signed-off-by: Vignesh Venkatasubramanian 
>  ---
>    libavformat/movenc.c | 188 +--
>    libavformat/movenc.h |   4 +-
>    2 files changed, 130 insertions(+), 62 deletions(-)
> 
> >>>
> >>> lgtm.
> >>> ___
> >>> ffmpeg-devel mailing list
> >>> ffmpeg-devel@ffmpeg.org
> >>> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> >>>
> >>> To unsubscribe, visit link above, or email
> >>> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
> >>
> >> Any more comments on this? If not can this be merged please? :)
> >>
> >
> > Another ping on this please.
> >
> >> --
> >> Vignesh
>
> I thought James Zern had push access, which is why i didn't apply it as
> soon as he reviewed it. Sorry.
>
> Pushed it now.
>

Thanks!
 ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".



-- 
Vignesh
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-06-27 Thread James Almer

On 6/27/2022 1:43 PM, Vignesh Venkatasubramanian wrote:

On Tue, Jun 21, 2022 at 10:12 AM Vignesh Venkatasubramanian
 wrote:


On Mon, Jun 13, 2022 at 10:17 AM James Zern
 wrote:


On Wed, Jun 1, 2022 at 11:06 AM Vignesh Venkatasubramanian
 wrote:


AVIF specification allows for alpha channel as an auxiliary item (in
case of still images) or as an auxiliary track (in case of animated
images).  Add support for both of these. The AVIF muxer will take
exactly two streams (when alpha is present) as input (first one being
the YUV planes and the second one being the alpha plane).

The input has to come from two different images (one of it color and
the other one being alpha), or it can come from a single file
source with the alpha channel extracted using the "alphaextract"
filter.

Example using alphaextract:
ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map "[a]" 
-still-picture 1 avif_with_alpha.avif

Example using two sources (first source can be in any pixel format and
the second source has to be in monochrome grey pixel format):
ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy avif_with_alpha.avif

The generated files pass the compliance checks in Compliance Warden:
https://github.com/gpac/ComplianceWarden

libavif (the reference avif library) is able to decode the files
generated using this patch.

They also play back properly (with transparent background) in:
1) Chrome
2) Firefox (only still AVIF, no animation support)

Signed-off-by: Vignesh Venkatasubramanian 
---
  libavformat/movenc.c | 188 +--
  libavformat/movenc.h |   4 +-
  2 files changed, 130 insertions(+), 62 deletions(-)



lgtm.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".


Any more comments on this? If not can this be merged please? :)



Another ping on this please.


--
Vignesh


I thought James Zern had push access, which is why i didn't apply it as 
soon as he reviewed it. Sorry.


Pushed it now.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-06-27 Thread Vignesh Venkatasubramanian
On Tue, Jun 21, 2022 at 10:12 AM Vignesh Venkatasubramanian
 wrote:
>
> On Mon, Jun 13, 2022 at 10:17 AM James Zern
>  wrote:
> >
> > On Wed, Jun 1, 2022 at 11:06 AM Vignesh Venkatasubramanian
> >  wrote:
> > >
> > > AVIF specification allows for alpha channel as an auxiliary item (in
> > > case of still images) or as an auxiliary track (in case of animated
> > > images).  Add support for both of these. The AVIF muxer will take
> > > exactly two streams (when alpha is present) as input (first one being
> > > the YUV planes and the second one being the alpha plane).
> > >
> > > The input has to come from two different images (one of it color and
> > > the other one being alpha), or it can come from a single file
> > > source with the alpha channel extracted using the "alphaextract"
> > > filter.
> > >
> > > Example using alphaextract:
> > > ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map 
> > > "[a]" -still-picture 1 avif_with_alpha.avif
> > >
> > > Example using two sources (first source can be in any pixel format and
> > > the second source has to be in monochrome grey pixel format):
> > > ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy 
> > > avif_with_alpha.avif
> > >
> > > The generated files pass the compliance checks in Compliance Warden:
> > > https://github.com/gpac/ComplianceWarden
> > >
> > > libavif (the reference avif library) is able to decode the files
> > > generated using this patch.
> > >
> > > They also play back properly (with transparent background) in:
> > > 1) Chrome
> > > 2) Firefox (only still AVIF, no animation support)
> > >
> > > Signed-off-by: Vignesh Venkatasubramanian 
> > > ---
> > >  libavformat/movenc.c | 188 +--
> > >  libavformat/movenc.h |   4 +-
> > >  2 files changed, 130 insertions(+), 62 deletions(-)
> > >
> >
> > lgtm.
> > ___
> > ffmpeg-devel mailing list
> > ffmpeg-devel@ffmpeg.org
> > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> >
> > To unsubscribe, visit link above, or email
> > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
>
> Any more comments on this? If not can this be merged please? :)
>

Another ping on this please.

> --
> Vignesh



-- 
Vignesh
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-06-21 Thread Vignesh Venkatasubramanian
On Mon, Jun 13, 2022 at 10:17 AM James Zern
 wrote:
>
> On Wed, Jun 1, 2022 at 11:06 AM Vignesh Venkatasubramanian
>  wrote:
> >
> > AVIF specification allows for alpha channel as an auxiliary item (in
> > case of still images) or as an auxiliary track (in case of animated
> > images).  Add support for both of these. The AVIF muxer will take
> > exactly two streams (when alpha is present) as input (first one being
> > the YUV planes and the second one being the alpha plane).
> >
> > The input has to come from two different images (one of it color and
> > the other one being alpha), or it can come from a single file
> > source with the alpha channel extracted using the "alphaextract"
> > filter.
> >
> > Example using alphaextract:
> > ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map "[a]" 
> > -still-picture 1 avif_with_alpha.avif
> >
> > Example using two sources (first source can be in any pixel format and
> > the second source has to be in monochrome grey pixel format):
> > ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy avif_with_alpha.avif
> >
> > The generated files pass the compliance checks in Compliance Warden:
> > https://github.com/gpac/ComplianceWarden
> >
> > libavif (the reference avif library) is able to decode the files
> > generated using this patch.
> >
> > They also play back properly (with transparent background) in:
> > 1) Chrome
> > 2) Firefox (only still AVIF, no animation support)
> >
> > Signed-off-by: Vignesh Venkatasubramanian 
> > ---
> >  libavformat/movenc.c | 188 +--
> >  libavformat/movenc.h |   4 +-
> >  2 files changed, 130 insertions(+), 62 deletions(-)
> >
>
> lgtm.
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".

Any more comments on this? If not can this be merged please? :)

-- 
Vignesh
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-06-13 Thread James Zern
On Wed, Jun 1, 2022 at 11:06 AM Vignesh Venkatasubramanian
 wrote:
>
> AVIF specification allows for alpha channel as an auxiliary item (in
> case of still images) or as an auxiliary track (in case of animated
> images).  Add support for both of these. The AVIF muxer will take
> exactly two streams (when alpha is present) as input (first one being
> the YUV planes and the second one being the alpha plane).
>
> The input has to come from two different images (one of it color and
> the other one being alpha), or it can come from a single file
> source with the alpha channel extracted using the "alphaextract"
> filter.
>
> Example using alphaextract:
> ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map "[a]" 
> -still-picture 1 avif_with_alpha.avif
>
> Example using two sources (first source can be in any pixel format and
> the second source has to be in monochrome grey pixel format):
> ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy avif_with_alpha.avif
>
> The generated files pass the compliance checks in Compliance Warden:
> https://github.com/gpac/ComplianceWarden
>
> libavif (the reference avif library) is able to decode the files
> generated using this patch.
>
> They also play back properly (with transparent background) in:
> 1) Chrome
> 2) Firefox (only still AVIF, no animation support)
>
> Signed-off-by: Vignesh Venkatasubramanian 
> ---
>  libavformat/movenc.c | 188 +--
>  libavformat/movenc.h |   4 +-
>  2 files changed, 130 insertions(+), 62 deletions(-)
>

lgtm.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-06-13 Thread Vignesh Venkatasubramanian
On Mon, Jun 6, 2022 at 9:29 AM Vignesh Venkatasubramanian
 wrote:
>
> On Wed, Jun 1, 2022 at 12:47 PM Vignesh Venkatasubramanian
>  wrote:
> >
> > On Wed, Jun 1, 2022 at 11:52 AM xyesbee  wrote:
> > >
> > > Why can it not accept it as one but two distinct streams? Why the extra 
> > > hurdle of alphaextract? YUVA pixel format exists though.
> >
> > Yes, while the YUVA pixel formats exist, AVIF specification requires
> > alpha channel to be a separate track (i.e.) we would need two AV1
> > encoders to make an AVIF image with alpha channel (one for the YUV
> > planes and one for the alpha plane encoded as a monochrome frame). The
> > underlying AV1 codec does not support the YUVA pixel format. So, in
> > order to be able to encode an AVIF image with alpha channel, we would
> > have to separate the alpha channel with the alphaextract filter and
> > pass it to a separate AV1 encoder.
> >
> > If you already have the alpha channel as a separate input, then you
> > can simply pass it along as a second input stream and there will be no
> > need to use the alphaextract filter. I pointed out the use of
> > alphaextract filter simply because it is the simplest way to re-encode
> > existing PNG images with alpha channel into AVIF.
> >
> > An alternative solution is to use the YUVA pixel format and internally
> > use two AV1 encoders in the libaom wrapper. But that requires more
> > changes and does not really make things any better. If you have a
> > better solution, please let me know and I can update this.
> >
> > >  Original Message 
> > > On Jun 1, 2022, 11:35 PM, Vignesh Venkatasubramanian wrote:
> > >
> > > > AVIF specification allows for alpha channel as an auxiliary item (in
> > > > case of still images) or as an auxiliary track (in case of animated
> > > > images). Add support for both of these. The AVIF muxer will take
> > > > exactly two streams (when alpha is present) as input (first one being
> > > > the YUV planes and the second one being the alpha plane).
> > > >
> > > > The input has to come from two different images (one of it color and
> > > > the other one being alpha), or it can come from a single file
> > > > source with the alpha channel extracted using the "alphaextract"
> > > > filter.
> > > >
> > > > Example using alphaextract:
> > > > ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map 
> > > > "[a]" -still-picture 1 avif_with_alpha.avif
> > > >
> > > > Example using two sources (first source can be in any pixel format and
> > > > the second source has to be in monochrome grey pixel format):
> > > > ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy 
> > > > avif_with_alpha.avif
> > > >
> > > > The generated files pass the compliance checks in Compliance Warden:
> > > > https://github.com/gpac/ComplianceWarden
> > > >
> > > > libavif (the reference avif library) is able to decode the files
> > > > generated using this patch.
> > > >
> > > > They also play back properly (with transparent background) in:
> > > > 1) Chrome
> > > > 2) Firefox (only still AVIF, no animation support)
> > > >
> > > > Signed-off-by: Vignesh Venkatasubramanian 
> > > > ---
> > > > libavformat/movenc.c | 188 +--
> > > > libavformat/movenc.h | 4 +-
> > > > 2 files changed, 130 insertions(+), 62 deletions(-)
> > > >
> > > > diff --git a/libavformat/movenc.c b/libavformat/movenc.c
> > > > index de971f94e8..02eb4d0e9a 100644
> > > > --- a/libavformat/movenc.c
> > > > +++ b/libavformat/movenc.c
> > > > @@ -2852,7 +2852,7 @@ static int mov_write_hdlr_tag(AVFormatContext *s, 
> > > > AVIOContext *pb, MOVTrack *tra
> > > > hdlr = (track->mode == MODE_MOV) ? "mhlr" : "\0\0\0\0";
> > > > if (track->par->codec_type == AVMEDIA_TYPE_VIDEO) {
> > > > if (track->mode == MODE_AVIF) {
> > > > - hdlr_type = "pict";
> > > > + hdlr_type = (track == &mov->tracks[0]) ? "pict" : "auxv";
> > > > descr = "PictureHandler";
> > > > } else {
> > > > hdlr_type = "vide";
> > > > @@ -2940,57 +2940,83 @@ static int mov_write_iloc_tag(AVIOContext *pb, 
> > > > MOVMuxContext *mov, AVFormatConte
> > > > avio_wb32(pb, 0); /* Version & flags */
> > > > avio_w8(pb, (4 << 4) + 4); /* offset_size(4) and length_size(4) */
> > > > avio_w8(pb, 0); /* base_offset_size(4) and reserved(4) */
> > > > - avio_wb16(pb, 1); /* item_count */
> > > > + avio_wb16(pb, s->nb_streams); /* item_count */
> > > >
> > > > - avio_wb16(pb, 1); /* item_id */
> > > > - avio_wb16(pb, 0); /* data_reference_index */
> > > > - avio_wb16(pb, 1); /* extent_count */
> > > > - mov->avif_extent_pos = avio_tell(pb);
> > > > - avio_wb32(pb, 0); /* extent_offset (written later) */
> > > > - // For animated AVIF, we simply write the first packet's size.
> > > > - avio_wb32(pb, mov->avif_extent_length); /* extent_length */
> > > > + for (int i = 0; i < s->nb_streams; i++) {
> > > > + avio_wb16(pb, i + 1); /* item_id */
> > > > + avio_wb16(pb, 0); /* data_reference_index */
> > > > + avio_wb16(pb, 1); /* extent_count */

Re: [FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-06-06 Thread Vignesh Venkatasubramanian
On Wed, Jun 1, 2022 at 12:47 PM Vignesh Venkatasubramanian
 wrote:
>
> On Wed, Jun 1, 2022 at 11:52 AM xyesbee  wrote:
> >
> > Why can it not accept it as one but two distinct streams? Why the extra 
> > hurdle of alphaextract? YUVA pixel format exists though.
>
> Yes, while the YUVA pixel formats exist, AVIF specification requires
> alpha channel to be a separate track (i.e.) we would need two AV1
> encoders to make an AVIF image with alpha channel (one for the YUV
> planes and one for the alpha plane encoded as a monochrome frame). The
> underlying AV1 codec does not support the YUVA pixel format. So, in
> order to be able to encode an AVIF image with alpha channel, we would
> have to separate the alpha channel with the alphaextract filter and
> pass it to a separate AV1 encoder.
>
> If you already have the alpha channel as a separate input, then you
> can simply pass it along as a second input stream and there will be no
> need to use the alphaextract filter. I pointed out the use of
> alphaextract filter simply because it is the simplest way to re-encode
> existing PNG images with alpha channel into AVIF.
>
> An alternative solution is to use the YUVA pixel format and internally
> use two AV1 encoders in the libaom wrapper. But that requires more
> changes and does not really make things any better. If you have a
> better solution, please let me know and I can update this.
>
> >  Original Message 
> > On Jun 1, 2022, 11:35 PM, Vignesh Venkatasubramanian wrote:
> >
> > > AVIF specification allows for alpha channel as an auxiliary item (in
> > > case of still images) or as an auxiliary track (in case of animated
> > > images). Add support for both of these. The AVIF muxer will take
> > > exactly two streams (when alpha is present) as input (first one being
> > > the YUV planes and the second one being the alpha plane).
> > >
> > > The input has to come from two different images (one of it color and
> > > the other one being alpha), or it can come from a single file
> > > source with the alpha channel extracted using the "alphaextract"
> > > filter.
> > >
> > > Example using alphaextract:
> > > ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map 
> > > "[a]" -still-picture 1 avif_with_alpha.avif
> > >
> > > Example using two sources (first source can be in any pixel format and
> > > the second source has to be in monochrome grey pixel format):
> > > ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy 
> > > avif_with_alpha.avif
> > >
> > > The generated files pass the compliance checks in Compliance Warden:
> > > https://github.com/gpac/ComplianceWarden
> > >
> > > libavif (the reference avif library) is able to decode the files
> > > generated using this patch.
> > >
> > > They also play back properly (with transparent background) in:
> > > 1) Chrome
> > > 2) Firefox (only still AVIF, no animation support)
> > >
> > > Signed-off-by: Vignesh Venkatasubramanian 
> > > ---
> > > libavformat/movenc.c | 188 +--
> > > libavformat/movenc.h | 4 +-
> > > 2 files changed, 130 insertions(+), 62 deletions(-)
> > >
> > > diff --git a/libavformat/movenc.c b/libavformat/movenc.c
> > > index de971f94e8..02eb4d0e9a 100644
> > > --- a/libavformat/movenc.c
> > > +++ b/libavformat/movenc.c
> > > @@ -2852,7 +2852,7 @@ static int mov_write_hdlr_tag(AVFormatContext *s, 
> > > AVIOContext *pb, MOVTrack *tra
> > > hdlr = (track->mode == MODE_MOV) ? "mhlr" : "\0\0\0\0";
> > > if (track->par->codec_type == AVMEDIA_TYPE_VIDEO) {
> > > if (track->mode == MODE_AVIF) {
> > > - hdlr_type = "pict";
> > > + hdlr_type = (track == &mov->tracks[0]) ? "pict" : "auxv";
> > > descr = "PictureHandler";
> > > } else {
> > > hdlr_type = "vide";
> > > @@ -2940,57 +2940,83 @@ static int mov_write_iloc_tag(AVIOContext *pb, 
> > > MOVMuxContext *mov, AVFormatConte
> > > avio_wb32(pb, 0); /* Version & flags */
> > > avio_w8(pb, (4 << 4) + 4); /* offset_size(4) and length_size(4) */
> > > avio_w8(pb, 0); /* base_offset_size(4) and reserved(4) */
> > > - avio_wb16(pb, 1); /* item_count */
> > > + avio_wb16(pb, s->nb_streams); /* item_count */
> > >
> > > - avio_wb16(pb, 1); /* item_id */
> > > - avio_wb16(pb, 0); /* data_reference_index */
> > > - avio_wb16(pb, 1); /* extent_count */
> > > - mov->avif_extent_pos = avio_tell(pb);
> > > - avio_wb32(pb, 0); /* extent_offset (written later) */
> > > - // For animated AVIF, we simply write the first packet's size.
> > > - avio_wb32(pb, mov->avif_extent_length); /* extent_length */
> > > + for (int i = 0; i < s->nb_streams; i++) {
> > > + avio_wb16(pb, i + 1); /* item_id */
> > > + avio_wb16(pb, 0); /* data_reference_index */
> > > + avio_wb16(pb, 1); /* extent_count */
> > > + mov->avif_extent_pos[i] = avio_tell(pb);
> > > + avio_wb32(pb, 0); /* extent_offset (written later) */
> > > + // For animated AVIF, we simply write the first packet's size.
> > > + avio_wb32(pb, mov->avif_extent_length[i]); /* extent_length */
> > > + }
> > 

Re: [FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-06-01 Thread Vignesh Venkatasubramanian
On Wed, Jun 1, 2022 at 11:52 AM xyesbee  wrote:
>
> Why can it not accept it as one but two distinct streams? Why the extra 
> hurdle of alphaextract? YUVA pixel format exists though.

Yes, while the YUVA pixel formats exist, AVIF specification requires
alpha channel to be a separate track (i.e.) we would need two AV1
encoders to make an AVIF image with alpha channel (one for the YUV
planes and one for the alpha plane encoded as a monochrome frame). The
underlying AV1 codec does not support the YUVA pixel format. So, in
order to be able to encode an AVIF image with alpha channel, we would
have to separate the alpha channel with the alphaextract filter and
pass it to a separate AV1 encoder.

If you already have the alpha channel as a separate input, then you
can simply pass it along as a second input stream and there will be no
need to use the alphaextract filter. I pointed out the use of
alphaextract filter simply because it is the simplest way to re-encode
existing PNG images with alpha channel into AVIF.

An alternative solution is to use the YUVA pixel format and internally
use two AV1 encoders in the libaom wrapper. But that requires more
changes and does not really make things any better. If you have a
better solution, please let me know and I can update this.

>  Original Message 
> On Jun 1, 2022, 11:35 PM, Vignesh Venkatasubramanian wrote:
>
> > AVIF specification allows for alpha channel as an auxiliary item (in
> > case of still images) or as an auxiliary track (in case of animated
> > images). Add support for both of these. The AVIF muxer will take
> > exactly two streams (when alpha is present) as input (first one being
> > the YUV planes and the second one being the alpha plane).
> >
> > The input has to come from two different images (one of it color and
> > the other one being alpha), or it can come from a single file
> > source with the alpha channel extracted using the "alphaextract"
> > filter.
> >
> > Example using alphaextract:
> > ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map "[a]" 
> > -still-picture 1 avif_with_alpha.avif
> >
> > Example using two sources (first source can be in any pixel format and
> > the second source has to be in monochrome grey pixel format):
> > ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy avif_with_alpha.avif
> >
> > The generated files pass the compliance checks in Compliance Warden:
> > https://github.com/gpac/ComplianceWarden
> >
> > libavif (the reference avif library) is able to decode the files
> > generated using this patch.
> >
> > They also play back properly (with transparent background) in:
> > 1) Chrome
> > 2) Firefox (only still AVIF, no animation support)
> >
> > Signed-off-by: Vignesh Venkatasubramanian 
> > ---
> > libavformat/movenc.c | 188 +--
> > libavformat/movenc.h | 4 +-
> > 2 files changed, 130 insertions(+), 62 deletions(-)
> >
> > diff --git a/libavformat/movenc.c b/libavformat/movenc.c
> > index de971f94e8..02eb4d0e9a 100644
> > --- a/libavformat/movenc.c
> > +++ b/libavformat/movenc.c
> > @@ -2852,7 +2852,7 @@ static int mov_write_hdlr_tag(AVFormatContext *s, 
> > AVIOContext *pb, MOVTrack *tra
> > hdlr = (track->mode == MODE_MOV) ? "mhlr" : "\0\0\0\0";
> > if (track->par->codec_type == AVMEDIA_TYPE_VIDEO) {
> > if (track->mode == MODE_AVIF) {
> > - hdlr_type = "pict";
> > + hdlr_type = (track == &mov->tracks[0]) ? "pict" : "auxv";
> > descr = "PictureHandler";
> > } else {
> > hdlr_type = "vide";
> > @@ -2940,57 +2940,83 @@ static int mov_write_iloc_tag(AVIOContext *pb, 
> > MOVMuxContext *mov, AVFormatConte
> > avio_wb32(pb, 0); /* Version & flags */
> > avio_w8(pb, (4 << 4) + 4); /* offset_size(4) and length_size(4) */
> > avio_w8(pb, 0); /* base_offset_size(4) and reserved(4) */
> > - avio_wb16(pb, 1); /* item_count */
> > + avio_wb16(pb, s->nb_streams); /* item_count */
> >
> > - avio_wb16(pb, 1); /* item_id */
> > - avio_wb16(pb, 0); /* data_reference_index */
> > - avio_wb16(pb, 1); /* extent_count */
> > - mov->avif_extent_pos = avio_tell(pb);
> > - avio_wb32(pb, 0); /* extent_offset (written later) */
> > - // For animated AVIF, we simply write the first packet's size.
> > - avio_wb32(pb, mov->avif_extent_length); /* extent_length */
> > + for (int i = 0; i < s->nb_streams; i++) {
> > + avio_wb16(pb, i + 1); /* item_id */
> > + avio_wb16(pb, 0); /* data_reference_index */
> > + avio_wb16(pb, 1); /* extent_count */
> > + mov->avif_extent_pos[i] = avio_tell(pb);
> > + avio_wb32(pb, 0); /* extent_offset (written later) */
> > + // For animated AVIF, we simply write the first packet's size.
> > + avio_wb32(pb, mov->avif_extent_length[i]); /* extent_length */
> > + }
> >
> > return update_size(pb, pos);
> > }
> >
> > static int mov_write_iinf_tag(AVIOContext *pb, MOVMuxContext *mov, 
> > AVFormatContext *s)
> > {
> > - int64_t infe_pos;
> > int64_t iinf_pos = avio_tell(pb);
> > avio_wb32(pb, 0); /* size */
> > ffio_wfourcc(pb, "iinf");
> > 

[FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-06-01 Thread Vignesh Venkatasubramanian
AVIF specification allows for alpha channel as an auxiliary item (in
case of still images) or as an auxiliary track (in case of animated
images).  Add support for both of these. The AVIF muxer will take
exactly two streams (when alpha is present) as input (first one being
the YUV planes and the second one being the alpha plane).

The input has to come from two different images (one of it color and
the other one being alpha), or it can come from a single file
source with the alpha channel extracted using the "alphaextract"
filter.

Example using alphaextract:
ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map "[a]" 
-still-picture 1 avif_with_alpha.avif

Example using two sources (first source can be in any pixel format and
the second source has to be in monochrome grey pixel format):
ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy avif_with_alpha.avif

The generated files pass the compliance checks in Compliance Warden:
https://github.com/gpac/ComplianceWarden

libavif (the reference avif library) is able to decode the files
generated using this patch.

They also play back properly (with transparent background) in:
1) Chrome
2) Firefox (only still AVIF, no animation support)

Signed-off-by: Vignesh Venkatasubramanian 
---
 libavformat/movenc.c | 188 +--
 libavformat/movenc.h |   4 +-
 2 files changed, 130 insertions(+), 62 deletions(-)

diff --git a/libavformat/movenc.c b/libavformat/movenc.c
index de971f94e8..02eb4d0e9a 100644
--- a/libavformat/movenc.c
+++ b/libavformat/movenc.c
@@ -2852,7 +2852,7 @@ static int mov_write_hdlr_tag(AVFormatContext *s, 
AVIOContext *pb, MOVTrack *tra
 hdlr = (track->mode == MODE_MOV) ? "mhlr" : "\0\0\0\0";
 if (track->par->codec_type == AVMEDIA_TYPE_VIDEO) {
 if (track->mode == MODE_AVIF) {
-hdlr_type = "pict";
+hdlr_type = (track == &mov->tracks[0]) ? "pict" : "auxv";
 descr = "PictureHandler";
 } else {
 hdlr_type = "vide";
@@ -2940,57 +2940,83 @@ static int mov_write_iloc_tag(AVIOContext *pb, 
MOVMuxContext *mov, AVFormatConte
 avio_wb32(pb, 0); /* Version & flags */
 avio_w8(pb, (4 << 4) + 4); /* offset_size(4) and length_size(4) */
 avio_w8(pb, 0); /* base_offset_size(4) and reserved(4) */
-avio_wb16(pb, 1); /* item_count */
+avio_wb16(pb, s->nb_streams); /* item_count */
 
-avio_wb16(pb, 1); /* item_id */
-avio_wb16(pb, 0); /* data_reference_index */
-avio_wb16(pb, 1); /* extent_count */
-mov->avif_extent_pos = avio_tell(pb);
-avio_wb32(pb, 0); /* extent_offset (written later) */
-// For animated AVIF, we simply write the first packet's size.
-avio_wb32(pb, mov->avif_extent_length); /* extent_length */
+for (int i = 0; i < s->nb_streams; i++) {
+avio_wb16(pb, i + 1); /* item_id */
+avio_wb16(pb, 0); /* data_reference_index */
+avio_wb16(pb, 1); /* extent_count */
+mov->avif_extent_pos[i] = avio_tell(pb);
+avio_wb32(pb, 0); /* extent_offset (written later) */
+// For animated AVIF, we simply write the first packet's size.
+avio_wb32(pb, mov->avif_extent_length[i]); /* extent_length */
+}
 
 return update_size(pb, pos);
 }
 
 static int mov_write_iinf_tag(AVIOContext *pb, MOVMuxContext *mov, 
AVFormatContext *s)
 {
-int64_t infe_pos;
 int64_t iinf_pos = avio_tell(pb);
 avio_wb32(pb, 0); /* size */
 ffio_wfourcc(pb, "iinf");
 avio_wb32(pb, 0); /* Version & flags */
-avio_wb16(pb, 1); /* entry_count */
+avio_wb16(pb, s->nb_streams); /* entry_count */
 
-infe_pos = avio_tell(pb);
-avio_wb32(pb, 0); /* size */
-ffio_wfourcc(pb, "infe");
-avio_w8(pb, 0x2); /* Version */
-avio_wb24(pb, 0); /* flags */
-avio_wb16(pb, 1); /* item_id */
-avio_wb16(pb, 0); /* item_protection_index */
-avio_write(pb, "av01", 4); /* item_type */
-avio_write(pb, "Color\0", 6); /* item_name */
-update_size(pb, infe_pos);
+for (int i = 0; i < s->nb_streams; i++) {
+int64_t infe_pos = avio_tell(pb);
+avio_wb32(pb, 0); /* size */
+ffio_wfourcc(pb, "infe");
+avio_w8(pb, 0x2); /* Version */
+avio_wb24(pb, 0); /* flags */
+avio_wb16(pb, i + 1); /* item_id */
+avio_wb16(pb, 0); /* item_protection_index */
+avio_write(pb, "av01", 4); /* item_type */
+avio_write(pb, !i ? "Color\0" : "Alpha\0", 6); /* item_name */
+update_size(pb, infe_pos);
+}
 
 return update_size(pb, iinf_pos);
 }
 
-static int mov_write_ispe_tag(AVIOContext *pb, MOVMuxContext *mov, 
AVFormatContext *s)
+
+static int mov_write_iref_tag(AVIOContext *pb, MOVMuxContext *mov, 
AVFormatContext *s)
+{
+int64_t auxl_pos;
+int64_t iref_pos = avio_tell(pb);
+avio_wb32(pb, 0); /* size */
+ffio_wfourcc(pb, "iref");
+avio_wb32(pb, 0); /* Version & flags */
+
+auxl_pos = avio_tell(pb);
+

Re: [FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-06-01 Thread Vignesh Venkatasubramanian
On Wed, Jun 1, 2022 at 10:52 AM James Zern  wrote:
>
> On Wed, May 18, 2022 at 2:56 PM Vignesh Venkatasubramanian
>  wrote:
> >
> > AVIF specification allows for alpha channel as an auxillary item (in
>
> auxiliary
>

Done.

> > case of still images) or as an auxillary track (in case of animated
> > images).  Add support for both of these. The AVIF muxer will take
> > exactly two streams (when alpha is present) as input (first one being
> > the YUV planes and the second one being the alpha plane).
> >
> > The input has to come from two different images (one of it color and
> > the other one being alpha), or it can come from a single file
> > source with the alpha channel extracted using the "alphaextract"
> > filter.
> >
> > Example using alphaextract:
> > ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map "[a]" 
> > -still-picture 1 avif_with_alpha.avif
> >
> > Example using two sources (first source can be in any pixel format and
> > the second source has to be in monochrome grey pixel format):
> > ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy avif_with_alpha.avif
> >
> > The generated files pass the compliance checks in Compliance Warden:
> > https://github.com/gpac/ComplianceWarden
> >
> > libavif (the reference avif library) is able to decode the files
> > generated using this patch.
> >
> > They also play back properly (with transparent background) in:
> > 1) Chrome
> > 2) Firefox (only still AVIF, no animation support)
> >
> > Signed-off-by: Vignesh Venkatasubramanian 
> > ---
> >  libavformat/movenc.c | 185 +--
> >  libavformat/movenc.h |   4 +-
> >  2 files changed, 128 insertions(+), 61 deletions(-)
> >
> > diff --git a/libavformat/movenc.c b/libavformat/movenc.c
> > index de971f94e8..00e42b7abb 100644
> > --- a/libavformat/movenc.c
> > +++ b/libavformat/movenc.c
> > @@ -2852,7 +2852,7 @@ static int mov_write_hdlr_tag(AVFormatContext *s, 
> > AVIOContext *pb, MOVTrack *tra
> >  hdlr = (track->mode == MODE_MOV) ? "mhlr" : "\0\0\0\0";
> >  if (track->par->codec_type == AVMEDIA_TYPE_VIDEO) {
> >  if (track->mode == MODE_AVIF) {
> > -hdlr_type = "pict";
> > +hdlr_type = (track == &mov->tracks[0]) ? "pict" : "auxv";
> >  descr = "PictureHandler";
> >  } else {
> >  hdlr_type = "vide";
> > @@ -2940,57 +2940,83 @@ static int mov_write_iloc_tag(AVIOContext *pb, 
> > MOVMuxContext *mov, AVFormatConte
> >  avio_wb32(pb, 0); /* Version & flags */
> >  avio_w8(pb, (4 << 4) + 4); /* offset_size(4) and length_size(4) */
> >  avio_w8(pb, 0); /* base_offset_size(4) and reserved(4) */
> > -avio_wb16(pb, 1); /* item_count */
> > +avio_wb16(pb, s->nb_streams); /* item_count */
>
> This assumes at most 2 streams for AVIF, the use of nb_streams here and
> elsewhere carry any risk for other formats?
>

For AVIF, we check and ensure we only have at most 2 streams in
mov_init. iloc box is written only for AVIF as of now. So there is no
risk for other formats.

> > [...]
> >
> > @@ -6874,14 +6920,23 @@ static int mov_init(AVFormatContext *s)
> >
> >  /* AVIF output must have exactly one video stream */
>
> This is no longer true.
>

Updated.

> >  if (mov->mode == MODE_AVIF) {
> > -if (s->nb_streams > 1) {
> > -av_log(s, AV_LOG_ERROR, "AVIF output requires exactly one 
> > stream\n");
> > +if (s->nb_streams > 2) {
> > +av_log(s, AV_LOG_ERROR, "AVIF output requires exactly one or 
> > two streams\n");
> >  return AVERROR(EINVAL);
> >  }
> > -if (s->streams[0]->codecpar->codec_type != AVMEDIA_TYPE_VIDEO) {
> > -av_log(s, AV_LOG_ERROR, "AVIF output requires one video 
> > stream\n");
> > +if (s->streams[0]->codecpar->codec_type != AVMEDIA_TYPE_VIDEO &&
> > +(s->nb_streams > 1 && s->streams[1]->codecpar->codec_type != 
> > AVMEDIA_TYPE_VIDEO)) {
> > +av_log(s, AV_LOG_ERROR, "AVIF output supports only video 
> > streams\n");
> >  return AVERROR(EINVAL);
> >  }
> > +if (s->nb_streams > 1) {
> > +const AVPixFmtDescriptor *pixdesc =
> > +av_pix_fmt_desc_get(s->streams[1]->codecpar->format);
> > +if (pixdesc->nb_components != 1) {
> > +av_log(s, AV_LOG_ERROR, "Second stream for AVIF (alpha) 
> > output must have exactly one plane\n");
> > +return AVERROR(EINVAL);
> > +}
> > +}
> >  s->streams[0]->disposition |= AV_DISPOSITION_DEFAULT;
> >  }
> >
> > @@ -7543,18 +7598,25 @@ static int avif_write_trailer(AVFormatContext *s)
> >  {
> >  AVIOContext *pb = s->pb;
> >  MOVMuxContext *mov = s->priv_data;
> > -int64_t pos_backup, mdat_pos;
> > +int64_t pos_backup, extent_offsets[2];
> >  uint8_t *buf;
> > -int buf_size, moov_size;
> > +int buf_size, moov_size, i;
> >
> 

Re: [FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-06-01 Thread James Zern
On Wed, May 18, 2022 at 2:56 PM Vignesh Venkatasubramanian
 wrote:
>
> AVIF specification allows for alpha channel as an auxillary item (in

auxiliary

> case of still images) or as an auxillary track (in case of animated
> images).  Add support for both of these. The AVIF muxer will take
> exactly two streams (when alpha is present) as input (first one being
> the YUV planes and the second one being the alpha plane).
>
> The input has to come from two different images (one of it color and
> the other one being alpha), or it can come from a single file
> source with the alpha channel extracted using the "alphaextract"
> filter.
>
> Example using alphaextract:
> ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map "[a]" 
> -still-picture 1 avif_with_alpha.avif
>
> Example using two sources (first source can be in any pixel format and
> the second source has to be in monochrome grey pixel format):
> ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy avif_with_alpha.avif
>
> The generated files pass the compliance checks in Compliance Warden:
> https://github.com/gpac/ComplianceWarden
>
> libavif (the reference avif library) is able to decode the files
> generated using this patch.
>
> They also play back properly (with transparent background) in:
> 1) Chrome
> 2) Firefox (only still AVIF, no animation support)
>
> Signed-off-by: Vignesh Venkatasubramanian 
> ---
>  libavformat/movenc.c | 185 +--
>  libavformat/movenc.h |   4 +-
>  2 files changed, 128 insertions(+), 61 deletions(-)
>
> diff --git a/libavformat/movenc.c b/libavformat/movenc.c
> index de971f94e8..00e42b7abb 100644
> --- a/libavformat/movenc.c
> +++ b/libavformat/movenc.c
> @@ -2852,7 +2852,7 @@ static int mov_write_hdlr_tag(AVFormatContext *s, 
> AVIOContext *pb, MOVTrack *tra
>  hdlr = (track->mode == MODE_MOV) ? "mhlr" : "\0\0\0\0";
>  if (track->par->codec_type == AVMEDIA_TYPE_VIDEO) {
>  if (track->mode == MODE_AVIF) {
> -hdlr_type = "pict";
> +hdlr_type = (track == &mov->tracks[0]) ? "pict" : "auxv";
>  descr = "PictureHandler";
>  } else {
>  hdlr_type = "vide";
> @@ -2940,57 +2940,83 @@ static int mov_write_iloc_tag(AVIOContext *pb, 
> MOVMuxContext *mov, AVFormatConte
>  avio_wb32(pb, 0); /* Version & flags */
>  avio_w8(pb, (4 << 4) + 4); /* offset_size(4) and length_size(4) */
>  avio_w8(pb, 0); /* base_offset_size(4) and reserved(4) */
> -avio_wb16(pb, 1); /* item_count */
> +avio_wb16(pb, s->nb_streams); /* item_count */

This assumes at most 2 streams for AVIF, the use of nb_streams here and
elsewhere carry any risk for other formats?

> [...]
>
> @@ -6874,14 +6920,23 @@ static int mov_init(AVFormatContext *s)
>
>  /* AVIF output must have exactly one video stream */

This is no longer true.

>  if (mov->mode == MODE_AVIF) {
> -if (s->nb_streams > 1) {
> -av_log(s, AV_LOG_ERROR, "AVIF output requires exactly one 
> stream\n");
> +if (s->nb_streams > 2) {
> +av_log(s, AV_LOG_ERROR, "AVIF output requires exactly one or two 
> streams\n");
>  return AVERROR(EINVAL);
>  }
> -if (s->streams[0]->codecpar->codec_type != AVMEDIA_TYPE_VIDEO) {
> -av_log(s, AV_LOG_ERROR, "AVIF output requires one video 
> stream\n");
> +if (s->streams[0]->codecpar->codec_type != AVMEDIA_TYPE_VIDEO &&
> +(s->nb_streams > 1 && s->streams[1]->codecpar->codec_type != 
> AVMEDIA_TYPE_VIDEO)) {
> +av_log(s, AV_LOG_ERROR, "AVIF output supports only video 
> streams\n");
>  return AVERROR(EINVAL);
>  }
> +if (s->nb_streams > 1) {
> +const AVPixFmtDescriptor *pixdesc =
> +av_pix_fmt_desc_get(s->streams[1]->codecpar->format);
> +if (pixdesc->nb_components != 1) {
> +av_log(s, AV_LOG_ERROR, "Second stream for AVIF (alpha) 
> output must have exactly one plane\n");
> +return AVERROR(EINVAL);
> +}
> +}
>  s->streams[0]->disposition |= AV_DISPOSITION_DEFAULT;
>  }
>
> @@ -7543,18 +7598,25 @@ static int avif_write_trailer(AVFormatContext *s)
>  {
>  AVIOContext *pb = s->pb;
>  MOVMuxContext *mov = s->priv_data;
> -int64_t pos_backup, mdat_pos;
> +int64_t pos_backup, extent_offsets[2];
>  uint8_t *buf;
> -int buf_size, moov_size;
> +int buf_size, moov_size, i;
>
>  if (mov->moov_written) return 0;
>
>  mov->is_animated_avif = s->streams[0]->nb_frames > 1;
> +if (mov->is_animated_avif && s->nb_streams > 1) {
> +// For animated avif with alpha channel, we need to write a the tref

...write a tref...
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-

Re: [FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-05-31 Thread Vignesh Venkatasubramanian
On Thu, May 19, 2022 at 9:08 AM Vignesh Venkatasubramanian
 wrote:
>
> On Wed, May 18, 2022 at 7:36 PM Bang He  wrote:
> >
> > error happened:
> >
> > ./ffmpeg -i alpha.png -filter_complex [0:v]alphaextract[a] -map 0 -map [a]
> > -still-picture 1 avif_with_alpha.avif
> > ffmpeg version N-106936-gff5ea89da2 Copyright (c) 2000-2022 the FFmpeg
> > developers
> >   built with gcc 11 (Ubuntu 11.2.0-19ubuntu1)
> >   configuration: --disable-ffplay --disable-ffprobe --enable-gpl
> > --enable-nonfree --prefix=/home/bang/Desktop/out
> >   libavutil  57. 24.101 / 57. 24.101
> >   libavcodec 59. 28.100 / 59. 28.100
> >   libavformat59. 24.100 / 59. 24.100
> >   libavdevice59.  6.100 / 59.  6.100
> >   libavfilter 8. 38.100 /  8. 38.100
> >   libswscale  6.  6.100 /  6.  6.100
> >   libswresample   4.  6.100 /  4.  6.100
> >   libpostproc56.  5.100 / 56.  5.100
> > Unrecognized option 'still-picture'.
> > Error splitting the argument list: Option not found
> >
>
> You would have to build ffmpeg with libaom enabled for AVIF encoding
> to work (since AVIF is backed by an AV1 encoder). From the logs you
> posted, it seems like you don't have an AV1 encoder available in your
> ffmpeg build.
>
> The "-still-picture" flag was added in ab05e9a7f2. Please make sure
> that you are sync'ed past that to pick up that option.
>
> > On Thu, May 19, 2022 at 5:56 AM Vignesh Venkatasubramanian <
> > vigneshv-at-google@ffmpeg.org> wrote:
> >
> > > AVIF specification allows for alpha channel as an auxillary item (in
> > > case of still images) or as an auxillary track (in case of animated
> > > images).  Add support for both of these. The AVIF muxer will take
> > > exactly two streams (when alpha is present) as input (first one being
> > > the YUV planes and the second one being the alpha plane).
> > >
> > > The input has to come from two different images (one of it color and
> > > the other one being alpha), or it can come from a single file
> > > source with the alpha channel extracted using the "alphaextract"
> > > filter.
> > >
> > > Example using alphaextract:
> > > ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map
> > > "[a]" -still-picture 1 avif_with_alpha.avif
> > >
> > > Example using two sources (first source can be in any pixel format and
> > > the second source has to be in monochrome grey pixel format):
> > > ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy
> > > avif_with_alpha.avif
> > >
> > > The generated files pass the compliance checks in Compliance Warden:
> > > https://github.com/gpac/ComplianceWarden
> > >
> > > libavif (the reference avif library) is able to decode the files
> > > generated using this patch.
> > >
> > > They also play back properly (with transparent background) in:
> > > 1) Chrome
> > > 2) Firefox (only still AVIF, no animation support)
> > >
> > > Signed-off-by: Vignesh Venkatasubramanian 
> > > ---
> > >  libavformat/movenc.c | 185 +--
> > >  libavformat/movenc.h |   4 +-
> > >  2 files changed, 128 insertions(+), 61 deletions(-)
> > >
> > > diff --git a/libavformat/movenc.c b/libavformat/movenc.c
> > > index de971f94e8..00e42b7abb 100644
> > > --- a/libavformat/movenc.c
> > > +++ b/libavformat/movenc.c
> > > @@ -2852,7 +2852,7 @@ static int mov_write_hdlr_tag(AVFormatContext *s,
> > > AVIOContext *pb, MOVTrack *tra
> > >  hdlr = (track->mode == MODE_MOV) ? "mhlr" : "\0\0\0\0";
> > >  if (track->par->codec_type == AVMEDIA_TYPE_VIDEO) {
> > >  if (track->mode == MODE_AVIF) {
> > > -hdlr_type = "pict";
> > > +hdlr_type = (track == &mov->tracks[0]) ? "pict" : "auxv";
> > >  descr = "PictureHandler";
> > >  } else {
> > >  hdlr_type = "vide";
> > > @@ -2940,57 +2940,83 @@ static int mov_write_iloc_tag(AVIOContext *pb,
> > > MOVMuxContext *mov, AVFormatConte
> > >  avio_wb32(pb, 0); /* Version & flags */
> > >  avio_w8(pb, (4 << 4) + 4); /* offset_size(4) and length_size(4) */
> > >  avio_w8(pb, 0); /* base_offset_size(4) and reserved(4) */
> > > -avio_wb16(pb, 1); /* item_count */
> > > +avio_wb16(pb, s->nb_streams); /* item_count */
> > >
> > > -avio_wb16(pb, 1); /* item_id */
> > > -avio_wb16(pb, 0); /* data_reference_index */
> > > -avio_wb16(pb, 1); /* extent_count */
> > > -mov->avif_extent_pos = avio_tell(pb);
> > > -avio_wb32(pb, 0); /* extent_offset (written later) */
> > > -// For animated AVIF, we simply write the first packet's size.
> > > -avio_wb32(pb, mov->avif_extent_length); /* extent_length */
> > > +for (int i = 0; i < s->nb_streams; i++) {
> > > +avio_wb16(pb, i + 1); /* item_id */
> > > +avio_wb16(pb, 0); /* data_reference_index */
> > > +avio_wb16(pb, 1); /* extent_count */
> > > +mov->avif_extent_pos[i] = avio_tell(pb);
> > > +avio_wb32(pb, 0); /* extent_offset (written later) */
> >

Re: [FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-05-19 Thread Vignesh Venkatasubramanian
On Wed, May 18, 2022 at 7:36 PM Bang He  wrote:
>
> error happened:
>
> ./ffmpeg -i alpha.png -filter_complex [0:v]alphaextract[a] -map 0 -map [a]
> -still-picture 1 avif_with_alpha.avif
> ffmpeg version N-106936-gff5ea89da2 Copyright (c) 2000-2022 the FFmpeg
> developers
>   built with gcc 11 (Ubuntu 11.2.0-19ubuntu1)
>   configuration: --disable-ffplay --disable-ffprobe --enable-gpl
> --enable-nonfree --prefix=/home/bang/Desktop/out
>   libavutil  57. 24.101 / 57. 24.101
>   libavcodec 59. 28.100 / 59. 28.100
>   libavformat59. 24.100 / 59. 24.100
>   libavdevice59.  6.100 / 59.  6.100
>   libavfilter 8. 38.100 /  8. 38.100
>   libswscale  6.  6.100 /  6.  6.100
>   libswresample   4.  6.100 /  4.  6.100
>   libpostproc56.  5.100 / 56.  5.100
> Unrecognized option 'still-picture'.
> Error splitting the argument list: Option not found
>

You would have to build ffmpeg with libaom enabled for AVIF encoding
to work (since AVIF is backed by an AV1 encoder). From the logs you
posted, it seems like you don't have an AV1 encoder available in your
ffmpeg build.

The "-still-picture" flag was added in ab05e9a7f2. Please make sure
that you are sync'ed past that to pick up that option.

> On Thu, May 19, 2022 at 5:56 AM Vignesh Venkatasubramanian <
> vigneshv-at-google@ffmpeg.org> wrote:
>
> > AVIF specification allows for alpha channel as an auxillary item (in
> > case of still images) or as an auxillary track (in case of animated
> > images).  Add support for both of these. The AVIF muxer will take
> > exactly two streams (when alpha is present) as input (first one being
> > the YUV planes and the second one being the alpha plane).
> >
> > The input has to come from two different images (one of it color and
> > the other one being alpha), or it can come from a single file
> > source with the alpha channel extracted using the "alphaextract"
> > filter.
> >
> > Example using alphaextract:
> > ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map
> > "[a]" -still-picture 1 avif_with_alpha.avif
> >
> > Example using two sources (first source can be in any pixel format and
> > the second source has to be in monochrome grey pixel format):
> > ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy
> > avif_with_alpha.avif
> >
> > The generated files pass the compliance checks in Compliance Warden:
> > https://github.com/gpac/ComplianceWarden
> >
> > libavif (the reference avif library) is able to decode the files
> > generated using this patch.
> >
> > They also play back properly (with transparent background) in:
> > 1) Chrome
> > 2) Firefox (only still AVIF, no animation support)
> >
> > Signed-off-by: Vignesh Venkatasubramanian 
> > ---
> >  libavformat/movenc.c | 185 +--
> >  libavformat/movenc.h |   4 +-
> >  2 files changed, 128 insertions(+), 61 deletions(-)
> >
> > diff --git a/libavformat/movenc.c b/libavformat/movenc.c
> > index de971f94e8..00e42b7abb 100644
> > --- a/libavformat/movenc.c
> > +++ b/libavformat/movenc.c
> > @@ -2852,7 +2852,7 @@ static int mov_write_hdlr_tag(AVFormatContext *s,
> > AVIOContext *pb, MOVTrack *tra
> >  hdlr = (track->mode == MODE_MOV) ? "mhlr" : "\0\0\0\0";
> >  if (track->par->codec_type == AVMEDIA_TYPE_VIDEO) {
> >  if (track->mode == MODE_AVIF) {
> > -hdlr_type = "pict";
> > +hdlr_type = (track == &mov->tracks[0]) ? "pict" : "auxv";
> >  descr = "PictureHandler";
> >  } else {
> >  hdlr_type = "vide";
> > @@ -2940,57 +2940,83 @@ static int mov_write_iloc_tag(AVIOContext *pb,
> > MOVMuxContext *mov, AVFormatConte
> >  avio_wb32(pb, 0); /* Version & flags */
> >  avio_w8(pb, (4 << 4) + 4); /* offset_size(4) and length_size(4) */
> >  avio_w8(pb, 0); /* base_offset_size(4) and reserved(4) */
> > -avio_wb16(pb, 1); /* item_count */
> > +avio_wb16(pb, s->nb_streams); /* item_count */
> >
> > -avio_wb16(pb, 1); /* item_id */
> > -avio_wb16(pb, 0); /* data_reference_index */
> > -avio_wb16(pb, 1); /* extent_count */
> > -mov->avif_extent_pos = avio_tell(pb);
> > -avio_wb32(pb, 0); /* extent_offset (written later) */
> > -// For animated AVIF, we simply write the first packet's size.
> > -avio_wb32(pb, mov->avif_extent_length); /* extent_length */
> > +for (int i = 0; i < s->nb_streams; i++) {
> > +avio_wb16(pb, i + 1); /* item_id */
> > +avio_wb16(pb, 0); /* data_reference_index */
> > +avio_wb16(pb, 1); /* extent_count */
> > +mov->avif_extent_pos[i] = avio_tell(pb);
> > +avio_wb32(pb, 0); /* extent_offset (written later) */
> > +// For animated AVIF, we simply write the first packet's size.
> > +avio_wb32(pb, mov->avif_extent_length[i]); /* extent_length */
> > +}
> >
> >  return update_size(pb, pos);
> >  }
> >
> >  static int mov_write_iinf_tag(AVIOContext *pb, MOVMuxConte

Re: [FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-05-18 Thread Bang He
error happened:

./ffmpeg -i alpha.png -filter_complex [0:v]alphaextract[a] -map 0 -map [a]
-still-picture 1 avif_with_alpha.avif
ffmpeg version N-106936-gff5ea89da2 Copyright (c) 2000-2022 the FFmpeg
developers
  built with gcc 11 (Ubuntu 11.2.0-19ubuntu1)
  configuration: --disable-ffplay --disable-ffprobe --enable-gpl
--enable-nonfree --prefix=/home/bang/Desktop/out
  libavutil  57. 24.101 / 57. 24.101
  libavcodec 59. 28.100 / 59. 28.100
  libavformat59. 24.100 / 59. 24.100
  libavdevice59.  6.100 / 59.  6.100
  libavfilter 8. 38.100 /  8. 38.100
  libswscale  6.  6.100 /  6.  6.100
  libswresample   4.  6.100 /  4.  6.100
  libpostproc56.  5.100 / 56.  5.100
Unrecognized option 'still-picture'.
Error splitting the argument list: Option not found

On Thu, May 19, 2022 at 5:56 AM Vignesh Venkatasubramanian <
vigneshv-at-google@ffmpeg.org> wrote:

> AVIF specification allows for alpha channel as an auxillary item (in
> case of still images) or as an auxillary track (in case of animated
> images).  Add support for both of these. The AVIF muxer will take
> exactly two streams (when alpha is present) as input (first one being
> the YUV planes and the second one being the alpha plane).
>
> The input has to come from two different images (one of it color and
> the other one being alpha), or it can come from a single file
> source with the alpha channel extracted using the "alphaextract"
> filter.
>
> Example using alphaextract:
> ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map
> "[a]" -still-picture 1 avif_with_alpha.avif
>
> Example using two sources (first source can be in any pixel format and
> the second source has to be in monochrome grey pixel format):
> ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy
> avif_with_alpha.avif
>
> The generated files pass the compliance checks in Compliance Warden:
> https://github.com/gpac/ComplianceWarden
>
> libavif (the reference avif library) is able to decode the files
> generated using this patch.
>
> They also play back properly (with transparent background) in:
> 1) Chrome
> 2) Firefox (only still AVIF, no animation support)
>
> Signed-off-by: Vignesh Venkatasubramanian 
> ---
>  libavformat/movenc.c | 185 +--
>  libavformat/movenc.h |   4 +-
>  2 files changed, 128 insertions(+), 61 deletions(-)
>
> diff --git a/libavformat/movenc.c b/libavformat/movenc.c
> index de971f94e8..00e42b7abb 100644
> --- a/libavformat/movenc.c
> +++ b/libavformat/movenc.c
> @@ -2852,7 +2852,7 @@ static int mov_write_hdlr_tag(AVFormatContext *s,
> AVIOContext *pb, MOVTrack *tra
>  hdlr = (track->mode == MODE_MOV) ? "mhlr" : "\0\0\0\0";
>  if (track->par->codec_type == AVMEDIA_TYPE_VIDEO) {
>  if (track->mode == MODE_AVIF) {
> -hdlr_type = "pict";
> +hdlr_type = (track == &mov->tracks[0]) ? "pict" : "auxv";
>  descr = "PictureHandler";
>  } else {
>  hdlr_type = "vide";
> @@ -2940,57 +2940,83 @@ static int mov_write_iloc_tag(AVIOContext *pb,
> MOVMuxContext *mov, AVFormatConte
>  avio_wb32(pb, 0); /* Version & flags */
>  avio_w8(pb, (4 << 4) + 4); /* offset_size(4) and length_size(4) */
>  avio_w8(pb, 0); /* base_offset_size(4) and reserved(4) */
> -avio_wb16(pb, 1); /* item_count */
> +avio_wb16(pb, s->nb_streams); /* item_count */
>
> -avio_wb16(pb, 1); /* item_id */
> -avio_wb16(pb, 0); /* data_reference_index */
> -avio_wb16(pb, 1); /* extent_count */
> -mov->avif_extent_pos = avio_tell(pb);
> -avio_wb32(pb, 0); /* extent_offset (written later) */
> -// For animated AVIF, we simply write the first packet's size.
> -avio_wb32(pb, mov->avif_extent_length); /* extent_length */
> +for (int i = 0; i < s->nb_streams; i++) {
> +avio_wb16(pb, i + 1); /* item_id */
> +avio_wb16(pb, 0); /* data_reference_index */
> +avio_wb16(pb, 1); /* extent_count */
> +mov->avif_extent_pos[i] = avio_tell(pb);
> +avio_wb32(pb, 0); /* extent_offset (written later) */
> +// For animated AVIF, we simply write the first packet's size.
> +avio_wb32(pb, mov->avif_extent_length[i]); /* extent_length */
> +}
>
>  return update_size(pb, pos);
>  }
>
>  static int mov_write_iinf_tag(AVIOContext *pb, MOVMuxContext *mov,
> AVFormatContext *s)
>  {
> -int64_t infe_pos;
>  int64_t iinf_pos = avio_tell(pb);
>  avio_wb32(pb, 0); /* size */
>  ffio_wfourcc(pb, "iinf");
>  avio_wb32(pb, 0); /* Version & flags */
> -avio_wb16(pb, 1); /* entry_count */
> +avio_wb16(pb, s->nb_streams); /* entry_count */
>
> -infe_pos = avio_tell(pb);
> -avio_wb32(pb, 0); /* size */
> -ffio_wfourcc(pb, "infe");
> -avio_w8(pb, 0x2); /* Version */
> -avio_wb24(pb, 0); /* flags */
> -avio_wb16(pb, 1); /* item_id */
> -avio_wb16(pb, 0); /* item_protection_index */
> -avi

Re: [FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-05-18 Thread Bang He
some error happened:

On Thu, May 19, 2022 at 5:56 AM Vignesh Venkatasubramanian <
vigneshv-at-google@ffmpeg.org> wrote:

> AVIF specification allows for alpha channel as an auxillary item (in
> case of still images) or as an auxillary track (in case of animated
> images).  Add support for both of these. The AVIF muxer will take
> exactly two streams (when alpha is present) as input (first one being
> the YUV planes and the second one being the alpha plane).
>
> The input has to come from two different images (one of it color and
> the other one being alpha), or it can come from a single file
> source with the alpha channel extracted using the "alphaextract"
> filter.
>
> Example using alphaextract:
> ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map
> "[a]" -still-picture 1 avif_with_alpha.avif
>
> Example using two sources (first source can be in any pixel format and
> the second source has to be in monochrome grey pixel format):
> ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy
> avif_with_alpha.avif
>
> The generated files pass the compliance checks in Compliance Warden:
> https://github.com/gpac/ComplianceWarden
>
> libavif (the reference avif library) is able to decode the files
> generated using this patch.
>
> They also play back properly (with transparent background) in:
> 1) Chrome
> 2) Firefox (only still AVIF, no animation support)
>
> Signed-off-by: Vignesh Venkatasubramanian 
> ---
>  libavformat/movenc.c | 185 +--
>  libavformat/movenc.h |   4 +-
>  2 files changed, 128 insertions(+), 61 deletions(-)
>
> diff --git a/libavformat/movenc.c b/libavformat/movenc.c
> index de971f94e8..00e42b7abb 100644
> --- a/libavformat/movenc.c
> +++ b/libavformat/movenc.c
> @@ -2852,7 +2852,7 @@ static int mov_write_hdlr_tag(AVFormatContext *s,
> AVIOContext *pb, MOVTrack *tra
>  hdlr = (track->mode == MODE_MOV) ? "mhlr" : "\0\0\0\0";
>  if (track->par->codec_type == AVMEDIA_TYPE_VIDEO) {
>  if (track->mode == MODE_AVIF) {
> -hdlr_type = "pict";
> +hdlr_type = (track == &mov->tracks[0]) ? "pict" : "auxv";
>  descr = "PictureHandler";
>  } else {
>  hdlr_type = "vide";
> @@ -2940,57 +2940,83 @@ static int mov_write_iloc_tag(AVIOContext *pb,
> MOVMuxContext *mov, AVFormatConte
>  avio_wb32(pb, 0); /* Version & flags */
>  avio_w8(pb, (4 << 4) + 4); /* offset_size(4) and length_size(4) */
>  avio_w8(pb, 0); /* base_offset_size(4) and reserved(4) */
> -avio_wb16(pb, 1); /* item_count */
> +avio_wb16(pb, s->nb_streams); /* item_count */
>
> -avio_wb16(pb, 1); /* item_id */
> -avio_wb16(pb, 0); /* data_reference_index */
> -avio_wb16(pb, 1); /* extent_count */
> -mov->avif_extent_pos = avio_tell(pb);
> -avio_wb32(pb, 0); /* extent_offset (written later) */
> -// For animated AVIF, we simply write the first packet's size.
> -avio_wb32(pb, mov->avif_extent_length); /* extent_length */
> +for (int i = 0; i < s->nb_streams; i++) {
> +avio_wb16(pb, i + 1); /* item_id */
> +avio_wb16(pb, 0); /* data_reference_index */
> +avio_wb16(pb, 1); /* extent_count */
> +mov->avif_extent_pos[i] = avio_tell(pb);
> +avio_wb32(pb, 0); /* extent_offset (written later) */
> +// For animated AVIF, we simply write the first packet's size.
> +avio_wb32(pb, mov->avif_extent_length[i]); /* extent_length */
> +}
>
>  return update_size(pb, pos);
>  }
>
>  static int mov_write_iinf_tag(AVIOContext *pb, MOVMuxContext *mov,
> AVFormatContext *s)
>  {
> -int64_t infe_pos;
>  int64_t iinf_pos = avio_tell(pb);
>  avio_wb32(pb, 0); /* size */
>  ffio_wfourcc(pb, "iinf");
>  avio_wb32(pb, 0); /* Version & flags */
> -avio_wb16(pb, 1); /* entry_count */
> +avio_wb16(pb, s->nb_streams); /* entry_count */
>
> -infe_pos = avio_tell(pb);
> -avio_wb32(pb, 0); /* size */
> -ffio_wfourcc(pb, "infe");
> -avio_w8(pb, 0x2); /* Version */
> -avio_wb24(pb, 0); /* flags */
> -avio_wb16(pb, 1); /* item_id */
> -avio_wb16(pb, 0); /* item_protection_index */
> -avio_write(pb, "av01", 4); /* item_type */
> -avio_write(pb, "Color\0", 6); /* item_name */
> -update_size(pb, infe_pos);
> +for (int i = 0; i < s->nb_streams; i++) {
> +int64_t infe_pos = avio_tell(pb);
> +avio_wb32(pb, 0); /* size */
> +ffio_wfourcc(pb, "infe");
> +avio_w8(pb, 0x2); /* Version */
> +avio_wb24(pb, 0); /* flags */
> +avio_wb16(pb, i + 1); /* item_id */
> +avio_wb16(pb, 0); /* item_protection_index */
> +avio_write(pb, "av01", 4); /* item_type */
> +avio_write(pb, !i ? "Color\0" : "Alpha\0", 6); /* item_name */
> +update_size(pb, infe_pos);
> +}
>
>  return update_size(pb, iinf_pos);
>  }
>
> -static int mov_write_ispe_tag(AVIOContext *pb, MOVMuxC

[FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF

2022-05-18 Thread Vignesh Venkatasubramanian
AVIF specification allows for alpha channel as an auxillary item (in
case of still images) or as an auxillary track (in case of animated
images).  Add support for both of these. The AVIF muxer will take
exactly two streams (when alpha is present) as input (first one being
the YUV planes and the second one being the alpha plane).

The input has to come from two different images (one of it color and
the other one being alpha), or it can come from a single file
source with the alpha channel extracted using the "alphaextract"
filter.

Example using alphaextract:
ffmpeg -i rgba.png -filter_complex "[0:v]alphaextract[a]" -map 0 -map "[a]" 
-still-picture 1 avif_with_alpha.avif

Example using two sources (first source can be in any pixel format and
the second source has to be in monochrome grey pixel format):
ffmpeg -i color.avif -i grey.avif -map 0 -map 1 -c copy avif_with_alpha.avif

The generated files pass the compliance checks in Compliance Warden:
https://github.com/gpac/ComplianceWarden

libavif (the reference avif library) is able to decode the files
generated using this patch.

They also play back properly (with transparent background) in:
1) Chrome
2) Firefox (only still AVIF, no animation support)

Signed-off-by: Vignesh Venkatasubramanian 
---
 libavformat/movenc.c | 185 +--
 libavformat/movenc.h |   4 +-
 2 files changed, 128 insertions(+), 61 deletions(-)

diff --git a/libavformat/movenc.c b/libavformat/movenc.c
index de971f94e8..00e42b7abb 100644
--- a/libavformat/movenc.c
+++ b/libavformat/movenc.c
@@ -2852,7 +2852,7 @@ static int mov_write_hdlr_tag(AVFormatContext *s, 
AVIOContext *pb, MOVTrack *tra
 hdlr = (track->mode == MODE_MOV) ? "mhlr" : "\0\0\0\0";
 if (track->par->codec_type == AVMEDIA_TYPE_VIDEO) {
 if (track->mode == MODE_AVIF) {
-hdlr_type = "pict";
+hdlr_type = (track == &mov->tracks[0]) ? "pict" : "auxv";
 descr = "PictureHandler";
 } else {
 hdlr_type = "vide";
@@ -2940,57 +2940,83 @@ static int mov_write_iloc_tag(AVIOContext *pb, 
MOVMuxContext *mov, AVFormatConte
 avio_wb32(pb, 0); /* Version & flags */
 avio_w8(pb, (4 << 4) + 4); /* offset_size(4) and length_size(4) */
 avio_w8(pb, 0); /* base_offset_size(4) and reserved(4) */
-avio_wb16(pb, 1); /* item_count */
+avio_wb16(pb, s->nb_streams); /* item_count */
 
-avio_wb16(pb, 1); /* item_id */
-avio_wb16(pb, 0); /* data_reference_index */
-avio_wb16(pb, 1); /* extent_count */
-mov->avif_extent_pos = avio_tell(pb);
-avio_wb32(pb, 0); /* extent_offset (written later) */
-// For animated AVIF, we simply write the first packet's size.
-avio_wb32(pb, mov->avif_extent_length); /* extent_length */
+for (int i = 0; i < s->nb_streams; i++) {
+avio_wb16(pb, i + 1); /* item_id */
+avio_wb16(pb, 0); /* data_reference_index */
+avio_wb16(pb, 1); /* extent_count */
+mov->avif_extent_pos[i] = avio_tell(pb);
+avio_wb32(pb, 0); /* extent_offset (written later) */
+// For animated AVIF, we simply write the first packet's size.
+avio_wb32(pb, mov->avif_extent_length[i]); /* extent_length */
+}
 
 return update_size(pb, pos);
 }
 
 static int mov_write_iinf_tag(AVIOContext *pb, MOVMuxContext *mov, 
AVFormatContext *s)
 {
-int64_t infe_pos;
 int64_t iinf_pos = avio_tell(pb);
 avio_wb32(pb, 0); /* size */
 ffio_wfourcc(pb, "iinf");
 avio_wb32(pb, 0); /* Version & flags */
-avio_wb16(pb, 1); /* entry_count */
+avio_wb16(pb, s->nb_streams); /* entry_count */
 
-infe_pos = avio_tell(pb);
-avio_wb32(pb, 0); /* size */
-ffio_wfourcc(pb, "infe");
-avio_w8(pb, 0x2); /* Version */
-avio_wb24(pb, 0); /* flags */
-avio_wb16(pb, 1); /* item_id */
-avio_wb16(pb, 0); /* item_protection_index */
-avio_write(pb, "av01", 4); /* item_type */
-avio_write(pb, "Color\0", 6); /* item_name */
-update_size(pb, infe_pos);
+for (int i = 0; i < s->nb_streams; i++) {
+int64_t infe_pos = avio_tell(pb);
+avio_wb32(pb, 0); /* size */
+ffio_wfourcc(pb, "infe");
+avio_w8(pb, 0x2); /* Version */
+avio_wb24(pb, 0); /* flags */
+avio_wb16(pb, i + 1); /* item_id */
+avio_wb16(pb, 0); /* item_protection_index */
+avio_write(pb, "av01", 4); /* item_type */
+avio_write(pb, !i ? "Color\0" : "Alpha\0", 6); /* item_name */
+update_size(pb, infe_pos);
+}
 
 return update_size(pb, iinf_pos);
 }
 
-static int mov_write_ispe_tag(AVIOContext *pb, MOVMuxContext *mov, 
AVFormatContext *s)
+
+static int mov_write_iref_tag(AVIOContext *pb, MOVMuxContext *mov, 
AVFormatContext *s)
+{
+int64_t auxl_pos;
+int64_t iref_pos = avio_tell(pb);
+avio_wb32(pb, 0); /* size */
+ffio_wfourcc(pb, "iref");
+avio_wb32(pb, 0); /* Version & flags */
+
+auxl_pos = avio_tell(pb);
+