qm-music
🎧☁️ Your Private Music Service
Runssource: GitHubJavaApache-2.0commit e14547e15540
Java, Apache-2.0 licensed. The project labels itself: music, music server, self hosted and subsonic server.
qm-music runs. An Argusic agent installed it in 8 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
qm-music builds with Maven, passes 201 tests, and runs on port 6688 serving a web UI and Subsonic-compatible REST API (ping returns status=ok)
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.
- Install time
- 8 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- mvn test exited 0, 201 passed 0 failed 0 errors 8 skipped; curl http://127.0.0.1:6688/ returned 200; curl http://127.0.0.1:6688/rest/ping?u=admin&p=admin&v=1.16.0&c=test returned HTTP 200 with XML body <subsonic-response status='ok' version='1.16.1' serverVersion='v2.4.0' openSubsonic='true'/>
- Model tokens used
- 248,331
- Exact commit tested
- e14547e15540
- 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.
tokens used 248,331 Subsonic API responds correctly: ```xml <subsonic-response xmlns="http://subsonic.org/restapi" status="ok" version="1.16.1" serverVersion="… ``` Everything works end to end. Let me compile the results. Key findings: - **Install**: Java 25 (Eclipse Temurin) downloaded and set up manually; Maven 3.9.9 downloaded man… - **Tests**: `mvn test` ran 201 tests, all passed (0 failures, 0 errors, 8 skipped). - **Launch**: The app started in ~3.5 seconds on port 6688 in dev mode using SQLite, with Flyway mi… - **No code changes were required** — the project compiled and ran from source as-is after installi…
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.
- Installed in 8 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
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 8 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/qm-music)Questions
- Does qm-music run?
- Yes. qm-music runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test qm-music?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e14547e15540. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test qm-music?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does qm-music take to install?
- 8 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 qm-music need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing qm-music?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for qm-music?
- 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.