switchfin
Third-party native Jellyfin client for PC/PS4/PSVita/Nintendo Switch
Runssource: GitHubC++Apache-2.0commit ee04d1d465a2
C++, Apache-2.0 licensed. The project labels itself: jellyfin, jellyfin client, mpv, nintendo switch and nintendo switch homebrew.
switchfin runs. An Argusic agent installed it in 25 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Switchfin builds for desktop and starts on the virtual display: the -version flag prints '2d585b2ca07c ee04d1d' and the GUI window titled 'Switchfin for Linux' 1280x720 opens and stays running under Xvfb with a session D-Bus.
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 90 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.
- Link errors: undefined symbols from static libavformat/libavcodec and transitive libmpv deps12 minutes
- Missing X11 headers/xkb (GLFW X11)4 minutes
- Missing wayland-scanner (GLFW build dep)3 minutes
- FindCURL/FindMPV/FindDBus could not locate headers/libs in local prefix3 minutes
- wayland-client.h missing for app's GLFW_EXPOSE_NATIVE_WAYLAND2 minutes
- App aborted at startup: dbus_bus_name_has_owner assertion (no session bus in container)2 minutes
- Install time
- 25 minutes
- Cold machine to finish
- 30 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- cmake --build build_new returned '[100%] Built target Switchfin'; ./build_new/Switchfin -version printed '2d585b2ca07c ee04d1d' and exited 0; under dbus-run-session + Xvfb the process stayed alive and xwininfo -root -tree listed window 0x200007 'Switchfin for Linux' 1280x720.
- Model tokens used
- 952,929
- Exact commit tested
- ee04d1d465a2
- 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.
3. Missing CUR→ fixed include dir to `/usr/include/x86_64-linux-gnu` and typed `CURL_LIBRARY`/`CU… 4. Missing MPV (dedicated `FindMPV.cmake`) → gave explicit `-DMPV_INCLUDE_DIR`/`-DMPV_LIBRARY`. 5. Missing DBus headers → added `/usr/include/dbus-1.0` include dir. 6. Missing `wayland-client.h`, `glfwGetWaylandDisplay` → installed wayland dev packages and rebui… 7. Static lib dependency cascades (`libssh`, `libavformat`/avcodec etc.) → linked all transitive … 8. App crashed at startup: D-Bus assertion because no session bus → found `dbus-run-session` on t… - **Verification**: - `cmake --build build_new` completed: `[100%] Built target Switchfin`, binary 9.1 MB. - `./build_new/Switchfin -version` printed `2d585b2ca07c ee04d1d` and exited 0. - Under Xvfb (`DISPLAY=:99`) with `dbus-run-session` + `XDG_RUNTIME_DIR`, process stayed alive (8… No test suite is included in the repo, so the deepest end-to-end check is: binary builds, version c… Final line:
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 6 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 Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 25 minutes to install, slower than the median of the 8 comparable projects Argusic has measured.
Of the 9 jellyfin projects Argusic has installed and timed, switchfin was the 9th fastest to reach a running state, and 5 of 9 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.42 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.24 |
Topics (from GitHub)
jellyfinjellyfin-clientmpvnintendo-switchnintendo-switch-homebrew
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/switchfin)Questions
- Does switchfin run?
- Yes. switchfin runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test switchfin?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ee04d1d465a2. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test switchfin?
- The run that produced this verdict cost $0.42: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does switchfin take to install?
- 25 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 switchfin need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing switchfin?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does switchfin compare with the alternatives?
- Of the 9 jellyfin projects Argusic has installed and timed, switchfin was the 9th fastest to reach a running state, and 5 of 9 reached one at all.
- Where is the evidence for switchfin?
- 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.