Clip-Anything

Clip any moment from any video with prompts

Runs with mockssource: GitHubhomepagePythonMITcommit f455b2d306ce

Python, MIT licensed. The project labels itself: ai video, ai video generator, ai video maker, clipanything, clipbasic, shorts, shorts maker and sora video.

Clip-Anything runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7.4 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Clip-Anything transcribes a video with OpenAI Whisper (tiny model), calls a configurable LLM API for segment selection, and outputs a valid H.264/AAC MP4 clip with fades.

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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.08 (measured)
recorded runs
1
last tested
stars
321
forks
60
open issues
0
watchers
7
size
22 MB
created
last push

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.

Time lost to each failure while testing Clip-Anything, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • openai-whisper build fails due to pkg_resources missing in modern setuptools build-isolation2 minutes
  • moviepy 2.x removed moviepy.editor module1 minute
  • Hardcoded 'Bearer groq-key' and groq.com URL in app.py1 minute
  • ffmpeg prompts for overwrite on temp_audio.wav0.3 minutes
  • Externally-managed pip environment blocks system install0.2 minutes
  • python command not found (Debian uses python3)0.1 minutes
Install time
7 minutes
Cold machine to finish
8 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
python3 app.py ran with GROQ_API_URL=http://localhost:8888/v1/chat/completions GROQ_API_KEY=test, exited 0, produced edited_output.mp4 (4s from 5s input). ffmpeg -v error -i edited_output.mp4 -f null - exited 0.
Model tokens used
85,364
Exact commit tested
f455b2d306ce
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

/bin/sh -lc "python3 -c \"
import subprocess, time
t0 = 1792923360  # approximate start
tn = int(time.time())
print(f'Elapsed: {(tn-t0)/60:.1f} min')
\"" in /work/repo
 succeeded in 0ms:
Elapsed: 7.4 min
All good. Let me produce the final structured report.
tokens used
85,364
All good. Let me produce the final structured report.

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

  • Installed in 7.4 minutes, faster than the median of the 5 comparable projects Argusic has measured.
  • Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 6 ai-video projects Argusic has installed and timed, Clip-Anything was the 3rd fastest to reach a running state, and 4 of 6 reached one at all.

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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.08

Topics (from GitHub)

ai-videoai-video-generatorai-video-makerclipanythingclipbasicshortsshorts-makersora-videosora-video-aitext-to-videotext-to-video-generationvideo-editingyoutube-shorts

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/Clip-Anything.svg)](https://argusic.com/subject/clip-anything)

Questions

Does Clip-Anything run?
Clip-Anything runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test Clip-Anything?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f455b2d306ce. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test Clip-Anything?
The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Clip-Anything take to install?
7.4 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 Clip-Anything need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Clip-Anything?
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 Clip-Anything compare with the alternatives?
Of the 6 ai-video projects Argusic has installed and timed, Clip-Anything was the 3rd fastest to reach a running state, and 4 of 6 reached one at all.
Where is the evidence for Clip-Anything?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion