A file manager for people with two kinds of files
Both worlds, side by side.
A twin-panel file manager with tabs per pane, independent history, a breadcrumb you can type into and bookmarks that remember which tie collection they belong to. The left pane can be a local disk; the right pane can be the library; drag between them.
- Copy into tie as ▸ with the eight built-in dir-types, or one of your own.
- Pause, resume, stop a copy. Conflicts offer skip, rename, overwrite and apply-to-all.
- Preview mode turns either pane into a thumbnail grid with an in-pane image viewer and video player.
- Hand-off: open a tie image in tie-view, or a track in tie-audio, from the row's own menu.
Albums, not folders of tracks.
"Import as albums…" discovers albums from a music root, matches them against
MusicBrainz (a local Postgres mirror or the web service), fills missing
covers, and places discs with templates like
/{albumartist}/{year} - {album}/cd{disc}. The dry run shows you
every destination before a byte moves.
- By directory, by tags, or auto.
- Use as album cover from any image in the pane.
- Re-import is a version, not a duplicate: contents are content-addressed.
The tag panel does both jobs.
With nothing selected, the tag panel filters the pane. With rows selected, the same panel edits their tags. Directories are taggable too, and favourite tags are shared with tie-view and tie-audio.
- Free-text search in tie panes, ranked, with field selection.
- Breeze file-type icons in light and dark, with per-extension associations.
- Devices (Linux): USB drives through udisks2 and MTP phones through libmtp, with a gvfs fallback.
Ctrl+I filter this page Ctrl+T new tab
Ctrl+Tab switch pane Ctrl+W close tab
Ctrl+click open in new tab Esc leave preview
Shift/Ctrl multi-select ⌘ the same on macOSWhat Delete means
tie-fm is careful about the word “delete”. On a local disk it is the file
manager delete you expect. On a tie: row it removes the reference from the
tree, keeps the blob (other paths may point at the same content), and the library
knows what became unreferenced. The manual has the exact semantics and the
roadmap for blob garbage collection.