FFmpeg is powerful technology, yet approaching it can be very daunting. So we decided to create an approachable guide for intermediate devs.
Feedback is very much appreciated.
Shameless plug: a while ago I wrote a simple Python script to remove silent parts from video using ffmpeg, which AFAIK it doesn't do out of the box:
https://github.com/bambax/Remsi
It might be helpful to others.
As soon as that worked I wanted more - mostly just really wanted the process to be interactive and real-time, instead of the run-check-tweak-repeat cycle of using a script.
So I ended up down the rabbit hole of building a video editor instead of making screencasts, and now Recut exists (https://getrecut.com).
It’s basically an interactive silence remover. I still haven’t finished those screencasts but now I have an editor haha. While it’s pretty basic, it’s saving folks a bunch of time, and there’s lots more cool stuff I want to add between automations and basic manual editing features.
Your're a hacker role model.
I mostly interpret this as ‘see me see me - I’m good!’ in stead of ‘let me try to educate you about this subject’.
All the natural pauses between sentences gives a much better and natural flow.
This also includes ‘oups I made a mistake .. and fixed it like this…’
Just like the line breaks in this comment serves a purpose;-)
One great example of a really good tutorial is Eivind Fonn’s Spacemacs ABC videos: https://youtu.be/2y9NLIbNf_I
Here’s my worst example of how not to teach: https://youtu.be/qtIqKaDlqXo
This series is also bad as there is way too much zoom in and out (which distract all but the presenter!)
A bunch of non-breaking quick cuts is of course jarring and could be better, but what you describe with "mistakes and all" is too far down the other end in my mind. I would not want to sit through someone having to backpedal like that.
But to each their own, we all learn differently.
It's for videos you make yourself, to remove silent parts automatically. In interviews for example, it's useful to simply remove silences.
Someone should do a gui for common tasks it can do line there used to be the Zenmap gui for nmap.
(Learning how to do those sorts of simple guis quickly in python of something is another holiday todo, if anyone has suggestions on that - all my tools thus far are gui based and I need to make sure as many folks as possible use them.)
Here's the script I cobbled together from various internet searches for the video-to-gif one, it works well enough for that purpose and all you have to do is remove the video-to-PNG bits at the start.:
https://gist.github.com/JobLeonard/5f99b712ba77b7aa82696c136...
The goal is gonna be to have something where I can give it units of time as arguments and do clips. So for example, you could give it a dot mkv and say from 30 seconds in to 300 seconds in, take that into stills then create a GIF... or an aPNG but... I'll take a look, play around, I need to learn to read undocumented code better this will be a good exercise since it's not some possibly zero day malware that didn't get past noscript like the last time I did that...
(But to swing it back to graphics: there a reason people don't use apng more? The reason I got ages ago is PNG is more for line drawings, not raster images like what you'd normally use a JPEG format for, but it's my understanding you can play with settings and get a similar level of compression without the patent encumberment of things like GIF with aPNG, and that it's supported by pretty much every browser except for... [checks wikipedia] Internet Explorer[1]?)
Anyways TL;DR: sorry to wall of text you, I'm pounding caffeine and reading the news and jumping between several projects at once -- thanks for the code, I'm going to take a look later -- right now gotta switch locations in ~10 minutes like I'm a Tor circuit ;-)
"HandBrake uses FFmpeg under the hood and generally can open whatever FFmpeg will, in addition to disc-based formats like DVD and Blu-ray." Via
https://handbrake.fr/docs/en/1.3.0/technical/source-formats....
> Feedback is very much appreciated.
Nothing about captions that I could find quickly, which seems like an oversight.
To get rid of the cookie consent in this case,
curl https://img.ly/blog/ultimate-guide-to-ffmpeg/|sed 's/<div class=\"cke-overlay\">/<!--&/;s/<main class=\"main u-relative \">/-->&/' > 1.htm
firefox ./1.htm
links https://img.ly/blog/ultimate-guide-to-ffmpeg/amp/
It may also be possible to remove a <div>-based cookie consent using a browser Add-On like uBlock Origin.
If it were up to me, cookie consents would be done via HTTP headers. The user could simply set their client to send an HTTP header indicating no consent. Something like
Cookie-consent: False
proof: they've had plenty of time, and even browsers that claim to be public services can't even keep the APIs stable for cookie/storage control.
(MOV in fact does support this, but ffmpeg doesn't play it back properly.)
Can't repro here.
Commands:
ffmpeg -ss X -i INPUT -c copy -t 10 test.mp4
ffplay test.mp4
As far as feedback goes, I noticed when running through the guide that the following command is missing an -i flag: ffplay -vf "drawtext=text='HELLO THERE':y=h-text_h-10:x=(w/2-text_w/2):fontsize=200:f
I've already learned a lot from the ffmpeg concepts section. Appreciate it.