From: Stefano Sabatini <stefasab@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Marth64 <marth64@proxyid.net>
Subject: Re: [FFmpeg-devel] [PATCH v4] doc/filters: add idet example
Date: Sun, 7 Jan 2024 15:39:38 +0100
Message-ID: <ZZq3qlINR0kECirR@mariano> (raw)
In-Reply-To: <20240106221838.1573736-1-marth64@proxyid.net>
On date Saturday 2024-01-06 16:18:39 -0600, Marth64 wrote:
> Thanks all, this should be much better now.
>
> Signed-off-by: Marth64 <marth64@proxyid.net>
> ---
> doc/filters.texi | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/doc/filters.texi b/doc/filters.texi
> index 09fa3264ea..20c91bab3a 100644
> --- a/doc/filters.texi
> +++ b/doc/filters.texi
> @@ -15968,6 +15968,15 @@ further computations. This allows inserting the idet filter as a low computation
> method to clean up the interlaced flag
> @end table
>
> +@subsection Examples
> +
> +Inspect the field order of the first 360 frames in a video, in verbose detail:
> +@example
> +ffmpeg -i INPUT -filter:v idet,metadata=mode=print -frames:v 360 -an -f null -
> +@end example
> +The idet filter will add analysis metadata to each frame, which will then be
> +discarded. At the end, the filter will also print a final report with statistics.
> +
Thanks, will apply.
_______________________________________________
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".
prev parent reply other threads:[~2024-01-07 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 19:53 [FFmpeg-devel] [PATCH] doc/filters: add example for idet filter Marth64
2023-12-12 0:18 ` Michael Niedermayer
2023-12-12 0:19 ` Michael Niedermayer
2024-01-06 22:18 ` [FFmpeg-devel] [PATCH v4] doc/filters: add idet example Marth64
2024-01-06 22:20 ` Marth64
2024-01-07 14:39 ` Stefano Sabatini [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=ZZq3qlINR0kECirR@mariano \
--to=stefasab@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=marth64@proxyid.net \
/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