EdenLive
Real-time generative rendering for interactive worlds, from any visual reference.
Runs with mockssource: GitHubPythonApache-2.0commit 0b78d211bfa8
Python, Apache-2.0 licensed. The project labels itself: game, game engine, generative rendering, interactive worlds, real time, renderer, video generation and world model.
EdenLive runs, with stand-ins for the services it depends on. An Argusic agent installed it in 28 minutes and hit 5 errors on a clean machine with no GPU, and the whole session was recorded.
EdenLive Python package installs and its CPU-safe test suite (75 of 76 tests) passes on Python 3.12 with PyTorch 2.15 CPU; the inference CLI reports the expected CUDA GPU requirement, and sample proxy recordings decode successfully via ffmpeg.
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 84 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. 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.
- Missing triton module for flashdreams attention kernels2 minutes
- numpy 2.5.4 incompatible with flashdreams (<2.5 required)1 minute
- No CUDA GPU available; offline inference requires NVIDIA GPU
- Missing playwright module for game rendering and cover capture tests
- decord 0.6.0 not supported on this platform (pip check warning)
- Install time
- 28 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 5 hit, 3 fixed with no human help
- How the result was proved
- cd /work/repo && python -m pytest edenlive/tests/ -q -> 29 passed; cd /work/repo/realtime && python -m pytest apps/cam2v/tests/ integrations_v2/eden/tests/test_import_game.py integrations_v2/eden/tests/test_game2v_session_init.py integrations_v2/eden/tests/test_reference_latents.py --import-mode=importlib -q -> 46 passed, 1 skipped; ffmpeg -v error -i examples/samples/cryo-crossing/recording.mp4 -f null - -> exit 0; python -m edenlive.scripts.infer --help -> usage printed; edenlive-infer --help -> usage printed
- Model tokens used
- 1,070,617
- Exact commit tested
- 0b78d211bfa8
- 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
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 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.
/bin/sh -lc 'cd /work/repo && /tmp/edenlive_venv/bin/python -c "import numpy; print(numpy.__version… succeeded in 0ms: 2.4.6 exec /bin/sh -lc 'cd /work/repo/realtime && /tmp/edenlive_venv/bin/python -m pytest apps/cam2v/tests/ in… succeeded in 5048ms: ..............................s................ [100%] 46 passed, 1 skipped in 3.50s Now I have a complete picture. Let me compile the final report. tokens used 1,070,617 Now I have a complete picture. Let me compile the final 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
- Licensed Apache-2.0, 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.
- Took 28 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
- Hit 5 errors during setup, 2 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 5 game projects Argusic has installed and timed, EdenLive was the 5th fastest to reach a running state, and 4 of 5 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 84.00 | 0.23 |
Topics (from GitHub)
gamegame-enginegenerative-renderinginteractive-worldsreal-timerenderervideo-generationworld-model
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/edenlive)Questions
- Does EdenLive run?
- EdenLive runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 28 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test EdenLive?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0b78d211bfa8. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test EdenLive?
- The run that produced this verdict cost $0.23: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does EdenLive take to install?
- 28 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 EdenLive need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing EdenLive?
- 5 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does EdenLive compare with the alternatives?
- Of the 5 game projects Argusic has installed and timed, EdenLive was the 5th fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for EdenLive?
- 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.