Skip to content

RFC: Lidarr — Music Quality Upgrades

Status: Draft Date: 2026-04-25

Problem

Yubal downloads from YouTube Music in lossy formats (opus/m4a at ~256kbps). There's no automated way to find and replace these with lossless FLAC versions.

Proposal

Deploy Lidarr — the Sonarr equivalent for music:

  • Scans existing library, matches albums via MusicBrainz
  • Quality profiles: prefer FLAC over lossy, auto-upgrade when found
  • Searches indexers for better quality versions
  • Automatically replaces lossy files with FLAC

Infrastructure

Component Value
LXC 113 (mediabot) — colocate with existing *arr stack
Indexers Jackett + Prowlarr (already deployed)
Music path /mnt/all-might/music (bind mount, same as Navidrome)
Download client qBittorrent on LXC 113

Workflow

Yubal downloads from YouTube Music (fast, lossy)
  -> Lidarr monitors library
  -> Finds FLAC on indexers
  -> Replaces lossy with lossless
  -> Navidrome rescans (every 15min)

Dependencies

  • Navidrome + Yubal stack stable and populated first
  • Bind mount from /mnt/all-might/music added to LXC 113

Open Questions

  1. Should Lidarr manage the entire music library or only upgrade existing files?
  2. Root folder conflict — Lidarr wants to own the music directory structure, but Yubal also writes to it. Need to test coexistence.
  3. Metadata conflicts — Lidarr may re-tag files that Yubal already tagged. Which source of truth wins?