Tauon Music Box: a Python desktop player for large local libraries

Who Tauon Music Box is actually for

Most music players assume a streaming subscription and a small cache. Tauon Music Box assumes the opposite: a folder tree of files you own, possibly with CUE sheets that describe track boundaries inside a single image file, and possibly with tracker formats such as .MOD sitting next to .FLAC. The README lists CUE sheet support, gapless playback, drag and drop, and archive extraction as first-class features rather than plugins. That combination points at a specific user: someone with a curated library measured in thousands of files who wants a desktop window, not a web app.

The second audience is people who already run a media server. The README states that Tauon can stream from a PLEX, Jellyfin or Airsonic server. That matters because the alternative is usually a browser tab or a separate client that does not integrate with a local library. Tauon's pitch is that both live in one window with one queue.

The project is written in Python and licensed GPL-3.0-or-later according to pyproject.toml. If you are choosing a player for a locked-down corporate laptop where you cannot install Python packages, that licence and stack are relevant constraints, not footnotes.

How the Python package is put together

The repository is a Python application, not a compiled binary with a thin binding. pyproject.toml declares requires-python >= 3.10 and a dependency list that includes mutagen for tag reading, musicbrainzngs and pylast for metadata services, pysdl3 and pyopengl for audio and rendering, pygobject for GTK on Linux, and platform markers such as comtypes and keyboard on Windows and pyobjc-framework-cocoa on macOS. In other words, the player leans on the host desktop toolkit rather than shipping its own.

Optional extras are split into an all group and a dev group. The all group adds plexapi, pychromecast, tidalapi and zeroconf, which is where server streaming and cast discovery come from. The dev group is a single entry, pygobject-stubs, and pyproject.toml notes it needs PYGOBJECT_STUB_CONFIG=Gtk3,Gdk3 when installed. That is a type-checking aid, not something a normal user needs.

The build path is also unusual for a desktop app: setup.py subclasses the build and sdist commands so that compile_translations runs before either one. Translations are compiled at packaging time, not at first launch, which means a source install that skips the standard build commands can end up without compiled locale files. The entry point is declared as a GUI script, tauonmb, mapping to tauon.__main__:main.

Installing Tauon Music Box on Linux, Windows and macOS

The README points at three distribution routes and does not give a pip install line, so treat the packaged routes as the supported ones. On Linux, the README says installation is available on Arch Linux and that Tauon is also on Flathub, with portable binaries on the releases page. On Windows and macOS, the README directs you to the installer and DMG on the releases page respectively. The releases listed for this project include v12.0.0 and a pre-release build, so check which one you are pulling.

If you are on Arch, the package name given in the README is tauon-music-box. The README states the package is available on Arch Linux; it does not print an install command, so use your normal package manager with that name.

On other distributions the README's route is Flathub, and it links the application page under the ID com.github.taiko2k.tauonmb. The README warns that Flatpak uses sandboxing and links to a wiki page titled Sandboxing Quirks. Read that before you file a bug about a folder Tauon cannot see; sandboxed access to your music directory is the likely cause, not a parsing failure.

For a source install, setup.py exists and its build and sdist command classes call compile_translations first, so a plain build of the source tree is what compiles the locale files:

python setup.py build

After that, the entry point declared in pyproject.toml is what launches the application:

tauonmb

For a first real use, drag a folder of albums onto the window. The README lists drag and drop and one-click archive extraction as features, so pointing Tauon at a downloads folder and letting it unpack and import is the intended first-run flow. The README does not document an initial scan progress indicator or a rollback for a bad import, so keep a backup of the library directory before the first large import.

Where the dependency stack and sandboxing bite

The honest limitation is the install surface. A Python 3.10+ application with pygobject, pysdl3, pyopengl and dbus-python in its dependency list is sensitive to the host's GTK and audio stack. The README does not publish a troubleshooting matrix for missing codecs, and it does not document rollback for an import that goes wrong. If your distribution does not package tauon-music-box and you do not want Flatpak, your remaining option per the README is a portable binary from the releases page, which shifts the problem from package management to manual updates.

Sandboxing is the second edge. Flatpak is the recommended cross-distribution route, and the README explicitly flags sandboxing quirks. That means paths outside the sandbox, extra drives, and network mounts can behave differently than they would in an unsandboxed install. This is a normal Flatpak trade-off, not a Tauon defect, but it changes what you should expect on first launch.

The project is not archived and the last push was on 2026-08-29, with v12.0.0 released on 2026-08-25. That is a recent cadence, but it also means the current release line is young. If you need a player that has been on the same version for years with no interface changes, this is the wrong tool. The README also does not describe a stable plugin API, so anything you build against internal modules is at risk on upgrade.

Tauon compared with a server-first player like Jellyfin's web client

The nearest alternative for the server-streaming audience is not another desktop player but the web client that ships with the server you already run. Jellyfin's own web interface plays your library in a browser, on any device that has one, with no install on the client machine. The difference in approach is where the library lives. Jellyfin treats the server as the source of truth and the client as a thin view. Tauon treats the local file system as the source of truth and the server as an additional source it can pull from, which is why the README lists PLEX, Jellyfin and Airsonic support alongside local codec support rather than instead of it.

That distinction decides the choice. If your music only exists on a server and you switch machines often, a browser client wins on reach. If you have a local library with CUE sheets and tracker files, a browser client cannot represent that library well, and Tauon's local-first model is the reason to pick it. Tauon also runs as a desktop application with visualisations and customisable widgets, which the README lists as features; a web client does not offer that surface.

Licence and what an upgrade actually costs

pyproject.toml declares license = "GPL-3.0-or-later", and the repository carries a LICENSE file at the top level. For personal use this changes nothing. For redistribution, the practical consequence is that if you ship a modified Tauon, you ship the source under the same terms. If you only install it from Flathub or your distribution, you are a user, not a distributor, and the licence is not something you act on. This is a description of the declared licence, not legal advice; read the LICENSE file if redistribution is on the table.

The upgrade cost is tied to the release cadence. The listed releases are v11.1.1 on 2026-07-20, v12.0.0 on 2026-08-25, and a pre-release build on 2026-08-29. A major version bump inside roughly five weeks means configuration or database formats can move. The README does not document a migration procedure or a downgrade path, and the repository does not expose a documented stable plugin interface, so the safe assumption is that you reinstall rather than patch in place. Flatpak and distribution packages handle that for you; a portable binary from the releases page does not, and you will need to track the releases page yourself.

Editorial conclusion

Tauon suits listeners who keep a large local library, use CUE sheets, or stream from a Plex, Jellyfin or Airsonic server, and who are comfortable installing a Python application with a long dependency list. Skip it if you want a browser-based player, a phone client, or a package that pulls in almost nothing. Before adopting, check three things: whether your distribution packages tauon-music-box or you must use Flathub or a release binary, whether the GPL-3.0-or-later licence fits how you plan to redistribute it, and whether gapless playback and Milkdrop visualisations behave on your platform, since the README does not document platform-specific limitations for either.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes