Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] avformat/img2enc: use unmatched filename for an invalid or missing sequence pattern
Date: Mon, 20 Jun 2022 23:31:36 +0200 (CEST)
Message-ID: <435abbbb-6fbc-a2d1-8adb-aa4a5fe9dbfb@passwd.hu> (raw)
In-Reply-To: <20220612224449.23333-2-cus@passwd.hu>



On Mon, 13 Jun 2022, Marton Balint wrote:

> Also warn the user that for single images -update should be used, for sequences
> a proper pattern should be specified.
>
> Fixes ticket #9748.

Ping for this. Note that this patch will show a warning for any 
non-sequence image filename (unless the -update option is specified) 
in order to help the user avoid unexpected results with filenames 
containing %d.

Regards,
Marton

>
> Signed-off-by: Marton Balint <cus@passwd.hu>
> ---
> libavformat/img2enc.c | 18 +++++++++++-------
> 1 file changed, 11 insertions(+), 7 deletions(-)
>
> diff --git a/libavformat/img2enc.c b/libavformat/img2enc.c
> index 82a04e639b..50e469dd96 100644
> --- a/libavformat/img2enc.c
> +++ b/libavformat/img2enc.c
> @@ -163,13 +163,17 @@ static int write_packet(AVFormatContext *s, AVPacket *pkt)
>         }
>     } else if (av_get_frame_filename2(filename, sizeof(filename), s->url,
>                                       img->img_number,
> -                                      AV_FRAME_FILENAME_FLAGS_MULTIPLE) < 0 &&
> -               img->img_number > img->start_img_number) {
> -        av_log(s, AV_LOG_ERROR,
> -               "Could not get frame filename number %d from pattern '%s'. "
> -               "Use '-frames:v 1' for a single image, or '-update' option, or use a pattern such as %%03d within the filename.\n",
> -               img->img_number, s->url);
> -        return AVERROR(EINVAL);
> +                                      AV_FRAME_FILENAME_FLAGS_MULTIPLE) < 0) {
> +        if (img->img_number == img->start_img_number) {
> +            av_log(s, AV_LOG_WARNING, "The specified filename '%s' does not contain an image sequence pattern or a pattern is invalid.\n", s->url);
> +            av_log(s, AV_LOG_WARNING,
> +                   "Use a pattern such as %%03d for an image sequence or "
> +                   "use the -update option (with -frames:v 1 if needed) to write a single image.\n");
> +            av_strlcpy(filename, s->url, sizeof(filename));
> +        } else {
> +            av_log(s, AV_LOG_ERROR, "Cannot write more than one file with the same name. Are you missing the -update option or a sequence pattern?\n");
> +            return AVERROR(EINVAL);
> +        }
>     }
>     for (i = 0; i < 4; i++) {
>         av_dict_copy(&options, img->protocol_opts, 0);
> -- 
> 2.34.1
>
> _______________________________________________
> 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".
>
_______________________________________________
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:[~2022-06-20 21:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-12 22:44 [FFmpeg-devel] [PATCH 1/2] avformat/img2enc: fix first image check Marton Balint
2022-06-12 22:44 ` [FFmpeg-devel] [PATCH 2/2] avformat/img2enc: use unmatched filename for an invalid or missing sequence pattern Marton Balint
2022-06-20 21:31   ` Marton Balint [this message]
2022-07-07 18:32     ` Marton Balint

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=435abbbb-6fbc-a2d1-8adb-aa4a5fe9dbfb@passwd.hu \
    --to=cus@passwd.hu \
    --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