From: Stefano Sabatini <stefasab@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Stefano Sabatini <stefasab@gmail.com> Subject: [FFmpeg-devel] [PATCH 3/6] doc/muxers: add avif Date: Sun, 14 Jan 2024 17:39:12 +0100 Message-ID: <20240114163912.496806-1-stefasab@gmail.com> (raw) --- doc/muxers.texi | 28 +++++++++++++++++++++++++++- 1 file changed, 27 insertions(+), 1 deletion(-) diff --git a/doc/muxers.texi b/doc/muxers.texi index 1636f16cab..0d163a1629 100644 --- a/doc/muxers.texi +++ b/doc/muxers.texi @@ -835,6 +835,33 @@ compatibility with software that only supports a single audio stream in AVI (see @ref{amerge,,the "amerge" section in the ffmpeg-filters manual,ffmpeg-filters}). @end table +@section avif +AV1 (Alliance for Open Media Video codec 1) image format muxer. + +This muxers stores images encoded using the AV1 codec. + +It accepts one or two video streams. In case two video streams are +provided, the second one shall contain a single plane storing the +alpha mask. + +In case more than one image is provided, the generated output is +considered an animated AVIF and the number of loops can be specified +with the @option{loop} option. + +This is based on the specification by Alliance for Open Media at url +@url{https://aomediacodec.github.io/av1-avif}. + +@subsection Options +@table @option +@item loop @var{count} +number of times to loop an animated AVIF, @code{0} specify an infinite +loop, default is @code{0} + +@item movie_timescale @var{timescale} +Set the timescale written in the movie header box (@code{mvhd}). +Range is 1 to INT_MAX. Default is @code{1000}. +@end table + @anchor{chromaprint} @section chromaprint @@ -2048,7 +2075,6 @@ If a PNG image is used, it must use the rgba pixel format @anchor{image2} @section image2 - Image file muxer. The image file muxer writes video frames to image files. -- 2.34.1 _______________________________________________ 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".
reply other threads:[~2024-01-14 16:39 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240114163912.496806-1-stefasab@gmail.com \ --to=stefasab@gmail.com \ --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