From: Leo Izen <leo.izen@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] doc/encoders: document libjxl encoder options
Date: Wed, 27 Apr 2022 08:28:30 -0400
Message-ID: <52349af0-efb6-e5ed-9e20-ad4c03faa2f0@gmail.com> (raw)
In-Reply-To: <a2f6ed6a-b410-2d66-3bbc-ce08b0a04980@gyani.pro>
On 4/27/22 04:39, Gyan Doshi wrote:
>
>
> On 2022-04-27 02:38 am, Leo Izen wrote:
>>
>> +
>> +@item modular
>> +Force the encoder to use Modular mode. The default is to let the
>> encoder pick
>> +between VarDCT and Modular encoding modes based on encoding settings
>> and the
>> +type of input content.
>
> What happens in these two modes? Why would the user want to force
> modular? Is there a way and reason to force VarDCT?
>
>
VarDCT uses a fourier-DCT-based transform in essence. Modular uses a
variety of transforms that can be combined like Lego bricks into
patches, including a modified Haar transform.
In general, VarDCT will be superior to Modular for lossy encoding, but
VarDCT doesn't support lossless, so Modular is required for lossless
encoding. Currently, the library always chooses VarDCT for lossy and
Modular for lossless, although this could potentially be subject to change.
A user will have very little reason to force modular unless they're
testing the two modes against each other. The library API does not
provide a way to force VarDCT. Or rather, it does, but if you force
VarDCT and tell it to encode losslessly it will silently use modular
rather than fail.
You generally won't have a reason to force VarDCT anyway, since it's
chosen by default if you pick lossy, so this isn't an issue.
Leo Izen (thebombzen)
_______________________________________________
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-04-27 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 21:08 Leo Izen
2022-04-27 8:39 ` Gyan Doshi
2022-04-27 12:28 ` Leo Izen [this message]
2022-04-27 13:31 ` Gyan Doshi
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=52349af0-efb6-e5ed-9e20-ad4c03faa2f0@gmail.com \
--to=leo.izen@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