From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Connor Worley <connorbworley@gmail.com>
Subject: Re: [FFmpeg-devel] [PATCH v2] lavc/dxv: align to 4x4 blocks instead of 16x16
Date: Fri, 9 Feb 2024 21:47:19 +0200 (EET)
Message-ID: <baf46751-2140-1278-ccde-7715b1e118b@martin.st> (raw)
In-Reply-To: <20240209112649.16556-1-connorbworley@gmail.com>
On Fri, 9 Feb 2024, Connor Worley wrote:
> The previous assumption that DXV needs to be aligned to 16x16 was
> erroneous. 4x4 works just as well, and FATE decoder tests pass for all
> texture formats.
>
> On the encoder side, we should reject input that isn't 4x4 aligned,
> like the HAP encoder does, and stop aligning to 16x16. This both solves
> the uninitialized reads causing current FATE tests to fail and produces
> smaller encoded outputs.
>
> With regard to correctness, I've checked the decoding path by encoding a
> real-world sample with git master, and decoding it with
> ffmpeg -i dxt1-master.mov -c:v rawvideo -f framecrc -
> The results are exactly the same between master and this patch.
>
> On the encoding side, I've encoded a real-world sample with both master
> and this patch, and decoded both versions with
> ffmpeg -i dxt1-{master,patch}.mov -c:v rawvideo -f framecrc -
> Under this patch, results for both inputs are exactly the same.
>
> In other words, the extra padding gained by 16x16 alignment over 4x4
> alignment has no impact on decoded video.
>
> Signed-off-by: Connor Worley <connorbworley@gmail.com>
> ---
> libavcodec/dxv.c | 6 +++---
> libavcodec/dxvenc.c | 14 +++++++++++---
> tests/ref/fate/dxv3enc-dxt1 | 2 +-
> 3 files changed, 15 insertions(+), 7 deletions(-)
LGTM, will push soon to get FATE back to green again.
// Martin
_______________________________________________
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".
prev parent reply other threads:[~2024-02-09 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 11:26 Connor Worley
2024-02-09 19:47 ` Martin Storsjö [this message]
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=baf46751-2140-1278-ccde-7715b1e118b@martin.st \
--to=martin@martin.st \
--cc=connorbworley@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