xgplayer
A HTML5 video player with a parser that saves traffic
Runssource: GitHubhomepageJavaScriptMITcommit 2c4e5f6c44af
JavaScript, MIT licensed. The project labels itself: dash, flv, flv parser, fmp4, hls, hls player, html5 video and html5 video player.
xgplayer runs. An Argusic agent installed it in 2.1 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
yarn install succeeds, yarn build:all builds all 16 packages, full test suite passes (300/300), and the dev server starts on port 8081 and serves HTTP 200
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.
- FetchLoader._getRangeResponseMismatchReason had guard `if (!this._rangeRequestMustReturn206)` preventing content-range validation when flag was falsy, causing test 'rejects range request when content-range and content-length do not match request range' to resolve instead of reject3 minutes
- XhrLoader._getRangeResponseMismatchReason had same guard as fetch.js causing identical test failure2 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- yarn test --silent exited 0, 52 suites passed, 300 tests passed; curl http://127.0.0.1:8081/fixtures/xgplayer/index.html returned 200
- Model tokens used
- 200,572
- Exact commit tested
- 2c4e5f6c44af
- 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.
yarn run v1.22.22 $ yarn libd dev fixtures/xgplayer $ node ./scripts/cli.js dev fixtures/xgplayer > Local: http://127.0.0.1:8081/fixtures/xgplayer/index.html > Network: http://10.130.12.9:8081/fixtures/xgplayer/index.html 200info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. error Command failed with signal "SIGTERM". ---done--- Everything works. Let me compile the final result. tokens used 200,572 Everything works. Let me compile the final result.
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 2.1 minutes.
- Recovered from all 2 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.
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.1 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)
dashflvflv-parserfmp4hlshls-playerhtml5-videohtml5-video-playermp4mp4boxplayervideovideo-playervideoplayer
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/xgplayer)Questions
- Does xgplayer run?
- Yes. xgplayer runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test xgplayer?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2c4e5f6c44af. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test xgplayer?
- 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 xgplayer take to install?
- 2.1 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 xgplayer need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing xgplayer?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for xgplayer?
- 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.