From: Umberto Boccioni <vexware@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [freezedetect filter] discard frozen frames option ever added?
Date: Sun, 1 Oct 2023 21:15:28 -0700
Message-ID: <CA+BiOCLkGN6E5g1FUP3PrEMp5ooRUee=8ZoW8ky9dBrZiXivMA@mail.gmail.com> (raw)
>
> something like freezedetect,metadata=mode=select:key=lavfi.freezedetect.freeze_amount:value=some_frozen_amount:function=greater
>
> You just need to export frozen value from freezedetect filter for each
> output frame metadata.
>
>
Thanks for taking the time to respond, which I'm sure is another load on
top of your dev duties. For completeness' sake, can you elaborate on the
solution you originally proposed a few years ago? I am hoping to eliminate
all (potentially multiple) frozen segments in one command. Getting from
your description to a functional solution requires a level of
sophistication (not sure how to "export") I haven't yet acquired with
ffmpeg.
As an example, I found a python script which uses ffmpeg's freezedetect
output to accomplish this in one command, but a native solution would be
preferable:
https://gitlab.com/dak425/scripts/-/blob/master/trim_frozen_frames?ref_type=heads
No point in using that patch as functionality is already available:
>
>
Certainly, this is a reasonable position to take and I'm not trying to
convince anyone otherwise. However, if the functionality is achievable
only through a relatively more non-obvious, opaque, or complicated means,
then having an option that condenses and simplifies and makes more visible
that functionality, well, I think that's a reasonable position to take
too. In any case, it's moot without a non-buggy patch.
--
ub
_______________________________________________
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".
next reply other threads:[~2023-10-02 4:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 4:15 Umberto Boccioni [this message]
2023-10-02 6:06 ` Paul B Mahol
-- strict thread matches above, loose matches on Subject: below --
2023-10-01 2:20 Umberto Boccioni
2023-10-01 12:12 ` Paul B Mahol
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='CA+BiOCLkGN6E5g1FUP3PrEMp5ooRUee=8ZoW8ky9dBrZiXivMA@mail.gmail.com' \
--to=vexware@gmail.com \
--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