Skip to content

Releases

v0.3.0

Choose a tag to compare

@tg099 tg099 released this 15 Nov 22:40

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

v0.3.0-rc.9

v0.3.0-rc.9 Pre-release
Pre-release

Choose a tag to compare

@tg099 tg099 released this 15 Nov 21:33

Songs matched by hand

  • A song you match by hand (an open song you resolve, or another version you pick for a song) now counts everywhere: in every fade, also the ones you share with friends, when you add songs to your library, and in every later search. Before, another fade that only takes the exact version judged the song again and showed it as an open song once more.
  • Other fades waiting for that song on the same service drop it from their open songs and add it with their next sync.
  • Account → Matches lists the songs you matched yourself. Listen to the version, pick another one (search the service or paste a link), or remove the match so Crossfade searches for the song again. A new choice counts for songs added from now on; what is already in a collection stays as it is.
  • Each person sees and changes only their own matches. Whoever picks last for a song and service owns that choice.
  • In a song's versions, a version picked by hand says so, and the version check no longer lists it as a mismatch.

Messages in your language

  • Messages Crossfade itself sends from the server, like a used-up quota, an expired sign-in or a sync that stopped to be safe, now show in your language (they used to be English in the German UI). A service's own error text stays as the service sent it.

Fixes

  • Health page: the list under the status card has the same width and inset as the card.
  • Apple Music: when music.apple.com can't be reached while loading the web token, you now get a normal service error instead of "Error 500".

Update notes

  • Database schema 26: a new table for matches made by hand. Matches you made earlier are copied over from the history of changes. As always, a backup is made on start before the migration runs.

Validation

  • 305 Python tests passed. Ruff passed.
  • Svelte check: 0 errors, 0 warnings. The production web build passed.
  • The migration was run on a copy of a real database and on test data with earlier matches made by hand.
  • The Matches page, the health page and the translated messages were checked with fake data in headless Chromium on the desktop (dark) and a phone (light). Not yet tried on a real iPhone or against the real services.

This is a pre-release. Publishing triggers the release workflow to test and build amd64/arm64 images for 0.3.0-rc.9 and testing.

v0.3.0-rc.8

v0.3.0-rc.8 Pre-release
Pre-release

Choose a tag to compare

@tg099 tg099 released this 15 Nov 19:31

Going through songs

  • The card for songs waiting for your pick now fits the screen, with the actions below it. Before, on a phone the lower versions couldn't be reached: the card blocked scrolling and the actions covered the last rows.
  • The versions scroll inside the card, with soft edges where more follows. Only a sideways move picks the card up, so scrolling up and down works anywhere on it, also on the list.
  • Each version shows its artist, and an album that only repeats the title ("Title - Single") reads as "Single". Versions that differ only by artist, like the two sides of a battle, are easier to tell apart.
  • On the desktop the sheet uses the full height. In any sheet, a swipe down on a scrolled list scrolls that list back before it drags the sheet.

Home

  • Two hint cards side by side keep one height when one title wraps, and a card on the next row keeps the height of the row above.

Update notes

  • No database or configuration changes.

Validation

  • 299 Python tests passed. Ruff passed.
  • Svelte check: 0 errors, 0 warnings. The production web build passed.
  • The review card was checked with fake data in headless Chromium at three phone sizes and on the desktop: scrolling the versions by touch, picking the last one, throwing the card sideways from the list, a swipe down on a scrolled list, mouse wheel and arrow keys. Not yet tried on a real iPhone.

This is a pre-release. Publishing triggers the release workflow to test and build amd64/arm64 images for 0.3.0-rc.8 and testing.

v0.3.0-rc.7

v0.3.0-rc.7 Pre-release
Pre-release

Choose a tag to compare

@tg099 tg099 released this 15 Nov 19:04

