From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Andreas Schneider <asn@cryptomilk.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/openh264: return (DE|EN)CODER_NOT_FOUND if version check fails
Date: Wed, 20 Apr 2022 15:07:04 +0300 (EEST)
Message-ID: <919e3498-f841-e879-580-18237036e056@martin.st> (raw)
In-Reply-To: <20220218125319.243373-1-asn@cryptomilk.org>
On Fri, 18 Feb 2022, Andreas Schneider wrote:
> Signed-off-by: Andreas Schneider <asn@cryptomilk.org>
> ---
> libavcodec/libopenh264dec.c | 2 +-
> libavcodec/libopenh264enc.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libavcodec/libopenh264dec.c b/libavcodec/libopenh264dec.c
> index 7f5e85402a..97d3630df6 100644
> --- a/libavcodec/libopenh264dec.c
> +++ b/libavcodec/libopenh264dec.c
> @@ -56,7 +56,7 @@ static av_cold int svc_decode_init(AVCodecContext *avctx)
> WelsTraceCallback callback_function;
>
> if ((err = ff_libopenh264_check_version(avctx)) < 0)
> - return err;
> + return AVERROR_DECODER_NOT_FOUND;
>
> if (WelsCreateDecoder(&s->decoder)) {
> av_log(avctx, AV_LOG_ERROR, "Unable to create decoder\n");
> diff --git a/libavcodec/libopenh264enc.c b/libavcodec/libopenh264enc.c
> index 7c0501a2eb..7649e7b025 100644
> --- a/libavcodec/libopenh264enc.c
> +++ b/libavcodec/libopenh264enc.c
> @@ -137,7 +137,7 @@ static av_cold int svc_encode_init(AVCodecContext *avctx)
> AVCPBProperties *props;
>
> if ((err = ff_libopenh264_check_version(avctx)) < 0)
> - return err;
> + return AVERROR_ENCODER_NOT_FOUND;
>
> if (WelsCreateSVCEncoder(&s->encoder)) {
> av_log(avctx, AV_LOG_ERROR, "Unable to create encoder\n");
> --
> 2.35.1
This looks reasonable to me, so I could push this in a little while if
there's no more comments on it.
But the patch lacks an explanation of _why_ this is done, in addition to
_what_ it does. I presume that's because the current error code makes some
decoder/encoder selection logic error out entirely, instead of continuing
trying some other codec - is that right? That would really be valuable to
include in the commit message.
// 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".
next prev parent reply other threads:[~2022-04-20 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 12:53 Andreas Schneider
2022-04-12 10:50 ` Neal Gompa
2022-04-20 12:07 ` Martin Storsjö [this message]
2022-04-27 8:51 ` Martin Storsjö
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=919e3498-f841-e879-580-18237036e056@martin.st \
--to=martin@martin.st \
--cc=asn@cryptomilk.org \
--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