Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] fftools/ffmpeg: Added ability to set a input burst time before readrate is enforced
Date: Fri, 28 Apr 2023 10:01:25 +0200
Message-ID: <168266888545.3843.830158000112531029@lain.khirnov.net> (raw)
In-Reply-To: <98e50dd9-c85e-3f18-654c-228ea6cb8113@davyandbeth.com>

Your email client mangled the patch, so it cannot be applied as is.

Quoting Davy Durham (2023-04-07 09:57:54)
> Implemented is the -irb <seconds> flag (i.e. "initial read burst") that
> causes ffmpeg to read the specified number of seconds of input before a
> given readrate starts to be enforced.  All inputs have to reach this
> point before the readrate is enforced.  The reason for this change is,
> in the scenario of live-streaming by transcoding from an pre-recorded or
> delayed source to an HLS or DASH webroot, we can more quickly prime the
> system of the first few seconds before the real-world read rate is
> imposed.  Else, one must wait for an entire segment length before the
> data can be fetched from the web server.
> 
> Signed-off-by: Davy Durham <ddurham@users.sourceforge.net>
> ---
>   doc/ffmpeg.texi        |  2 ++
>   fftools/ffmpeg.h       |  2 ++
>   fftools/ffmpeg_demux.c | 13 ++++++++++++-
>   fftools/ffmpeg_opt.c   |  3 +++
>   4 files changed, 19 insertions(+), 1 deletion(-)
> 
> diff --git a/doc/ffmpeg.texi b/doc/ffmpeg.texi
> index d433d60ce9..a519fea192 100644
> --- a/doc/ffmpeg.texi
> +++ b/doc/ffmpeg.texi
> @@ -1709,6 +1709,8 @@ it may cause packet loss.
>   It is useful for when flow speed of output packets is important, such 
> as live streaming.
>   @item -re (@emph{input})
>   Read input at native frame rate. This is equivalent to setting 
> @code{-readrate 1}.
> +@item -irb @var{seconds}

I think 'irb' is too short for an option that modifies behavior of
another, rather obscure, option. How about -readrate_burst or
-readrate_delay or something along these lines?

> @@ -1159,6 +1160,16 @@ int ifile_open(const OptionsContext *o, const 
> char *filename)
>           f->rate_emu = 0;
>       }
>   +    f->initial_read_burst = o->initial_read_burst ? 
> o->initial_read_burst : 0.0;
> +    if (f->initial_read_burst < 0.0) {
> +        av_log(NULL, AV_LOG_ERROR, "Option -irb for Input #%d is %0.3f; 

Use f as the log context, then you can drop the input file number in the
string itself.

Same below.

Otherwise seems reasonable.

-- 
Anton Khirnov
_______________________________________________
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-28  8:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07  7:57 Davy Durham
2023-04-28  8:01 ` Anton Khirnov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-07  7:50 Davy Durham
2023-04-07  7:54 ` Davy Durham
2023-02-23  8:05 Davy Durham
2023-03-17  6:50 ` Davy Durham

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=168266888545.3843.830158000112531029@lain.khirnov.net \
    --to=anton@khirnov.net \
    --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