The "N folders are named differently" warning now offers to rename the
slave folders to match the master, marked as the recommended first step
after a scan (also linked from the dashboard card).
- A preview lists each rename with the differing characters highlighted;
renames are selectable, and conflicts (the slave already has a folder
with the master's name, symlinks, the quarantine) are skipped with a
reason.
- Only renames the server computes itself are applied; a request can
only narrow them down, never name arbitrary paths. Only slave folders
are renamed.
- Case-only renames go through a temporary name so they also work on
case-insensitive filesystems; a rename interrupted by a crash is
completed on startup (the folder is never removed).
- Renaming everything repeats until folders revealed inside renamed ones
(an album under a renamed artist) are fixed too, then rescans.
- Each rename is an operation in History that can be undone (which also
rescans). Dry run records renames as planned.
Also fixes the Review list not refreshing after a job that started and
finished between two status polls, and logs the new path of operations.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Warnings are now stored and served as structured data (title, detail,
slave/master items, total) and rendered as cards with a Slave -> Master
table: the first five rows, with "Show all" for the rest.
- Renamed folders highlight the characters that differ; non-ASCII
characters get their code point in a tooltip, so look-alikes such as
"-" (U+002D) and "‐" (U+2010) can be told apart.
- Songs in a different folder are grouped by folder pair with a song
count, most affected first, instead of two long examples.
- Folders that only differ by name are no longer also reported as
songs in a different folder.
- Warnings saved as plain text by earlier scans still display.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A singles library naturally has artists and songs the albums library
lacks, so "only N of M top-level folders exist in the master" and "N of M
slave files have no counterpart" were false alarms.
Layout warnings now only flag real layout problems:
- Folders that are the same but named differently (case, punctuation,
accents, "&"/"and", leading/trailing "The"), at the top level and one
level down inside shared folders, with examples.
- Songs found in both libraries that mostly live in a different folder in
the master (e.g. Artist/Song vs Artist/Album/Song). Slave-only songs are
ignored, as are singles/EPs/compilations matched to their album version.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A per-pair "Approximate matching" setting adds a second pass for slave
files the strict rules could not place. It searches the same album with
disc folders (Disc 02, CD2, ...) ignored, then the top-level folder, and
scores titles by edit distance and word containment against a configurable
threshold (default 85%), with a small track-number bonus.
Guards against false matches: version words (live, remix, reprise,
instrumental, ...) must agree, near-tied candidates are left unmatched,
and approximate matches always go to manual review, never auto-link.
Each match records a human-readable reason.
Review now flags matches where the master copy is better as upgrades,
with an Upgrades filter and count and an "Upgrade to master copy" action.
The redundant "master is lossless" warning note is dropped.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The two libraries are now "master" and "slave" everywhere: UI text, API
JSON fields (master_root, rel_master, master_size, ...), Go identifiers,
database columns, quality verdicts, quarantine subfolders and docs.
Existing databases are upgraded by a new migration that renames the
columns in place and rewrites stored "host" values, so pairs, history,
cached verdicts and restorable quarantine entries carry over. Network
"host" usages (SplitHostPort, the Origin/Host check) are unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Matching has always been by relative path, so any folder layout works as
long as both libraries use the same one. Remove the depth and loose-root-file
warnings, which flagged valid layouts, and reword the UI and README to say
"same folder layout on both sides" with Artist/Album/Title.ext only as an
example. The "elsewhere" fallback is now described as same top-level folder,
different subfolder. Add a test covering flat and deeply nested layouts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Go backend (chi, SQLite) with an embedded React/TypeScript UI that finds
songs present in both a host and a slave music library and replaces the
slave copy with a hardlink to the host copy.
- Path-first matching with format/title/album-folder fallbacks
- Auto-linking of byte-identical files, re-verified with cmp before linking
- Manual review with ffprobe quality comparison, downgrade guard and
promote-to-host override
- Build mode to populate an empty slave library from the host
- Dry run by default, atomic stage+rename replacement, quarantine with
retention, undo, path confinement and authenticated UI
- Dockerfile and compose file for Unraid
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cdnutterandClaude Opus 5.5