ffmpeg-static vs PySceneDetect
Both in the video & clipping category. Side-by-side — pick the one that fits your stack tonight.
Bundled ffmpeg that just works — no 'your version is missing libfoo' errors.
- rating
- 4★
- tested
- ✓ loya-tested
- cost
- free
- install
- drop-in
- stars
- 1,350
- updated
- 5w ago
You only need basic trim/extract operations — system ffmpeg is fine for those.
Finds every camera cut in your video automatically. Powers smart cropping + transitions.
- rating
- 4★
- tested
- ✓ loya-tested
- cost
- free
- install
- sidecar
- stars
- 4,736
- updated
- 4d ago
You only work with single-camera talking-head footage — scene detection isn't useful there.
why it matters · ffmpeg-static
If you've tried to use ffmpeg in a Node project, you've probably hit the 'no such filter: subtitles' or 'no such filter: drawtext' error — because whichever ffmpeg your machine has was compiled without the library you need. ffmpeg-static is an npm package that ships a full ffmpeg binary with everything common pre-enabled (libass, libfreetype, the full encoder set). Drop it in, point your spawn calls at it, stop fighting the system ffmpeg. Works on Mac/Linux/Windows. 50MB dep, scoped per-project.
why it matters · PySceneDetect
PySceneDetect scans any video and spits out the timestamp of every hard cut — the moment the camera switches. For multi-cam podcasts, that's the boundary you need so your 9:16 crop follows the active speaker without drifting on stale frames. Used in podcast-clipper crop pipelines alongside face tracking — same library Loya's LYRC export pipeline relies on for scene work. Free, Python, actively maintained (commits this week).