printfilm

PRINTFILM: AI short-video marketing and AI short-drama creation platform

Runssource: GitHubhomepagePythonMITcommit cdcd1f73d667

Python, MIT licensed. The project labels itself: ai, ai video, short drama and short video.

printfilm runs. An Argusic agent installed it in 21 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Backend API running on port 8000, PostgreSQL on 15432, Redis on 16379; 609/614 tests pass; frontend fails to build due to Node 18 incompatibility with Vite 8

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.17 (measured)
recorded runs
2
last tested
stars
7,463
forks
840
open issues
10
watchers
404
size
47 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.

What went wrong, in the agent's own words

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

  • 4 pre-existing test failures due to updated VENDOR_VIDEO_YUAN_5S_BY_RES pricing (seedance-2-5 720p changed from ~5.04 to 7.56 yuan) - tests assert old 336 fen diff value: test_fragment_video_estimate_720p_doubles_480p, test_videos_estimate_hd_doubles_480p_preview, test_shot_regen_video_estimate_uses_project_hd, test_narration_edit_invalidates_continuous_audio
  • Frontend cannot build (Vite 8 requires Node 22+ for styleText from node:util; container has Node 18.19.1)
Install time
21 minutes
Cold machine to finish
21 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
uvicorn app.main:app --port 8000 started; curl -s http://127.0.0.1:8000/api/health returned 200 with ok=true, ark_mock=true, db_pool connected, task_runtime healthy; 613 total tests: 609 passed, 4 failed (pre-existing pricing assertion drift)
Model tokens used
443,332
Exact commit tested
cdcd1f73d667
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 1, 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.

Total: ~15 min
exec
/bin/sh -lc '# Final timing check
echo "start: 19:31"
echo "now: $(date +%H:%M)"
echo "Elapsed: ~21 minutes"' in /work/repo
 succeeded in 0ms:
start: 19:31
now: 19:53
Elapsed: ~21 minutes
tokens used
443,332

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 2 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 MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 21 minutes to install, slower than the median of the 46 comparable projects Argusic has measured.

Of the 47 Python projects Argusic has installed and timed, printfilm was the 47th fastest to reach a running state, and 32 of 47 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.17
Argusic Runner1/3Runs100.000.17

Topics (from GitHub)

aiai-videoshort-dramashort-video

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/printfilm.svg)](https://argusic.com/subject/printfilm)

Questions

Does printfilm run?
Yes. printfilm runs. Argusic installed and launched it on a clean machine in 21 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test printfilm?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit cdcd1f73d667. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test printfilm?
The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does printfilm take to install?
21 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 printfilm need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing printfilm?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does printfilm compare with the alternatives?
Of the 47 Python projects Argusic has installed and timed, printfilm was the 47th fastest to reach a running state, and 32 of 47 reached one at all.
Where is the evidence for printfilm?
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.

Discussion