From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v3] avcodec/av1dec: export pixel format even if no hardware decoder is present
Date: Fri, 8 Sep 2023 09:27:54 -0300
Message-ID: <16a15277-c975-8d1e-1f87-4f35ba6f5e34@gmail.com> (raw)
In-Reply-To: <20230908004905.8813-1-jamrial@gmail.com>
On 9/7/2023 9:49 PM, James Almer wrote:
> And remove the AVOID_PROBING flag, given it's the last av1 decoder to be tested
> either way.
> This fixes a regression introduced in 1652f2492f88434010053289d946dab6a57e4d58,
> where even if forcing the native av1 decoder, if another decoder was present,
> like libdav1d or libaom-av1, they'd be used for probing and some fate tests
> would have different results.
>
> Signed-off-by: James Almer <jamrial@gmail.com>
> ---
> libavcodec/av1dec.c | 41 ++++++++++++++++++++-------------
> tests/fate-run.sh | 11 +++++----
> tests/fate/flvenc.mak | 4 ++--
> tests/fate/lavf-container.mak | 8 +++----
> tests/fate/mpegps.mak | 2 +-
> tests/ref/fate/av1-annexb-demux | 2 +-
> tests/ref/lavf-fate/av1.mkv | 4 ++--
> tests/ref/lavf-fate/av1.mp4 | 4 ++--
> 8 files changed, 43 insertions(+), 33 deletions(-)
Will apply.
_______________________________________________
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:[~2023-09-08 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 2:06 [FFmpeg-devel] [PATCH] " James Almer
2023-09-07 8:06 ` Andreas Rheinhardt
2023-09-07 14:30 ` James Almer
2023-09-07 17:55 ` [FFmpeg-devel] [PATCH v2] " James Almer
2023-09-07 23:41 ` Michael Niedermayer
2023-09-08 0:49 ` [FFmpeg-devel] [PATCH v3] " James Almer
2023-09-08 12:27 ` James Almer [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=16a15277-c975-8d1e-1f87-4f35ba6f5e34@gmail.com \
--to=jamrial@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