Faster syncs

  • The services of a fade now read, search and add at the same time instead of waiting for each other. Each service still gets one request at a time (also across two accounts of the same service), so no service is asked more at once than before. Matching, merging, the deletion safety and the order of additions work as before. With simulated network times, a first sync of 300 songs took 17 s instead of 35, and a new like reached the other services in 2.9 s instead of 5.2, with the same changes.
  • The library scan reads its services side by side too.
  • Comparing songs remembers its work on titles, artists and versions. On a library of 5,000 songs the first sync needs well under half the computing time, and the tidy-up suggestions, loaded with every visit to the library, come in 0.4 s instead of 1.5.
  • Fewer repeated requests: the audio version of a YouTube music video is remembered instead of being asked for on every sync, and Apple Music's favourites playlist is looked up once per sync instead of on every read.
  • YouTube Music: a failed request is only tried again when that can help. Network trouble, rate limits and server errors are waited for (up to 12 s), an unreadable answer is tried once more, and a refused request isn't tried again. Before, every error cost 20 s or more. A missing YouTube login now shows as a login problem right away. With the Google sign-in, one dropped connection no longer fails a whole read.

A neutral look

  • Neutral grey surfaces in light and dark mode, with one calm blue as the only brand colour: the incoming curve of the logo, the focus ring and today's bar in the week chart. The glow behind page titles and on the sign-in page is gone, so covers and the fades' own colours carry the colour.
  • Fade colours are clear hues of one lightness. Existing fades move to the new shade of their colour automatically; custom colours stay as they are. A fade without covers shows its own colour, and stand-in covers are one hue deepening into its neighbour. New app icon and favicon.
  • The sync progress card keeps one height while song titles change: long titles end in …, and the content below no longer jumps.

Like order for receiving playlists

  • A playlist that only receives in a fade where likes send can now be put in the fade's like order, earliest first. Songs out of place are removed and added again at the end. Only the playlist's owner can start it, so a friend sorts their own playlist in your fade and you never touch theirs.

Docs

  • New README screenshots in the current look, made with made-up people. Both READMEs describe "Sign in as this person" for admins and mention CROSSFADE_BACKUP_ON_START.

Update notes

  • Database schema goes from 24 to 25 and migrates on start (clear fade colours). No configuration changes.

Validation

  • 299 Python tests passed, including new tests for working side by side and for when YouTube requests are tried again. Ruff passed.
  • Svelte check: 0 errors, 0 warnings. The production web build passed.
  • Not yet run against real services: the side-by-side sync and the new YouTube retry rules were tested with fake services only.

This is a pre-release. Publishing triggers the release workflow to test and build amd64/arm64 images for 0.3.0-rc.7 and testing.

v0.3.0-rc.6

v0.3.0-rc.6 Pre-release
Pre-release

Choose a tag to compare

@tg099 tg099 released this 15 Nov 15:34

A calmer look

  • New colours: sage and sand instead of red and blue, in the logo, the app icon, the favicon and the soft glow behind page titles. Light mode sits on a sand white, dark mode on a soft graphite instead of near black (still neutral).
  • Fade colours, status colours and settings icons are dusty instead of fully saturated. Stand-in covers (songs without artwork) use neighbouring hues instead of clashing ones. Existing fades move to the new shade of their colour automatically; custom colours stay as they are.
  • The brand glow stays behind each page title only, so lists and cards sit on calm ground. Type is lighter (titles 700, everything else 600 at most), section headings line up with the cards, labels lose their capitals, and buttons and covers cast neutral shadows instead of coloured glows. Spacing sits on a 4px grid.
  • The home screen shows the date as its title instead of a greeting. The week chart marks today in the accent colour.

Likes in the order they were liked

  • Liked songs now follow one timeline across services, ordered by when they were liked. Before, songs from one service landed as one block above the songs from another. Where a service gives no like date, the song gets a place between its neighbours. The earliest known date is kept per fade.
  • A fade with liked collections can put existing likes in order: Crossfade shows per collection how many songs are out of place, and moves the ones you pick by unliking and liking them again, one at a time.
  • Apple Music favourites are added one by one, a little more than a second apart, so they keep the source's order.

