vidcutter
A modern yet simple multi-platform video cutter and joiner.
Runssource: GitHubPythonGPL-3.0commit db6818f11bbb
Python, GPL-3.0 licensed. The project labels itself: appimage, arch linux, cross platform, cython, ffmpeg, linux, macos and mpv.
vidcutter runs. An Argusic agent installed it in 12 minutes and hit 12 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
VidCutter 6.0.5.2 GUI launches under offscreen Qt platform, connects to real libmpv 0.37.0 with FFmpeg 6.1.1, shows version and help output, and logs runtime configuration from the playback engine.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- setup.py build_ext: fatal error: Python.h: No such file or directory2 minutes
- pip install failed: externally-managed-environment1 minute
- setup.py build_ext: fatal error: x86_64-linux-gnu/python3.12/pyconfig.h1 minute
- runtime: ImportError: libdvdnav.so.4: cannot open shared object file1 minute
- setup.py build_ext: ModuleNotFoundError: No module named 'setuptools'0.5 minutes
- setup.py build_ext: fatal error: mpv/client.h: No such file or directory0.5 minutes
- Install time
- 12 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 12 hit, 12 fixed with no human help
- How the result was proved
- QT_QPA_PLATFORM=offscreen LD_LIBRARY_PATH=/work/repo/venv/lib64 /work/repo/venv/bin/python -m vidcutter --debug ran for 5 seconds, logged mpv 0.37.0, libplacebo v6.338.2, FFmpeg 6.1.1, exited cleanly; --version returned 'VidCutter 6.0.5.2'
- Model tokens used
- 87,451
- Exact commit tested
- db6818f11bbb
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `pip install` blocked by externally-managed environment → created venv - `No module named 'setuptools'` → installed setuptools - `Python.h` / `pyconfig.h` / platform-include headers missing → extracted `libpython3.12-dev` deb … - `mpv/client.h: No such file or directory` → added `vidcutter/libs/pympv/include` to compiler incl… - Missing shared libraries at runtime: `libdvdnav.so.4`, `libmujs.so.3`, `liblua5.2.so.0`, `libsixe… **No test suite** exists in this project — no test directory, pytest config, or unittest files were exec /bin/sh -lc "cat << 'EOF' EOF" in /work/repo succeeded in 0ms: tokens used 87,451
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 12 minutes.
- Recovered from all 12 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed GPL-3.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
appimagearch-linuxcross-platformcythonffmpeglinuxmacosmpvopenglpyqt5python3qt5-guiubuntuvideo-editorwindows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/vidcutter)Questions
- Does vidcutter run?
- Yes. vidcutter runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 12 errors on the way, and recorded the session.
- How did Argusic test vidcutter?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit db6818f11bbb. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test vidcutter?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does vidcutter take to install?
- 12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does vidcutter need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing vidcutter?
- 12 things broke in the recorded run, and 12 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for vidcutter?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.