openshot-qt
OpenShot Video Editor is an award-winning free and open-source video editor for Linux, Mac, and Windows, and is dedicated to delivering high quality video editing and animation solutions to the world.
Runssource: GitHubhomepagePythonNOASSERTIONcommit d2737c461f57
Python, NOASSERTION licensed. The project labels itself: c plus plus, ffmpeg, gplv3, openshot, python, qt5, video and video editing.
openshot-qt runs. An Argusic agent installed it in 34 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
OpenShot qt 4.0.0 test suite passes all 513 tests on Ubuntu noble with PyQt6 6.11.0, libopenshot 0.3.2, and FFmpeg 6.1; app initializes to window creation, needing a display server for GUI.
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.
- libopenshot 0.3.2 from Ubuntu noble missing Clip.CreateReader, ScreenCaptureSettings, ScreenCaptureReader, ClipProcessingJobs APIs8 minutes
- PyQt6 ButtonRole enum comparison fails in style_message_box (role == QDialogButtonBox.YesRole returns False on PyQt6 despite same value)3 minutes
- tabifiedDockWidgets() returns empty on offscreen/minimal Qt platform until QMainWindow.show() is called3 minutes
- libopenshot 0.3.2 does not support Clip().SetJson({"reader":...}).Open() - test assumed newer API2 minutes
- Install time
- 34 minutes
- Cold machine to finish
- 34 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- python3 -m unittest discover -s src/tests -t src/tests returned 'Ran 513 tests in 0.951s ... OK' (0 failures, 0 errors)
- Model tokens used
- 563,297
- Exact commit tested
- d2737c461f57
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 1301ms:
Ran 513 tests in 0.951s
OK
All 513 tests pass. Now let me produce the final report
exec
/bin/sh -lc "ARGUSIC_RESULT: {\"install_succeeded\": true, \"launch_succeeded\": true, \"install_mi…
exited 127 in 0ms:
/bin/sh: 1: ARGUSIC_RESULT:: not found
The final result must be output as plain text in my message, not via a shell command. Let me provid…
tokens used
563,297
The final result must be output as plain text in my message, not via a shell command. Let me provid…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 4 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.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 34 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
- Its license file could not be classified automatically, so check it yourself before using it.
Of the 5 c-plus-plus projects Argusic has installed and timed, openshot-qt was the 4th fastest to reach a running state, and 4 of 5 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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.31 | |
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.19 |
Topics (from GitHub)
c-plus-plusffmpeggplv3openshotpythonqt5videovideo-editingvideo-production
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/openshot-qt)Questions
- Does openshot-qt run?
- Yes. openshot-qt runs. Argusic installed and launched it on a clean machine in 34 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test openshot-qt?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d2737c461f57. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test openshot-qt?
- The run that produced this verdict cost $0.31: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does openshot-qt take to install?
- 34 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 openshot-qt need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing openshot-qt?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does openshot-qt compare with the alternatives?
- Of the 5 c-plus-plus projects Argusic has installed and timed, openshot-qt was the 4th fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for openshot-qt?
- 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.