media-chrome
Custom elements (web components) for making audio and video player controls that look great in your website or app.
Runssource: GitHubhomepageTypeScriptMITcommit 803787e81917
TypeScript, MIT licensed. The project labels itself: audio, audio player, media chrome, mux, ui components, video, video player and web components.
media-chrome runs. An Argusic agent installed it in 2.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The media-chrome project installs, builds ESM/CJS/IIFE/React outputs, serves the dev site on port 8000, and runs 619+ of 721+ unit tests in headless Chromium. The 5-6 failures are environmental (no GPU codec for H.264 decode in container).
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.
- 5-6 tests fail: headless Chromium cannot decode H.264 video5 minutes
- CHROME_PATH not set and no Chrome binary found2 minutes
- Chromium sandbox not available in container1 minute
- Install time
- 3 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npm test:unit: 620 passed, 5 failed, 96 skipped out of 19 test files; dev server returned HTTP 200
- Model tokens used
- 49,898
- Exact commit tested
- 803787e81917
- 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.
The 5 failures are all due to media playback being unsupported in headless Chromium in this contain…
**Fix applied:** Added `--no-sandbox` and `--disable-gpu` to the Chrome launch args in `test/web-te…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 2.5, "errors": [{"msg": "C…
exec
/bin/sh -lc "cat << 'ARGUSIC_EOF'
ARGUSIC_EOF" in /work/repo
succeeded in 0ms:
tokens used
49,898Replay 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 2.5 minutes, faster than the median of the 7 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 8 audio projects Argusic has installed and timed, media-chrome was the 2nd fastest to reach a running state, and 6 of 8 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 2.5 minutes after the clone.
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-playermedia-chromemuxui-componentsvideovideo-playerweb-components
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/media-chrome)Questions
- Does media-chrome run?
- Yes. media-chrome runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test media-chrome?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 803787e81917. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test media-chrome?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does media-chrome take to install?
- 2.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 media-chrome need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing media-chrome?
- 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 media-chrome compare with the alternatives?
- Of the 8 audio projects Argusic has installed and timed, media-chrome was the 2nd fastest to reach a running state, and 6 of 8 reached one at all.
- Where is the evidence for media-chrome?
- 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.