General feedback

[rhyst]

Hello,

I've just got some general feedback from trying to use SoulSync on my media collection. It has worked amazingly well but I did find myself needing to use Claude to understand the workflows and work around a few maybe bugs?

Overall thanks for soulsync! I had a very messy library that I have no idea how I would have sorted.

SoulSync feedback

Maybe bugs

• Manual match ignored for "wing it" tracks. When discovery can't identify a track it stores a synthetic wing_it_… id, and sync looks manual matches up by that id rather than the source (Spotify) id, so a manual match never applies. Log: Manual match … cannot apply.
• Download review hides waiting items. The Import page's "Needs attention" filter hides waiting rows while auto-import is running. Folders with an old partial import row never get re-processed, so they stay hidden until the row is reset.
• Partial import shown as imported. Auto-import status partial maps to "imported" in the inbox, even when most files are still sitting in Staging.
• Import matcher mislabels covers. On Give Up (Deluxe) disc 2, the Shins and Iron & Wine covers were titled as the Postal Service originals ("… - Remastered").
• Import matched only 1 of 12 files. A Hard Day's Night imported one track into a stray Disc 1/ folder and left the rest in Staging, with no obvious warning.
• AcoustID Retag rewrites album artist. Retagging a compilation track sets album artist to the track artist, which splits compilations like Trail Songs apart.
• Empty Folder Cleaner misses release junk. .sfv and .srr files don't count as disposable, so folders holding only nfo/sfv/m3u never get cleaned.
• Quality profile flags non-MP3 at any bitrate. A profile with only MP3 targets flags 320 kbps m4a and FLAC files as "below profile" (I think I want this behaviour but maybe terminology is confusing)
• Partial scan reported as "completed". Quality Upgrade Finder scanned 3,008 of ~8,050 tracks and the run shows completed, with no hint it stopped early (probably a Spotify rate limit). It also keeps no record of tracks that passed, so every rerun re-checks them.
• Correct version rejected. The wishlist wanted Teardrop (A Still Heart, which is the stripped album), but "expected original, file is acoustic" verification rejected the right file, so it retries forever.

Confusing

• Relocate (AcoustID fix) moves files out of the library into Staging. Easy to trigger by accident, and hard to trace afterwards.
• "Transfer is my permanent library" is off by default, so the weekly Deep Scan can move unrecognised library files to Staging.
• "Sync" means SoulSync → Navidrome. Spotify → SoulSync is "Refresh". Nothing in the UI makes that split obvious.
• "Discovery" means two unrelated things: identifying playlist tracks, and the Discover recommendations page.
• Playlist sync defaults to replace. It silently overwrites Navidrome edits and creates a "… Backup" playlist on every sync, by default.
• Playlists are matched by name. Renaming one in Navidrome makes the next sync create a duplicate.
• Mirror status is stale. The "missing / in library" flags only update on sync, so a new manual match still shows as missing.
• Two match tools overlap: Manual Library Match (link only) and Find & Add (link and add to the playlist).
• "Unscheduled" badge ignores a Playlist Pipeline set to all. It only reflects Auto-Sync per-playlist lanes.
• "Transfer" terminology. One folder has three names: "Transfer" (toggle, docs), "Output Path" (settings field) and soulseek.transfer_path (config key, under Soulseek even though every source uses it). The Getting Started guide says it must be the media server's library folder, which is exactly when "Transfer is my permanent library" is needed, yet that toggle defaults off.
• Too many matching UIs, unclear direction. There's discovery Fix, the Wing It Pool, Manual Library Match, Server Playlists Find & Add, the Import matcher, and AcoustID retag/relocate. It's often unclear whether a screen matches a source track to catalogue metadata, catalogue metadata to a library file, or a file to a release, and which of them persist or affect sync.
• Wing It ≠ missing. Wing It means "not found in the metadata catalogue", not "not in my library": 62 of my 68 Wing It tracks were in the library. Missing Wing It tracks are silently never wishlisted (wishlist.wing_it_guesses is off by default), and "Server Playlists → missing" mixes both kinds.
• Playlist Explorer requires 50% discovered, a UI-only gate: the backend works without discovery.
• Library Maintenance vs Automations are separate schedulers, and some maintenance jobs auto-fix (Reorganize moves files) without review.
• Import rows are named by guessed album tag, not folder name. For example, the Beatles FLACs appeared as "Sgt. Pepper".
• Navidrome's Subsonic path is synthetic unless the SoulSync player has "Report Real Path" enabled. This broke every file-based repair job.

Suggestions

• One incoming-review queue. Downloads (quarantine, unverified) and Staging imports feed a single review UI, whatever the source.
• Merge Library Maintenance into Automations. Maintenance jobs become system automations, with the same scheduling, run history and enable/disable controls.
• One place to map playlist tracks to library tracks. A single view of every desired track from every playlist or wishlist, showing its library match (or none), with one manual-match action that sync always honours.

[Nezreka]

You're right on all counts. Going to have this ready by 3.5.0

[splitsec2]

Three additions from my install (3.4.9, Docker, two profiles).

The scheduler split has a second problem besides the ones listed. Scheduled automations owned by a non-admin profile are never re-armed after a restart: engine start() loads get_automations() with its default profile_id=1, so only admin and system rows get timers. A second profile's 6-hourly Playlist Pipeline here ran once on creation day and then sat frozen for ten days across four restarts. Filed as #1428 with the details. If Library Maintenance jobs become automations in 3.5.0, that filter is worth fixing first so the merged jobs don't inherit it.

The retry-forever shape also happens with "No matching track found". Three tracks from a Deezer-sourced album have been retrying since September 21 on my install. A retry cap or a parked state would cover both that and the wrong-version case above.

And thanks for the transfer_is_permanent note. Mine was still false with the transfer path pointed at the media server library, which is exactly the setup the Getting Started guide describes. I would have found out via the weekly Deep Scan.

[Nezreka]

I believe I have addressed everything in this discussion on the 3.5.0 release. Let me know