Repository navigation
Everything since 0.2.0, tested in ten release candidates (0.3.0-rc.1 to 0.3.0-rc.10).
AI assistants (MCP)
- Crossfade has its own MCP server (Streamable HTTP at
/mcp, Bearer token). Assistants can search and compare your library, build playlists and fades, sync, match songs, tidy up and use time travel. See docs/mcp.md. - Mood playlists from your own music, with explained picks, confidence thresholds, exclusions and song or time limits. Mood and genre labels come from the assistant; Crossfade does no audio analysis.
- Assistants act on their own. Only deleting waits for you: removing songs, duplicates or playlists, deleting a fade, exact restores, held deletions, or switching deletion sync on or loosening it. If something changes after the preview so that a proposal would now delete, it becomes an approval instead of running.
- Approvals show up as cards at the top of the home page, with a short summary, the preview, Allow and Discard.
- Account → AI assistants manages personal keys (read, sync, manage), open proposals and activity. Revoking all keys also cancels open proposals.
Fades
- Sorting rules: a receiving collection can have a rule (moods, genres, tags, languages, energy, artists, or "rest" for whatever no other rule takes) and then gets only the songs that fit. A sender such as your liked songs can work as an inbox: it lets a song go once the song is in every rule collection it fits. A "Sort your likes" template sets this up.
- Deletions without asking: switch off Ask first and removals are passed on without being held. Fades that still ask now hold deletions only above 10 songs (or 20 %), up from 5.
- Song order: songs arrive in their source's order. A new receiving playlist is built like the playlist it copies, and later additions go to the end.
- Likes in like order: liked songs follow one timeline across services, ordered by when they were liked. A fade can put existing likes, and receiving playlists, back in that order. A friend sorts their own playlist in your fade.
- Removals from a sending collection are passed on in the same sync, once a second read a few seconds later confirms them. Apple Music alone keeps a 10-minute wait, because it briefly drops songs that were just added. Crossfade then runs the fade again by itself.
- Service breaks: when a service runs out of quota or asks Crossfade to wait, nothing is sent to that service until the break is over, for every account on the instance. Affected fades show "Waiting for …" instead of "Last sync failed", send no error notification and carry on by themselves. If the service gives no wait time, breaks get longer each time (10 min up to 6 h). The health page lists every break.
Matching
- Matches made by hand count everywhere: in every fade (also ones shared with friends), when adding to your library and in later searches. Account → Matches lists them so you can listen, pick another version or remove a match.
- Fewer odd versions: sped up, bass boosted, 8D, mashups, sessions, interludes, genre and language versions and similar labels count as a different recording and are at most a suggestion. Part numbers ("Pt. 2", "Teil 3") make a different song.
- When a recording is on several releases, the release the source uses wins, so songs no longer arrive with the wrong cover. Compilations come last.
- In review, a version is only preselected when it clearly is the same song. Each version shows its artist and its version.
Faster syncs
- The services in a fade read, search and add at the same time. Each service still gets one request at a time. In simulated runs a first sync of 300 songs took 17 s instead of 35.
- Matching remembers its text work: on 5,000 songs the first sync needs well under half the computing time, and the tidy-up suggestions load in 0.4 s instead of 1.5.
- YouTube Music only retries a failed request when that can help, and Apple Music looks up its favourites playlist once per sync instead of on every read. Both send fewer requests.
Look and layout
- Neutral grey surfaces in light and dark mode, with one calm blue as the only accent colour. Clearer fade colours, a new app icon and favicon. Existing fades move to the new shade of their colour; custom colours stay.
- Phone: tighter page headers, the search field moves to the top while you search, previews float above sheets, and the review card fits the screen and scrolls its versions.
- Desktop: Ctrl+K on Windows and Linux, thin scroll bars, text fields that end in "…". The home screen shows the date as its title.
- Messages from the Crossfade server (quota used up, sign-in expired, sync stopped to be safe) appear in your language.
For admins
- Sign in as this person (Account → Users): set things up for someone. The visit ends after two hours. The person's password, AI assistants and the admin pages stay off limits, and admins can't sign in as other admins.
- Unraid: install from the Apps tab (Community Applications). The template now lives in tg099/unraid-templates. Public URL and secret key are optional: without a key, Crossfade creates one in its data folder. Never change it afterwards.
Fixes
- Combined library filters work again.
- Apple Music: if music.apple.com can't be reached while Crossfade loads the web token, you get a normal service error instead of "Error 500".
- The sync progress card and the home page's hint cards keep a steady height.
Updating from 0.2.0
- The database goes from schema 18 to 26 by itself on start: AI assistants, fade rules, deletions without asking, like dates, admin sign-in, fade colours, matches made by hand. Matches you made earlier are copied over. As always, Crossfade backs up the database on start before migrating.
- No configuration changes are needed. To use an assistant, create a key under Account → AI assistants.
Validation
- 325 Python tests passed. Ruff passed. Svelte check: 0 errors, 0 warnings. The production web build passed.
- Each release candidate went through the full release workflow: tests, a smoke test of the image, a vulnerability scan, then amd64 and arm64 builds. This release is the same commit as
0.3.0-rc.10. - Tested only with fake services, not yet against the real ones: services working side by side, the new YouTube retry rules, and how TIDAL and Deezer report their quotas.
Full Changelog: v0.2.0...v0.3.0