TopGit
GitHub Repo Review

PySceneDetect: README promises vs user reports

Breakthrough/PySceneDetect
PTopGit review image for Breakthrough/PySceneDetect
Review by Topgit.dev for Breakthrough/PySceneDetect, with GitHub repository stats and README context.
Quick verdict

Stars
β˜… 5.3k
Forks
β‘‚ 555
Contributors
πŸ‘₯ 43
Language
Python
License
BSD-3-Clause
Topic
Image Tools
Updated
Nov 2026
Homepage

The PySceneDetect README promises that a single command, scenedetect -i video.mp4 split-video, will cut a video on every fast cut, that AdaptiveDetector copes better with fast camera movement, and that a benchmark page measures accuracy and speed. User reports mostly show where those promises ran into trouble.

Start with the commands. In an issue dated 2019-02-09, @typoman wrote that "the precise flag (-p or --precise) has been changed to preset and does not work anymore although it's still written in the readme of the repo". The issue is closed, but the bundle does not say what changed.

Cut quality is the next promise. @ghost reported on 2020-04-15 that cuts were often off, with scenes starting or ending inside the previous or next scene, using the plain detect-content split-video combination on different sources. On speed, @tonycpsu opened an issue on 2016-01-16, still open, saying "it's much slower than other scene detection tools I've experimented with". That report is old, and the bundle holds no newer user timing to compare against the benchmark page.

Camera flashes are a gap in the README text provided here. @annishaa88 asked on 2017-06-13 what to do about videos with flashes, which produced only three timestamps for their clip. That issue is open as well. Separately, @joshuabolick asked on 2025-11-18 for help choosing detectors and settings for old VHS footage, while the README only mentions three detectors in a couple of sentences.

The only post from this month is @victor_explore on X, 2026-11-14, who advises cutting on whisperx word timestamps and using pyscenedetect only to nudge off a mid-shot cut. The post had no likes, so it is one person's workflow. The Hacker News mentions in the bundle are link drops or posts by the author, so none of them is cited.

The project itself is alive: last push 2026-11-13, BSD-3-Clause, first created 2014-06-04. On a repo with 5471 stars and 571 forks, 63 issues are open, two of them reports quoted above (#7 and #35).

Left unanswered by the README text supplied: how the tool behaves on flashes, on degraded footage, and how far the benchmark numbers match what these users saw.

View on GitHub β†—

Related repositories

Want a second opinion on PySceneDetect?

Ask an AI that can read this page β€” one click and you get its take on PySceneDetect.

GitHub