Nothing leaves the folder
No account, no cloud library, no telemetry. It works with the network unplugged, because there is nothing it needs to ask anyone for.
Resonant 2.0 is being built in the open · the current build is 0.2
Your music.
Your folder.
Your tuning.
Resonant plays the folder you already have. No account, no catalogue, no upload. And everything the player creates — ratings, notes, playlists, tunings — stays in open files inside that same folder, so your collection outlives the app.
The signature feature
Change the tuning while the song plays
Most people who want their music at A = 432 Hz end up converting the whole library with a command-line tool and living with two copies of everything. LiveTuner makes it a button: switch reference pitch mid-song, in the same spot, with no reload and no second file. At 440 Hz the processor leaves the chain completely, because a neutral processor still colours the sound.
440 Hz
standard reference · 0.0 cents
A demo of the control, not of the sound. Cents is the honest unit here: 432 Hz sits 31.8 cents below standard, 444 sits 15.7 above, and the ear starts noticing at around 10.
- Per track or everywhere. A track remembers the tuning you left on it and comes back that way.
- Compare by ear. One keystroke walks the presets without ever stopping playback.
- Render it out. The same engine, offline, when you want a tuned copy to take elsewhere.
Built like a vault
The folder is the product
Resonant takes its shape from note-taking tools rather than from streaming apps. Your music stays exactly where it is, in the format you ripped or downloaded. What the player adds goes next to it, in plain files you can read, sync, back up, or walk away with.
Notes, in Markdown in development
Write about a track, an album, a night. Link them to each other. A playlist can be a note holding a list of links, so months later the list still tells you why each track is on it.
It never edits your files behind your back
Tag suggestions stay suggestions. The audio file changes only when you accept, and by default metadata lives in the vault instead, leaving the original exactly as it arrived.
Uninstall and keep everything
The index is a cache that rebuilds itself. Your ratings, notes and tunings are files. Remove the app and the collection you built is still sitting there.
For libraries that got out of hand
Stop scrolling. Start narrowing.
Five hundred tracks is already enough to make playlist-building miserable: every tool asks you to remember what you own and drag it in one item at a time. Resonant turns that around. You describe what you want, and the library narrows to it.
Scope, not screens
Folder, artist, album, format, length, rating, play count, free text. Combine them as removable chips and negate any one of them. You can always see why those forty tracks are on screen.
Many folders, one library
Add as many source folders as you want, each with its own ignore rules and minimum length, so a samples drive never pollutes the list. On a phone it reads only the folder you point at, never the whole device.
A tagger that understands edits
Slowed, sped up, nightcore, remix, bootleg: labels like these stop being noise to strip and become information worth keeping. Resonant can correct the playback speed before fingerprinting, which is how a slowed version finally matches the original recording.
Fast triage in development
A full-screen mode that plays the hook of each untagged track and takes one keystroke per decision, so a neglected library gets sorted in one sitting instead of never.
Light on purpose
Weight is a requirement, not an outcome
These are budgets the build gets measured against, not aspirations. Anything that cannot fit inside them becomes an optional plugin rather than entering the core.
15 MBinstaller ceiling
1 scold start, 10,000 tracks
150 MBmemory while playing
60 fpsscrolling a long list
zeroaudio dropouts, non-negotiable
~0%processor while paused
Plays
MP3 FLAC OGG Opus WAV M4A AAC ALAC AIFF
Open source
A player we can improve together
Resonant is GPL-3.0, and the copyleft is deliberate: improvements come back to everybody, and nobody gets to close the code and sell the collective work back to you. The core stays small and conservative. Plugins and themes are where the community gets to be generous.
Plugins in plain JavaScript in development
Install without recompiling, update without reinstalling the app. No framework required, so nobody is shut out by a choice we made for them.
Themes in plain CSS in development
Documented variables, light and dark, swapped live. Changing how Resonant looks should not require knowing Rust.
The roadmap, the architecture decisions and the reasoning behind each one live in the repository, so anyone arriving can tell what was already considered and turned down.
Browse the repositoryPoint it at a folder and press play
Today’s release is 0.2 for Windows: the player, the automatic tagger and the library. LiveTuner, the vault and the scope filters arrive in 2.0, which is being built in public right now. The jump in numbering is deliberate: this is a rebuild, not a patch.