Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Stefano Sabatini <stefasab@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] lavf/mux: clarify log messages when choosing oformat fails
Date: Sun, 2 Apr 2023 21:08:18 +0200
Message-ID: <20230402190818.GK3542@mariano> (raw)
In-Reply-To: <20230330093809.22687-2-anton@khirnov.net>

On date Thursday 2023-03-30 11:38:08 +0200, Anton Khirnov wrote:
> Current log messages talk about 'suitable' output formats. This is
> confusing, because it suggests that some formats are suitable, while
> others are not, which is not the case.
> 
> Also, suggest possible user actions when format cannot be guessed from a
> filename.
> ---
>  libavformat/mux.c | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/libavformat/mux.c b/libavformat/mux.c
> index 0bc9b6b87d..415bd3948f 100644
> --- a/libavformat/mux.c
> +++ b/libavformat/mux.c
> @@ -102,7 +102,7 @@ int avformat_alloc_output_context2(AVFormatContext **avctx, const AVOutputFormat
>          if (format) {
>              oformat = av_guess_format(format, NULL, NULL);
>              if (!oformat) {
> -                av_log(s, AV_LOG_ERROR, "Requested output format '%s' is not a suitable output format\n", format);
> +                av_log(s, AV_LOG_ERROR, "Requested output format '%s' is not known.\n", format);
>                  ret = AVERROR(EINVAL);
>                  goto error;
>              }
> @@ -110,8 +110,10 @@ int avformat_alloc_output_context2(AVFormatContext **avctx, const AVOutputFormat
>              oformat = av_guess_format(NULL, filename, NULL);
>              if (!oformat) {
>                  ret = AVERROR(EINVAL);
> -                av_log(s, AV_LOG_ERROR, "Unable to find a suitable output format for '%s'\n",
> -                       filename);
> +                av_log(s, AV_LOG_ERROR,
> +                       "Unable to choose an output format for '%s'; "
> +                       "use a standard extension for the filename or specify "
> +                       "the format manually.\n", filename);

LGTM.
_______________________________________________
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".

  reply	other threads:[~2023-04-02 19:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30  9:38 [FFmpeg-devel] [PATCH 1/2] lavf: fall back to a more meaningful log instance name Anton Khirnov
2023-03-30  9:38 ` [FFmpeg-devel] [PATCH 2/2] lavf/mux: clarify log messages when choosing oformat fails Anton Khirnov
2023-04-02 19:08   ` Stefano Sabatini [this message]
2023-04-02 19:06 ` [FFmpeg-devel] [PATCH 1/2] lavf: fall back to a more meaningful log instance name Stefano Sabatini
2023-04-03 10:16   ` Anton Khirnov

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=20230402190818.GK3542@mariano \
    --to=stefasab@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