Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/2] doc/filters:ddagrab: elaborate on the semantics of framerate
Date: Wed, 22 Nov 2023 09:32:47 +0530
Message-ID: <aed820bb-bd88-4c5d-8700-94fa63dff57f@gyani.pro> (raw)
In-Reply-To: <20231119114917.1277-1-anton@khirnov.net>



On 2023-11-19 05:19 pm, Anton Khirnov wrote:
> ---
>   doc/filters.texi | 7 ++++++-
>   1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/doc/filters.texi b/doc/filters.texi
> index 38615e4f18..bd4e4ca8f7 100644
> --- a/doc/filters.texi
> +++ b/doc/filters.texi
> @@ -28163,7 +28163,12 @@ Only affects hardware cursors. If a game or application renders its own cursor,
>   it'll always be captured.
>   
>   @item framerate
> -Framerate at which the desktop will be captured.
> +Maximum framerate at which the desktop will be captured - the interval between
> +successive frames will not be smaller than the inverse of the framerate. When
> +the desktop is not being updated often enough, the filter will duplicate
> +a previous frame. Note that there is no background buffering going on, so when
> +the filter is not polled often enough then the actual inter-frame interval may
> +be significantly larger.
>   
>   Defaults to 30 FPS.
>   

LGTM.

Regards,
Gyan

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

      parent reply	other threads:[~2023-11-22  4:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-19 11:49 Anton Khirnov
2023-11-19 11:49 ` [FFmpeg-devel] [PATCH 2/2] lavfi/vsrc_ddagrab: add an option to avoid duplicating frames Anton Khirnov
2023-11-22  4:02 ` Gyan Doshi [this message]

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=aed820bb-bd88-4c5d-8700-94fa63dff57f@gyani.pro \
    --to=ffmpeg@gyani.pro \
    --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