From: Thilo Borgmann via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Thilo Borgmann <thilo.borgmann@mail.de>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] fate/video: add DXV3 HQ tests
Date: Tue, 30 Jan 2024 22:08:57 +0100
Message-ID: <c9cba6a3-de92-4db9-90bb-485d404b2ade@mail.de> (raw)
In-Reply-To: <CAN7ZixzZRO+8vgeFYvqrkkX4mEL64ZuN0knaAA5hAFpB7eVBRQ@mail.gmail.com>
Am 30.01.24 um 21:53 schrieb Connor Worley:
> In that case, it is probably worth replacing the existing "normal quality"
> samples as they're even larger.
> dxv3-nqwa.mov does not adequately exercise the code fixed in
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/20240130062626.98273-1-connorbworley@gmail.com/
> I'm not sure what the process for removing samples from fate-suite is.
>
The new ones are around 75K, not too big IMO.
Can the new samples cover the same use-cases like the old ones as well?
If we don't loose the old coverage, I can delete the unnecessary ones.
-Thilo
_______________________________________________
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:[~2024-01-30 21:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 19:45 [FFmpeg-devel] [PATCH 1/2] fate/video: add DXV3 DXT1 encoding test Connor Worley
2024-01-24 19:45 ` [FFmpeg-devel] [PATCH 2/2] fate/video: add DXV3 HQ tests Connor Worley
2024-01-28 21:31 ` Connor Worley
2024-01-29 9:23 ` Vittorio Giovara
2024-01-29 9:58 ` Andreas Rheinhardt
2024-01-29 18:37 ` Connor Worley
2024-01-30 19:18 ` Connor Worley
2024-01-30 19:31 ` Andreas Rheinhardt
2024-01-30 20:53 ` Connor Worley
2024-01-30 21:08 ` Thilo Borgmann via ffmpeg-devel [this message]
2024-01-30 21:14 ` Connor Worley
2024-01-30 21:25 ` Andreas Rheinhardt
2024-01-30 21:57 ` Connor Worley
2024-02-01 10:58 ` Thilo Borgmann via ffmpeg-devel
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=c9cba6a3-de92-4db9-90bb-485d404b2ade@mail.de \
--to=ffmpeg-devel@ffmpeg.org \
--cc=thilo.borgmann@mail.de \
/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