Removals

  • A song removed at a service other than Apple Music is passed on in the same sync: a second read a few seconds later confirms it. Only Apple Music keeps the 10-minute wait, because it briefly drops songs that were just added.

Admins can sign in as a user

  • An admin can open a user and pick "Sign in as this person" to set things up for them. The visit ends after two hours, and a banner brings the admin back with one tap. Password, MCP credentials and admin pages stay off limits during the visit. Admins can't sign in as other admins.

Update notes

  • Database schema goes from 21 to 24 and migrates on start: like dates (22), admin sign-in sessions (23), softer fade colours (24). No configuration changes.

Validation

  • 283 Python tests passed, including new tests for the colour migration. Ruff passed.
  • Svelte check: 0 errors, 0 warnings. The production web build passed.
  • The new look was checked on screenshots with fake data (light and dark, phone and desktop).

This is a pre-release. Publishing triggers the release workflow to test and build amd64/arm64 images for 0.3.0-rc.6 and testing.

v0.3.0-rc.10

v0.3.0-rc.10 Pre-release
Pre-release

Choose a tag to compare

@tg099 tg099 released this 15 Nov 22:26

When a service asks for a break

  • When a service says its quota is used up, asks Crossfade to wait longer than a minute, or keeps refusing after a short wait, Crossfade now gives it a break: nothing is sent to that service until the break is over, for every account on the instance. Before, every sync with that service failed and the next one asked again right away, which could make the block last longer.
  • If the service says how long to wait, Crossfade waits exactly that long (the old 60-second cap is gone). If it doesn't, each break in a row lasts longer (10 min, 30 min, 1 h, 3 h, 6 h). One request that goes through starts this over.
  • A fade that runs into a break now shows “Waiting for Spotify” with the time and reason instead of “Last sync failed”. It sends no error notification and carries on by itself once the break is over.
  • Songs that still need a search on a service on a break wait for the next sync instead of turning into open songs. Everything else in the sync goes ahead, and changes the break held up don't count as failed. A library add stops searching and adds what it already found.
  • Per service:
    • Spotify and TIDAL: a used-up quota or a long wait.
    • Apple Music: the library and the catalogue search take breaks separately. The search still falls back to iTunes Search first.
    • YouTube: a used-up Data API quota (Google sign-in) waits until just after midnight Pacific time and leaves the rest of YouTube Music alone. Repeated “too many requests” also leads to a break.
    • Deezer: quotas on both the gateway and the public API.
  • The health page lists every break (until when, why) and how many fades are waiting for one. The messages are shown in your language.

Unraid

  • Crossfade can be installed from the Apps tab (Community Applications). The template now lives in tg099/unraid-templates.
  • Public URL and secret key are optional there, so a new install works on the LAN right away. Without a key, Crossfade creates one in its data folder. Never change the key afterwards.

Update notes

  • No database or configuration changes. Breaks are kept in memory: after a restart the first request finds out again.

Validation

  • 325 Python tests passed, including new ones for the breaks of every service, waiting fades and the scheduler. Ruff passed.
  • Svelte check: 0 errors, 0 warnings. The production web build passed.
  • The waiting fades, the health page and the translated messages were checked with fake data in headless Chromium. Not yet tried against the real services: whether Spotify sends a wait time along with a used-up quota, and how TIDAL and Deezer report theirs.

This is a pre-release. Publishing triggers the release workflow to test and build amd64/arm64 images for 0.3.0-rc.10 and testing.

v0.3.0-rc.5

v0.3.0-rc.5 Pre-release
Pre-release

Choose a tag to compare

@tg099 tg099 released this 11 Nov 19:06

