Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 4/4] fftools/ffmpeg: deprecate -re
Date: Tue, 2 May 2023 17:36:30 +0200
Message-ID: <7dbd4844-61f8-716d-0eaa-316f5d708483@rothenpieler.org> (raw)
In-Reply-To: <20230502134316.10496-4-anton@khirnov.net>

On 02.05.2023 15:43, Anton Khirnov wrote:
> It is exactly equivalent to -readrate 1.0
> ---
>   Changelog              | 1 +
>   doc/ffmpeg.texi        | 2 +-
>   fftools/ffmpeg.h       | 3 +++
>   fftools/ffmpeg_demux.c | 5 +++++
>   fftools/ffmpeg_opt.c   | 4 +++-
>   5 files changed, 13 insertions(+), 2 deletions(-)
> 
> diff --git a/Changelog b/Changelog
> index 2061aaf462..5feb4fd24e 100644
> --- a/Changelog
> +++ b/Changelog
> @@ -8,6 +8,7 @@ version <next>:
>   - afireqsrc audio source filter
>   - arls filter
>   - ffmpeg CLI new option: -readrate_initial_burst
> +- ffmpeg CLI option -re deprecated in favor of -readrate 1.0


Not sure if deprecating that option is a good idea.
It's in A LOT of guides, and in a lot of peoples scripts.

I see no harm in keeping it around as a shorthand for a common use of 
-readrate.
_______________________________________________
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-05-02 15:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02 13:43 [FFmpeg-devel] [PATCH 1/4] fftools/ffmpeg: add ability to set a input burst time before readrate is enforced Anton Khirnov
2023-05-02 13:43 ` [FFmpeg-devel] [PATCH 2/4] fftools/ffmpeg: use a non-zero default for -readrate_initial_burst Anton Khirnov
2023-05-02 13:43 ` [FFmpeg-devel] [PATCH 3/4] fftools/ffmpeg: reduce -re to -readrate 1 Anton Khirnov
2023-05-02 13:43 ` [FFmpeg-devel] [PATCH 4/4] fftools/ffmpeg: deprecate -re Anton Khirnov
2023-05-02 15:36   ` Timo Rothenpieler [this message]
2023-05-02 15:40     ` Devin Heitmueller

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=7dbd4844-61f8-716d-0eaa-316f5d708483@rothenpieler.org \
    --to=timo@rothenpieler.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