stemdeck
Stemdeck is an modern stem extraction platform for musicians,producers and hobbyists, designed to isolate vocals, drums, bass, piano and guitar for practice, transcription, remixing, and creative audio workflows through a modern and interactive interface
Runssource: GitHubJavaScriptApache-2.0commit 96647d715fc4
JavaScript, Apache-2.0 licensed.
stemdeck runs. An Argusic agent installed it in 5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
uv sync completed, server starts and serves 200, full test suite passes 2406/2410
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.
- diffq C extension build failed: missing Python.h (python3.12-dev headers not installed)5 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 19 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- uvicorn app.main:app returned 200 on / and /health endpoints; pytest returned 2406 passed, 4 skipped, 0 failed
- Model tokens used
- 105,079
- Exact commit tested
- 96647d715fc4
- 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.
Let me calculate the install time - I started at about 13:16 and the first test finished, and the w… Let me compile the final JSON. Here's what I did and found: ## Work Performed **Install** — `uv sync` succeeded after fixing the `diffq` build issue. The missing `python3.12-dev… **Server** — `uvicorn app.main:app` starts cleanly and responds HTTP 200 on both `GET /` and `GET /… **Tests** — Full suite: **2406 passed, 4 skipped, 0 failed** (153s). - 3 TLS listener tests skipped — they require a compiled desktop binary (`cargo build` in `desktop/… - 1 fpcalc test skipped — needs the `fpcalc` binary (from `libchromaprint-tools` package, not insta… - All other tests including stem API, pipeline analysis, beat detection, lyrics, identification, qu… **Error encountered & fixed:** - `diffq==0.2.4` (dependency of `audio-separator`) couldn't compile its `bitpack.c` Cython extensio…
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 1 error 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Took 5 minutes to install, slower than the median of the 6 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 7 JavaScript projects Argusic has installed and timed, stemdeck was the 6th fastest to reach a running state, and 4 of 7 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.
- A quick evaluation: it was running 5 minutes after the clone.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/stemdeck)Questions
- Does stemdeck run?
- Yes. stemdeck runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test stemdeck?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 96647d715fc4. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test stemdeck?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does stemdeck take to install?
- 5 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 stemdeck need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing stemdeck?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does stemdeck compare with the alternatives?
- Of the 7 JavaScript projects Argusic has installed and timed, stemdeck was the 6th fastest to reach a running state, and 4 of 7 reached one at all.
- Where is the evidence for stemdeck?
- 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.