olive
Free open-source non-linear video editor
Runssource: GitHubhomepageC++GPL-3.0commit 7e0e94abf661
C++, GPL-3.0 licensed. The project labels itself: cpp, cross platform, glsl, hardware acceleration, linux, macos, opengl and qt.
olive runs. An Argusic agent installed it in 73 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Olive Video Editor 0.2.0 builds successfully with Qt6, all 3 test suites pass (compositing, common, timeline), and the application binary runs and displays its version and help text.
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.
- OpenImageIO and OpenCV had dozens of transitive shared library dependencies (GDAL, OpenVDB, DCMTK, OpenCV, etc.) that required hundreds of MB of additional runtime libs30 minutes
- Missing OpenGL, FFmpeg, OpenColorIO, OpenImageIO, OpenEXR, Imath, PortAudio, Zlib, XKB development headers/libraries15 minutes
- Missing Qt6 development headers and cmake configs - only runtime libs were installed5 minutes
- Cmake config files from Debian packages had incorrect absolute paths referencing /usr/lib/x86_64-linux-gnu instead of our sysroot5 minutes
- QStringRef was removed in Qt6 causing compilation error in serializer230220.cpp2 minutes
- Install time
- 73 minutes
- Cold machine to finish
- 74 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- Model tokens used
- 1,113,254
- Exact commit tested
- 7e0e94abf661
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
100% tests passed, 0 tests failed out of 3 Total Test time (real) = 1.13 sec === Version === 0.2.0-7e0e94ab Everything works. Let me compute the elapsed exec /bin/sh -lc "# Calculate total time from session start ps -o etime= -p 273 2>/dev/null | tr -d ' ' | head -1" in /work/repo succeeded in 0ms: 01:13:05 tokens used 1,113,254
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 73 minutes.
- Recovered from all 5 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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs | 100.00 | 0.64 | |
| Argusic Runner | 2/3 | Ran out of time | 0.00 | 0.38 |
Topics (from GitHub)
cppcross-platformglslhardware-accelerationlinuxmacosopenglqtvideo-editorvstwindows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/olive)Questions
- Does olive run?
- Yes. olive runs. Argusic installed and launched it on a clean machine in 73 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test olive?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7e0e94abf661. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test olive?
- The run that produced this verdict cost $0.64: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does olive take to install?
- 73 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 olive need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing olive?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for olive?
- 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.