MusicBox

一款高颜值、插件化、可深度定制的本地音乐播放器,支持Windows、MacOS、Linux系统

Runssource: GitHubhomepageTypeScriptMITcommit d28652e5dace

TypeScript, MIT licensed. The project labels itself: electron, extension system, javascript, linux, local music player, macos, music and music player.

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

on this Ubuntu container, MusicBox installs (Node 22.23.3, Rust 1.99.1, venv pip), builds renderer+main TS and lint/typecheck cleanly, launches on the Xvfb display with the full UI and preload bridge alive, scans a real music folder and returns correct track metadata, plays in UI state and fetches live network lyrics successfully, and edits FLAC metadata end-to-end;

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.37 (measured)
recorded runs
1
last tested
stars
511
forks
34
open issues
7
watchers
1
size
68 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.

Time lost to each failure while testing MusicBox, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

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

  • npm run build:rs fails on Linux: wasapi 0.21/windows 0.62 are Windows-only; wasapi crate unconditionally imports Win32 COM types, so no feature set compiles on non-Windows (tried default-features=false and cargo [patch] wasapi/windows-future; upstream has no Linux path)20 minutes
  • npm run build:python fails: PyInstaller and Nuitka both need system libpython3.12.so.1.0/python3-dev, absent and uninstallable without root8 minutes
  • No Rust toolchain in container; native audio crate requires one3 minutes
  • Container Node.js v18.19.1 is below the project's required >=222 minutes
  • System pip install refused by PEP 668 (externally-managed-environment)2 minutes
  • Headless container has no ALSA/PulseAudio//dev/snd, so audible WebAudio output could not be observed2 minutes
Install time
38 minutes
Cold machine to finish
17 minutes
Errors hit and fixed
7 hit, 7 fixed with no human help
How the result was proved
electron dist/main/main.js --no-sandbox --remote-debugging-port=9223 launched on DISPLAY=:99 (log showed '应用窗口已显示', renderer DOM 155KB, window.electronAPI true); via CDP: electronAPI.library.scanDirectory('/tmp/fix/music') true, getTracks({}) returned [Test Song/Test Artist 3s flac, test 3.03s mp3]; UI defined rows; play triggered api.lrc.cx request '网络请求成功' + LRC parsed 3 lines; python3 metadata_editor.py wrote FLAC tags (ffprobe shows TITLE/ARTIST/ALBUM/DATE/GENRE) and ffmpeg -v error -f null - decodes both fixtures cleanly; renderer lint+typecheck and architecture check pass
Model tokens used
1,694,083
Exact commit tested
d28652e5dace
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 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.

All checks complete. Compiling the final report now.
**Summary of the mission:**
- **Install:** `npm install`, `npm run install:renderer`, `npm run install:rs`, and `pip install -r…
- **Errors fixed:**
  1. Node <22 (needed ≥22) → installed Node 22.23.3 userland.
  2. Rust missing → installed rustup stable 1.99.1 userland.
  3. System pip blocked by PEP 668 → installed deps into a venv (`/home/runner/venv`), which also p…
  4. Electron SUID sandbox needs root → launched with `--no-sandbox` (documented non-root workaroun…
  5. `npm run build:rs` (Rust native audio engine) cannot compile on Linux: `wasapi`/`windows` are …
  6. `npm run build:python` (PyInstaller/Nuitka freeze) needs `libpython3.12.so.1.0` / `python3-dev…
- **Launch verified:** App launched on Xvfb `:99`; main process registered 22 IPC controllers, crea…
- **test_depth:** tier1_real — real app launch, real IPC/library/metadata/network-lyrics behavior v…

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 7 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.

What did not, or is not known

  • Took 38 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 6 electron projects Argusic has installed and timed, MusicBox was the 6th fastest to reach a running state, and 4 of 6 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 Runner1/3Runs100.000.37

Topics (from GitHub)

electronextension-systemjavascriptlinuxlocal-music-playermacosmusicmusic-playerpluginplugin-systemrusttypescriptwindowsyesplaymusic

Embed the badge

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

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

Questions

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

Discussion