[FFmpeg-user] Efficiently doing thousands of edits?
bouke at editb.nl
Thu Apr 11 13:01:28 EEST 2019
> On 11 Apr 2019, at 04:44, John Hawkinson <jhawk at alum.mit.edu> wrote:
> Michael Shaffer <mikeshaffer at gmail.com> wrote on Wed, 10 Apr 2019
> at 19:40:36 -0400 in <CAMrzi1s55GuHbXoWW+r6XibbDKdtsHa=x04vf5DO4fhUqUh4Jg at mail.gmail.com>:
>> I'm pretty sure you could use Python and OpenCV to create a solution..
> "Just because you can, doesn't mean you should."
> My original post explained how to determine where the runs of black are, using ffmpeg (libavfilter)'s "blackdetect." The only piece left is applying the edits in a practical fashion.
> Rolling your own with opencv would be a whole lot more work. I'm not entirely sure that I agree with Carl Eugen that ffmpeg isn't a video editing tool, but if it's not, Python certainly isn't. Yes, you can make it work. But you're going to spend a lot more time doing it than if higher level tools were used.
> The goal here is for higher-level tools, not lower-level ones.
> Or I might just end up using ffmpeg to split it into 7,000 files and then concatenating them. That's hardly the worst thing in the world.
Why split and cat? You are not doing editing, you want to mask (little) pieces, not shorten / extend / reshuffle, right?
If you have all the in/out point, why not do a (png or alike) overlay on those points?
Or, a subtitle overlay with a strange custom font (one big black rectangle char).
> jhawk at alum.mit.edu
> John Hawkinson
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
More information about the ffmpeg-user