Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: LinAdmin <linadmin@quickline.ch>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] Suggestion of append alternative when partial result file already exists
Date: Wed, 16 Feb 2022 11:17:02 +0100
Message-ID: <c718e586-56a0-9728-ec4f-e05fda4cb4e8@quickline.ch> (raw)

Unless you have a very powerful machine, encoding a 2 hour 
film may take 40 hours. It must run continuously and in case 
you are forced to interrupt the process, it becomes 
difficult to append to the work already done.

When you start encoding using something like
    ffmpeg -i input.mp4 -map 0:0 -map 0:1 -c:v libx265 -c:a 
copy output.mp4
and reuse that same command when part of output.mp4 is 
already present, ffmpeg asks the question
"output.mp4 already present, overwrite y/n".

It would be helpful if the question could be improved to:

"output.mp4 already present, append or overwrite a/o".

It is evident that appending would only success if creation 
of the existing partial file was stopped in a 'normal' way, 
e.g. by pressing CtrlC for the encoding process.

I am convinced that many users of ffmpeg would be very happy 
about this possibility.
Many thanks for your good work with ffmpeg!

LinAdmin


_______________________________________________
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-02-16 10:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=c718e586-56a0-9728-ec4f-e05fda4cb4e8@quickline.ch \
    --to=linadmin@quickline.ch \
    --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