Removals at a sending collection

  • A song removed at a sending collection (for example an unliked song) only counts as removed once it has been missing for about 10 minutes, so a service that briefly leaves out a song can't delete it everywhere. The run that confirms it used to come only with the fade's next scheduled sync, and never for fades that only sync manually. Crossfade now runs the fade again on its own as soon as the removal can be confirmed.
  • While a removal waits, the fade page says that the song leaves the other collections in about 10 minutes. The run summary carries vanishing and recheck_at.

Song order

  • Liked songs are now added oldest first. Services list liked songs newest first, but adding can only append (or mark a song as liked now), so rebuilding a collection put it upside down: the newest like ended at the bottom of liked songs and at the top of a playlist. Now liked songs elsewhere show the newest on top, and a playlist reads oldest to newest like later additions do. Playlists used as a source keep their own order.
  • Collections that were already filled in the wrong order are not reordered.

Update notes

No schema or configuration changes.

Validation

  • 270 Python tests passed, including new tests for the liked-song order, the waiting removal and the scheduler recheck. Ruff passed.
  • Svelte check: 0 errors, 0 warnings. The production web build passed.
  • That liked songs come newest first is documented for TIDAL and known for two other services; it was not verified for every service.

This is a pre-release. Publishing triggers the release workflow to test and build amd64/arm64 images for 0.3.0-rc.5 and testing.

v0.3.0-rc.4

v0.3.0-rc.4 Pre-release
Pre-release

Choose a tag to compare

@tg099 tg099 released this 11 Nov 16:30

Song order

  • Songs are now added in the order of their source. A new receiving playlist is built like the playlist it copies, and songs added to the source later land behind the others, in their order. Before, songs arrived in an arbitrary order.
  • With several sending collections, the first one in the fade (that lists the song) decides. Existing playlists are not reordered.

Interface

  • Phone: the library's buttons now sit in the large title's row like on the other pages. Select, time travel and the library's collections are in a More menu there (only one button fits next to the title on a 375 px screen); while selecting, Done takes its place.
  • Desktop: the sidebar search field says Search instead of a hint too long for it, and text fields end in "…" instead of cutting text off.
  • Windows and Linux: the search shortcut reads Ctrl+K (Strg+K in German) instead of ⌘K, and scroll bars that take room are drawn thin and quiet instead of as grey bars on the glass.

Update notes

No schema or configuration changes.

Validation

  • 267 Python tests passed, including a new test for the song order. Ruff passed.
  • Svelte check: 0 errors, 0 warnings. The production web build passed.
  • Page headers and text fields were checked in a headless browser with synthetic data at 375, 393, 430, 900 and 1280 px, in German and English, with macOS and Windows simulated. Not checked on a real Windows machine.

This is a pre-release. Publishing triggers the release workflow to test and build amd64/arm64 images for 0.3.0-rc.4 and testing.

v0.3.0-rc.3

v0.3.0-rc.3 Pre-release
Pre-release

Choose a tag to compare

@tg099 tg099 released this 11 Nov 15:46

Deletions without asking

  • A fade can now pass on deletions without ever asking first: switch off Ask first in the fade editor. What you remove from one collection then disappears from the others too, even when many songs go at once.
  • The safety limit for fades that still ask is now more than 10 songs (or 20 %) by default, instead of 5.
  • Assistants can change the setting through prepare_fade_update (delete_confirm). Switching asking off counts as loosening the deletion limit and needs your approval.

Matching

  • When a service lists one recording on several releases (single, album, compilation, each with its own cover), the release the source is on now wins and a compilation comes last. Before, the first result won, so the right song could arrive with the wrong cover. Songs that were already added keep their release.

Fixes

  • Creating a fade now stores its deletion settings correctly. This only affected unreleased code after rc.2.

Update notes

Schema 21 is applied automatically on start (lines.delete_confirm, on for existing fades). No configuration changes are needed.

Validation

  • 266 Python tests passed. Ruff passed.
  • Svelte check: 0 errors, 0 warnings. The production web build passed.

