flowblade
Video Editor for Linux
Runssource: GitHubPythonGPL-3.0commit 1ffef10a7916
Python, GPL-3.0 licensed.
flowblade runs. An Argusic agent installed it in 23.1 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Flowblade Movie Editor 2.24 launches and runs its GTK3 GUI with MLT 7.22.0, initializing the player with HD 1080p 30fps profile.
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 96 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.
- Missing Python dependencies (pygobject, pycairo, mlt, numpy, Pillow, usb1) - not installed in container10 minutes
- Introspection typelib chain errors (xlib, Atk, HarfBuzz namespaces not found)3 minutes
- Missing optional MLT plugin dependencies (libexif, Qt5, movit, opencv, frei0r, LADSPA)3 minutes
- MLT plugins not found - system MLT library looked in wrong path2 minutes
- editorlayout.py bug: _panel_positions is None on fresh install2 minutes
- editorwindow.py bug: G'MIC widget access on None1 minute
- Install time
- 23 minutes
- Cold machine to finish
- 30 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- Model tokens used
- 324,767
- Exact commit tested
- 1ffef10a7916
- 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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.
**Install & Launch Summary** - **Flowblade Movie Editor 2.24** successfully launches and runs its GTK3 GUI with **MLT 7.22.0** v… - The application initializes the player with **HD 1080p 30fps** profile and stays up for the full … - Audio warnings (ALSA/PulseAudio/SDL) are expected in a container without audio hardware **Errors Found & Fixed** 1. **Missing Python deps** - PyGObject, pycairo, python-mlt, numpy, Pillow, usb1 not installed → do… 2. **MLT plugin path** - System MLT looked in `/usr/lib/.../mlt-7/` but plugins were in extracted p… 3. **Typelib chain** - Missing xlib, Atk, HarfBuzz typelibs → downloaded `gir1.2-freedesktop`, `gir… 4. **editorlayout.py bug** - `_panel_positions` is `None` on fresh install causing TypeError → patc… 5. **editorwindow.py bug** - G'MIC menu widget access on `None` when G'MIC not installed → guarded … 6. **Optional MLT plugin libs** - Missing libexif, Qt5, movit, etc. → downloaded frei0r-plugins and… **To launch:** `/tmp/flowblade_env.sh python3 /work/repo/flowblade-trunk/flowblade`
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.
- Recovered from all 6 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 did not, or is not known
- Took 23.1 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
Of the 4 Python projects Argusic has installed and timed, flowblade was the 4th fastest to reach a running state, and 3 of 4 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.12 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.23 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/flowblade)Questions
- Does flowblade run?
- Yes. flowblade runs. Argusic installed and launched it on a clean machine in 23 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test flowblade?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1ffef10a7916. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test flowblade?
- The run that produced this verdict cost $0.23: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does flowblade take to install?
- 23.1 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 flowblade need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing flowblade?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does flowblade compare with the alternatives?
- Of the 4 Python projects Argusic has installed and timed, flowblade was the 4th fastest to reach a running state, and 3 of 4 reached one at all.
- Where is the evidence for flowblade?
- 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.