From: Vignesh Venkatasubramanian <vigneshv-at-google.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avformat/movenc: Support alpha channel for AVIF Date: Mon, 27 Jun 2022 09:43:52 -0700 Message-ID: <CAOJaEP+M5CwKkATdc5mQ31vMHj_9HPjOCpnpZeGRVjj9bqHY1g@mail.gmail.com> (raw) In-Reply-To: <CAOJaEPJdOG732NtDvD5f4PXM9HbVHv4v6ajPPJeUT5jm0uqL2g@mail.gmail.com> On Tue, Jun 21, 2022 at 10:12 AM Vignesh Venkatasubramanian <vigneshv@google.com> wrote: > > On Mon, Jun 13, 2022 at 10:17 AM James Zern > <jzern-at-google.com@ffmpeg.org> wrote: > > > > On Wed, Jun 1, 2022 at 11:06 AM Vignesh Venkatasubramanian > > <vigneshv-at-google.com@ffmpeg.org> 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 <vigneshv@google.com> > > > --- > > > 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-request@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-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-06-27 16:44 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-18 21:56 Vignesh Venkatasubramanian 2022-05-19 2:34 ` Bang He 2022-05-19 2:36 ` Bang He 2022-05-19 16:08 ` Vignesh Venkatasubramanian 2022-05-31 19:12 ` Vignesh Venkatasubramanian 2022-06-01 17:52 ` James Zern 2022-06-01 18:05 ` Vignesh Venkatasubramanian 2022-06-01 18:05 ` Vignesh Venkatasubramanian 2022-06-01 18:52 ` xyesbee 2022-06-01 19:47 ` Vignesh Venkatasubramanian 2022-06-06 16:29 ` Vignesh Venkatasubramanian 2022-06-13 16:30 ` Vignesh Venkatasubramanian 2022-06-13 17:17 ` James Zern 2022-06-21 17:12 ` Vignesh Venkatasubramanian 2022-06-27 16:43 ` Vignesh Venkatasubramanian [this message] 2022-06-27 16:48 ` James Almer 2022-06-27 17:17 ` Vignesh Venkatasubramanian 2022-06-27 19:46 ` James Zern
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAOJaEP+M5CwKkATdc5mQ31vMHj_9HPjOCpnpZeGRVjj9bqHY1g@mail.gmail.com \ --to=vigneshv-at-google.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git