This is a pre-release. Publishing triggers the release workflow to test and build amd64/arm64 images for 0.3.0-rc.3 and testing.

v0.3.0-rc.2

v0.3.0-rc.2 Pre-release
Pre-release

Choose a tag to compare

@tg099 tg099 released this 11 Nov 15:07

Sort songs into playlists inside fades

  • A receiving collection can carry a rule (moods, genres, tags, languages, energy, artists, or "rest" for everything no other rule takes) and then only gets the songs that fit, on every sync.
  • A sending collection such as your liked songs can let go of a song once it is listed in every rule collection it fits, so it works as an inbox. Songs without labels wait instead of landing in "rest". Nothing is removed from a playlist when rules or labels change, and many hand-offs at once are held for confirmation like deletions.
  • The fade editor gets a rule line per receiving collection, a hand-off switch for senders and a "Sort your likes" template. Fade details show each rule and how many songs wait for labels.

AI assistants act on their own, approvals only for deletions

  • Only proposals that delete wait for you: removing songs, duplicates or playlists, deleting a fade, exact restores, held deletions, switching deletion sync on or loosening its limit. Everything else the assistant applies itself. A proposal that would delete after something changed turns into an approval instead of running.
  • Approvals sit as cards at the top of the home page with a short gist, the preview, Allow and Discard. Links and notifications lead there, and a dot on Home points to it.
  • New tools: prepare_add_songs, prepare_fade_update, prepare_collection_role, fade_songs, fade_stats, activity, list_labels, clear_annotations, sorting_queue, plus unignore in prepare_issue_resolution. New fades created by an assistant start without deletion sync. Revoking all keys also cancels open proposals.
  • The AI assistants sheet is rebuilt in the app's usual style, with live updates instead of polling.

Fewer odd versions

  • Labels that used to read as "the same version" now mark another recording and are at most a suggestion: sped up/pitched/daycore, bass boosted, 8D, mashup/bootleg/VIP, re-imagined/revisited/from the vault, sessions, intro/interlude/skit/snippet/reprise, medley, commentary, more genre versions (hardstyle, drill, amapiano, drum and bass, dubstep, ambient …) and language versions.
  • A part number ("Pt. 2", "Part II", "Teil 3") is another song wherever it stands in the title.
  • An upload label keeps what it says about the recording: "(Official Live Video)" is live, "Song | Live at Wembley" is live.
  • A series upload ("Name | Episode | A vs B") keeps its whole title instead of matching another upload of the series. The same title and artist half a minute off on another album is a suggestion, not an automatic match. Only official music videos are used as a song's video.
  • In review, a suggestion is only preselected when it is convincingly the song: same title, same artist, about the same length. Otherwise you pick, and each suggestion shows its version.
  • Cached searches that did not find the exact version are redone. Songs already added in an odd version are left as they are.

Phone layout

  • Pages without a back button or actions start right below the status bar (with some room under a browser's own bar). Fades puts its buttons into the title row.
  • Searching moves the field to the top with a close button next to it, so the keyboard can't cover it.
  • A soft edge under the floating tab bar keeps content from peeking out below it. Pages leave room for the preview player.
  • A preview started inside a sheet (comparing versions in review) floats above the sheet instead of playing hidden behind it. Video previews stay visible and usable.
  • Version titles in review wrap to two lines, and the review actions take less height. The floating title stays readable over big text in dark mode.

Update notes

Schema 20 is applied automatically on start (fade rules and hand-off). No configuration changes are needed.

Validation

  • 263 Python tests passed, including new tests for odd versions and fade sorting.
  • Ruff passed. Svelte check: 0 errors, 0 warnings. The production web build passed.
  • The phone layout was checked in headless Chromium at phone size (browser tab and home-screen app), light and dark, with synthetic data and no external requests. iOS keyboard behaviour and real music services were not part of this check.

This is a pre-release. Publishing triggers the release workflow to test and build amd64/arm64 images for 0.3.0-rc.2 and testing.