PodRacer
____ _ ____ | _ \ ___ __| | _ \ __ _ ___ ___ _ __ | |_) / _ \ / _` | |_) / _` |/ __/ _ \ '__| | __/ (_) | (_| | _ < (_| | (_| __/ | |_| \___/ \__,_|_| \_\__,_|\___\___|_|
Transfer music to an iPod from Linux without iTunes.
Plug in the iPod, open PodRacer, drag music over.
Midnight-commander-style two-pane UI: browse your music folder on the left, see what is on the iPod on the right. Manual sync, automatic duplicate avoidance, auto-transcode via ffmpeg.
Compatibility
| Device generation | Supported? | Tested on Physical Hardware? |
|---|---|---|
| iPod nano 3G | Yes | Yes |
| iPod nano 1G–2G | Yes | No |
| iPod classic 1G–5.5G | Yes | No |
| iPod mini | Yes | No |
| iPod nano 4G+ | No | No |
| iPod classic 6G/7G | No | No |
| iPod shuffle | No | No |
| iPod touch | No | No |
nano 4G+ and classic 6G/7G (iTunesSD format) are planned.
Systems
Linux only, 64-bit: x86_64 (amd64) and ARM64 (aarch64) binaries, plus ARM64 via pip or the flatpak. ARM64 builds pass CI smoke tests but are not yet verified on real ARM hardware (no Pi or SBC on hand). Runs on any init system: systemd, OpenRC, runit, sysvinit. There is no systemd in the code; the device layer talks to the udisks2 daemon over D-Bus instead of udev or udisksctl. Non-systemd systems need udisks2 running and a desktop session to authorize mounts (elogind, or a local console login).
Verified on systemd distros; Artix and Devuan are next on the test list.
Want to help?
The biggest help: a real iTunesDB dump from a device we cannot verify ourselves. Nano 1G-2G especially, but any classic or mini helps, and a Shuffle 1G/2G dump would unlock the order-only DB work. One command:
python3 scripts/dump_itunesdb.py
then open a PR adding the file under fixtures/public/<model>/, or send it along. Heads up: the DB lists your whole music library (titles, artists, play counts), so only share one you are comfortable with.
I'd love to buy some iPods to test on if possible. I have a Buy Me a Cofee
Themes
Six of the twenty-one built-in themes, rendered in demo mode (synthetic data only). Run ./podracer --demo to preview any theme with a mock library, nothing real is touched.
Run it
- From PyPI:
pipx install podracer_mapple(orpip install podracer_mappleinside a venv), then launchpodracerfrom a terminal. - From the repo:
scripts/build_onefile.shproduces./podracer(one file, ~90 MB;podracer-arm64on ARM64). Symlink it into your PATH:ln -s "$PWD/podracer" ~/.local/bin/podracer. Launch from a terminal or double-click. - From source:
PYTHONPATH=src python3 -m podracer.main
pip installs the app only. It still needs
ffmpeg(tag reading + transcoding) andudisksctl(auto-mounting) on your system.
Plug in the iPod, and that's the whole setup. Enjoy the click of the wheel.
The podracer_db library
PodRacer is built on a small, standalone library: podracer_db parses and writes the classic iTunesDB format, the database on nano 1G–3G, classic 1G–5.5G, and mini. Pure stdlib, zero dependencies, no Qt.
It is also handy on its own. Point it at the iTunesDB file from a device or a backup and you get every track with its tags, play counts, and ratings, plus the playlists, smart-playlist rules included:
from pathlib import Path
from podracer_db import parse_db, write_db
lib = parse_db(Path("iTunesDB").read_bytes())
for track in lib.tracks:
print(track.artist or "Unknown", "-", track.display_title)
# And back the other way: serialize the library to a valid DB,
# hash58 checksum included, ready for a device to boot.
db_bytes = write_db(lib, firewire_guid="0011223344556677")
The write side is hardware-verified: a PodRacer-written DB boots on the real nano 3G with its full library, and the codec round-trips the device's own DB byte-for-byte. The codec is the heart of the app, but it works just as happily without a UI.
Development
- Python 3.13, PySide6 (Qt6) UI in
src/ podracer_dbinpackages/podracer_db/(its own PyPI dist, see above)- ffmpeg for tagging and transcoding to MP3
scripts/extract_fixtures.pypulls the DB and sample tracks from a real iPod for tests- Tests:
python3 -m unittest discover -s tests -t . -v(stdlib only) - Python floor: both dists declare
>=3.11(CI runs 3.13); the onefile and flatpak bundle their own Python, so the floor only affects source and pip installs
Metadata
Release files for podracer-mapple 1.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| podracer_mapple-1.2.1.tar.gz | 798.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| podracer_mapple-1.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 MB
Release files / podracer_mapple-1.2.1.tar.gz
| Download URL | podracer_mapple-1.2.1.tar.gz |
|---|---|
| Size | 798.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
76adec63d39481fcdd56229935ccf22b81ddbef9a97d57226b1ceba00fe73c6d
|
|
BLAKE2b-256 checksum How to use checksums |
ca2315292ffafe985ac94e8d00090e2d26420c8a406d0a7a83410083ba22043f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.
Transparency logRelease files / podracer_mapple-1.2.1-py3-none-any.whl
| Download URL | podracer_mapple-1.2.1-py3-none-any.whl |
|---|---|
| Size | 795.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1bf4f7715d5f5ef25c71cd9b087337074a2ba3009ab3458e3a338d731bf24a08
|
|
BLAKE2b-256 checksum How to use checksums |
a1b555730cef34fe29e0e2a4ce2c9d767fb7ff19a371adfd01aea874db79a303
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.
Transparency logSecurity for podracer-mapple 1.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for podracer_mapple-1.2.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.