[FFmpeg-devel] [freezedetect filter] discard frozen frames option ever added?

[FFmpeg-devel] [freezedetect filter] discard frozen frames option ever added?

[Umberto Boccioni]

[Apologies for the cross-post from User list, but in retrospect, I thought
the post was better placed here]

I'm trying to remove frozen frames from a video with gaps in the input
stream, and the freezedetect filter appears to accurately find/list those
sections.

I was hoping to use the results of freezedetect to trim those sections of
video, and there was a freezedetect "discard" ("f") option in the dev
builds a few years back which appears to do exactly that (
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20191008035428.19474-1-lance.lmwang@gmail.com/#46233
)

It doesn't seem to have made its way into any of the builds (including dev
branches) as far as I can find, and it's definitely not in the official
docs.

To my untrained eye, the patch looks complete, though possibly abandoned.
is there any chance of it being incorporated into the mainline source?  It
would be quite useful.

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

Re: [FFmpeg-devel] [freezedetect filter] discard frozen frames option ever added?

[Paul B Mahol]

On 10/1/23, Umberto Boccioni <vexware@gmail.com> wrote:
> [Apologies for the cross-post from User list, but in retrospect, I thought
> the post was better placed here]
>
> I'm trying to remove frozen frames from a video with gaps in the input
> stream, and the freezedetect filter appears to accurately find/list those
> sections.
>
> I was hoping to use the results of freezedetect to trim those sections of
> video, and there was a freezedetect "discard" ("f") option in the dev
> builds a few years back which appears to do exactly that (
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/20191008035428.19474-1-lance.lmwang@gmail.com/#46233
> )
>
> It doesn't seem to have made its way into any of the builds (including dev
> branches) as far as I can find, and it's definitely not in the official
> docs.
>
> To my untrained eye, the patch looks complete, though possibly abandoned.
> is there any chance of it being incorporated into the mainline source?  It
> would be quite useful.

That patch is incorrect and buggy.

The solution is written bellow that patch in discussion once you real all text:

freezedetect,metadata=mode=select:key=lavfi.freezedetect.freeze_amount:value=some_frozen_amount:function=greater

No point in using that patch as functionality is already available:

https://ffmpeg.org/ffmpeg-filters.html#toc-metadata_002c-ametadata


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

Re: [FFmpeg-devel] [freezedetect filter] discard frozen frames option ever added?

[Umberto Boccioni]

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

Re: [FFmpeg-devel] [freezedetect filter] discard frozen frames option ever added?

[Paul B Mahol]

On 10/2/23, Umberto Boccioni <vexware@gmail.com> wrote:
>>
>> 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.
>

Everything is written in examples in documentation.
Even written full example here.

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