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 23 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Olive 0.2.0 builds and links fully; the editor binary (15 MiB) prints version and help; all 9 test cases across 3 test suites pass; running requires LD_LIBRARY_PATH to include the rootfs-extracted runtime debs.
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.
- OIIO/OCIO transitive shared libs missing (opencv, dcmtk, boost, gstreamer, gphoto2, gdal, blosc, openvdb, etc., ~100 debs)13 minutes
- Qt6 cmake modules missing; qmake wrapper script used absolute /usr/lib/qt6/bin/qmake which didn't exist4 minutes
- OpenGL headers/libs not found (no -dev packages in container)2 minutes
- FindFFMPEG.cmake chose .a static libs over .so, causing soxr/other link errors2 minutes
- Git submodules (ext/core, ext/KDDockWidgets) not cloned1 minute
- QStringRef removed in Qt6 (serializer230220.cpp)1 minute
- Install time
- 23 minutes
- Cold machine to finish
- 30 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- ctest --output-on-failure: 3/3 tests passed (100%); olive-editor --version printed '0.2.0-7e0e94ab'; timeline-tests: 7/7 passed; common-tests: 1/1 passed; compositing-tests passed
- Model tokens used
- 1,573,944
- 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.
- 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 3, 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.
- FFmpeg library bindings (FindFFMPEG picked `.a` by default; forced `.so` paths) - OIIO/OCIO runtime transitive dependencies (~100 libs including GStreamer, OpenCV, GDAL, OpenVDB… - Qt6 API change (`QStringRef` → `QStringView` in serializer230220.cpp) - Linked with `--allow-shlib-undefined` to handle unresolved OIIO plugins that aren't used at runti… **Verification:** - `olive-editor --version` → `0.2.0-7e0e94ab` - `olive-editor --help` prints usage text - `ctest`: 3/3 test suites pass (100%) - **timeline-tests**: 7/7 passed - **common-tests**: 1/1 passed - **compositing-tests**: passed **Note:** Running the binary requires `LD_LIBRARY_PATH="/tmp/rootfs/usr/lib/x86_64-linux-gnu:/usr/l…
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 3 times, so the result is not a one-off.
What did not, or is not known
- Took 23 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
Of the 4 cpp projects Argusic has installed and timed, olive 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.
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)
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 23 minutes, hitting 6 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. 3 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.43: 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?
- 23 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?
- 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 olive compare with the alternatives?
- Of the 4 cpp projects Argusic has installed and timed, olive was the 4th fastest to reach a running state, and 3 of 4 reached one at all.
- Where is the evidence for olive?
- All 3 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.