From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libavif: enable encoding support
Date: Sat, 25 Feb 2023 06:28:47 +0100 [thread overview]
Message-ID: <20230225052847.mE5l_Y8n7szzoKL5zSZ5rCFfNeba6zav2xYJvw5QL9c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42438@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/42438#issuecomment-1444999291
Comment:
You can specify the encoder you want to use (although it can fallback to other encoders).
https://github.com/AOMediaCodec/libavif/blob/647c3c208cf152395d777c1bf7240d2ecf7df5a9/include/avif/avif.h#L707-L715
For example, the kimageformats test fails if you don't provide libaom since ra1ve and libsvt-av1 provide a different binary output (and don't support lossless).
libaom is the most important since it is necessary for lossless, rav1e and libsvt-av1 are faster and enabling them allow people to use them through libavif.
next prev parent reply other threads:[~2023-02-25 5:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 3:44 [PR PATCH] " oreo639
2023-02-25 3:45 ` [PR PATCH] [Updated] " oreo639
2023-02-25 3:57 ` oreo639
2023-02-25 4:51 ` lemmi
2023-02-25 5:26 ` oreo639
2023-02-25 5:26 ` oreo639
2023-02-25 5:27 ` oreo639
2023-02-25 5:28 ` oreo639 [this message]
2023-02-25 5:30 ` oreo639
2023-02-25 5:30 ` oreo639
2023-02-25 5:34 ` oreo639
2023-02-25 5:34 ` oreo639
2023-02-25 5:36 ` oreo639
2023-02-25 5:46 ` [PR PATCH] [Updated] " oreo639
2023-02-25 6:54 ` lemmi
2023-02-25 7:06 ` oreo639
2023-02-25 7:14 ` oreo639
2023-02-25 7:14 ` oreo639
2023-02-25 7:14 ` oreo639
2023-02-25 7:52 ` oreo639
2023-04-03 2:39 ` [PR PATCH] [Updated] " oreo639
2023-04-03 8:22 ` oreo639
2023-04-03 8:24 ` oreo639
2023-04-06 5:22 ` [PR PATCH] [Merged]: " lemmi
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=20230225052847.mE5l_Y8n7szzoKL5zSZ5rCFfNeba6zav2xYJvw5QL9c@z \
--to=oreo639@users.noreply.github.com \
--cc=ml@inbox.vuxu.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).