From: Paul B Mahol <onemda@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [freezedetect filter] discard frozen frames option ever added? Date: Sun, 1 Oct 2023 14:12:51 +0200 Message-ID: <CAPYw7P5N1cMRtFkkS=F6MwH1VxV_kE+1paV++4gk7_H7DG7-DQ@mail.gmail.com> (raw) In-Reply-To: <CA+BiOC+TCpHNrvqHM9z+oRRtLc3RpNaTng0+YOKho-dVK51bdA@mail.gmail.com> 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".
next prev parent reply other threads:[~2023-10-01 12:13 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-01 2:20 Umberto Boccioni 2023-10-01 12:12 ` Paul B Mahol [this message] 2023-10-02 4:15 Umberto Boccioni 2023-10-02 6:06 ` 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='CAPYw7P5N1cMRtFkkS=F6MwH1VxV_kE+1paV++4gk7_H7DG7-DQ@mail.gmail.com' \ --to=onemda@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