music-player
An extensible music server written in Rust , single binary, zero dependency 🚀🎵✨
Runssource: GitHubRustMITcommit 1658a2b247a8
Rust, MIT licensed. The project labels itself: audio, audio streaming, cli, daemon, graphql, grpc, mp3 and mpd.
music-player runs. An Argusic agent installed it in 18 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
music-player builds and its test suite passes (158 of 158, 2 pre-existing ignores for external servers). Binary prints version and help. The core daemon, gRPC server, client, playback, scanner, tracklist, storage, migration, settings, entity, types, graphql, addons, and discovery crates all compile and test cleanly. Desktop/Tauri/webui crates are excluded due to missing GTK dev libraries.
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 98.8 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.
- playback integration tests fail — default OutputConfig::Cpal unsupported without cpal3 minutes
- ALSA dev headers (libasound2-dev) not found — pkg-config cannot find alsa.pc2 minutes
- protoc compiler not found — prost-build requires it for gRPC codegen1 minute
- Install time
- 18 minutes
- Cold machine to finish
- 46 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- cargo test across 14 workspace members: 158 passed, 0 failed, 2 ignored; binary --version returns 0.2.1
- Model tokens used
- 271,267
- Exact commit tested
- 1658a2b247a8
- 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.
**Tests:** `cargo test` across 14 core workspace members: **158 passed, 0 failed, 2 ignored** (Subs… **Binary verification:** `./target/debug/music-player --version` returns `music-player 0.2.1`. tokens used 271,267 All tests pass and the binary builds and runs. Here's my final report: **Errors encountered:** 1. **Missing `libasound2-dev` (ALSA headers)** — The `cpal` crate needs `alsa.pc` from the dev pack… 2. **Missing `protoc` compiler** — The `prost-build` crate in `music-player-server` needs `protoc`.… 3. **Playback tests failing** — The default `OutputConfig::Cpal` can't open without the cpal featur… **Build:** `cargo build` exits 0 — binary at `target/debug/music-player` (744 MB debug). **Tests:** `cargo test` across 14 core workspace members: **158 passed, 0 failed, 2 ignored** (Subs… **Binary verification:** `./target/debug/music-player --version` returns `music-player 0.2.1`.
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 18 minutes, faster than the median of the 4 comparable projects Argusic has measured.
- Recovered from all 3 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.
Of the 5 audio projects Argusic has installed and timed, music-player was the 2nd fastest to reach a running state, and 4 of 5 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
Topics (from GitHub)
audioaudio-streamingclidaemongraphqlgrpcmp3mpdmusicmusic-playermusic-servermusic-streamingplayerrustself-hostedserverslinttokiotypesensewebassembly
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/music-player)Questions
- Does music-player run?
- Yes. music-player runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test music-player?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1658a2b247a8. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test music-player?
- The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does music-player take to install?
- 18 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 music-player need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing music-player?
- 3 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 music-player compare with the alternatives?
- Of the 5 audio projects Argusic has installed and timed, music-player was the 2nd fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for music-player?
- 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.