From 802496461e8a4074a72cd3c30fc4163ccc253af3 Mon Sep 17 00:00:00 2001 From: helliott-redactbox Date: Sun, 31 May 2026 22:00:54 +0100 Subject: [PATCH 1/4] Fix MD040: add language to fenced code blocks in Lidarr docs --- lidarr/importing-existing-library.md | 4 ++-- lidarr/tips-and-tricks.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/lidarr/importing-existing-library.md b/lidarr/importing-existing-library.md index 4a22e318e..4b1434cf4 100644 --- a/lidarr/importing-existing-library.md +++ b/lidarr/importing-existing-library.md @@ -38,13 +38,13 @@ For the automated import to succeed, structure and tag your files before pointin The recommended structure is: -``` +```text /// ``` For example: -``` +```text /music/Bob Dylan/Blood on the Tracks/01 - Tangled Up in Blue.flac /music/Bob Dylan/Blood on the Tracks/02 - Simple Twist of Fate.flac ``` diff --git a/lidarr/tips-and-tricks.md b/lidarr/tips-and-tricks.md index e81081c10..73d89220c 100644 --- a/lidarr/tips-and-tricks.md +++ b/lidarr/tips-and-tricks.md @@ -22,7 +22,7 @@ Your download folder and music library root folder can't be the same location. M Keep two locations separate: -``` +```text /data/ downloads/ ← download client writes here music/ ← Lidarr root folder (your library) @@ -37,7 +37,7 @@ On import, Lidarr moves (or hardlinks) files from `downloads/` into `music/`. Th If you're running more than one download client — say, a Usenet client alongside a torrent client — give each its own subfolder under `downloads/` and set a matching category in Lidarr: -``` +```text /data/ downloads/ usenet/ ← SABnzbd / NZBGet category: "lidarr" From 7ba4815f6d28f96644b31e011107c1c534dace74 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Sun, 31 May 2026 21:01:40 +0000 Subject: [PATCH 2/4] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- lidarr/beets-integration.md | 2 +- lidarr/installation/reverse-proxy.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/lidarr/beets-integration.md b/lidarr/beets-integration.md index 124257886..8115f5f48 100644 --- a/lidarr/beets-integration.md +++ b/lidarr/beets-integration.md @@ -1,6 +1,6 @@ --- title: Lidarr and beets Integration -description: +description: published: true date: 2026-05-29T13:03:01.899Z tags: lidarr, beets diff --git a/lidarr/installation/reverse-proxy.md b/lidarr/installation/reverse-proxy.md index 8e2995976..6c0ef6140 100644 --- a/lidarr/installation/reverse-proxy.md +++ b/lidarr/installation/reverse-proxy.md @@ -1,9 +1,9 @@ --- title: Lidarr Reverse Proxy -description: +description: published: true date: 2026-04-26T16:31:38.023Z -tags: +tags: editor: markdown dateCreated: 2023-07-03T20:10:58.279Z --- From ac232f707c2533ff70081163e2d82b2a31b59934 Mon Sep 17 00:00:00 2001 From: helliott-redactbox Date: Sun, 31 May 2026 22:06:01 +0100 Subject: [PATCH 3/4] Fix MD047: add trailing newline to Lidarr docs --- lidarr/importing-existing-library.md | 2 +- lidarr/tips-and-tricks.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/lidarr/importing-existing-library.md b/lidarr/importing-existing-library.md index 4b1434cf4..163efd9f1 100644 --- a/lidarr/importing-existing-library.md +++ b/lidarr/importing-existing-library.md @@ -132,4 +132,4 @@ If a `Release` or `Release Artist` you expect is genuinely missing from MusicBra - [Concepts](/lidarr/concepts) — the `Release` and `Artist` model that drives import behavior - [Quick Start](/lidarr/quick-start-guide) — install and first download, if you don't already have a library - [FAQ](/lidarr/faq) — common import and metadata issues -- [Settings](/lidarr/settings) — detailed reference for every option referenced on thi \ No newline at end of file +- [Settings](/lidarr/settings) — detailed reference for every option referenced on thi diff --git a/lidarr/tips-and-tricks.md b/lidarr/tips-and-tricks.md index 73d89220c..fcda6d1fe 100644 --- a/lidarr/tips-and-tricks.md +++ b/lidarr/tips-and-tricks.md @@ -416,4 +416,4 @@ As long as the root folder paths in the backup are still valid on the destinatio - [Metadata Troubleshooting](/lidarr/metadata-troubleshooting) — when MusicBrainz data is missing or stale - [Import Troubleshooting](/lidarr/import-troubleshooting) — when downloads finish but don't import - [Troubleshooting](/lidarr/troubleshooting) — general runtime issues -- [TRaSH Guides](https://trash-guides.info/) — community recipes for media server setups \ No newline at end of file +- [TRaSH Guides](https://trash-guides.info/) — community recipes for media server setups From 4b31f65585e5ed6fe9f3abb3e7880cb6c43d522a Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Sun, 31 May 2026 21:06:17 +0000 Subject: [PATCH 4/4] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- lidarr/beets-integration.md | 2 +- lidarr/custom-scripts.md | 2 +- lidarr/faq.md | 34 +++++++++++++++--------------- lidarr/import-troubleshooting.md | 2 +- lidarr/metadata-troubleshooting.md | 4 ++-- lidarr/plugins.md | 7 +----- lidarr/settings.md | 7 ------ lidarr/troubleshooting.md | 1 - 8 files changed, 23 insertions(+), 36 deletions(-) diff --git a/lidarr/beets-integration.md b/lidarr/beets-integration.md index 8115f5f48..37ca17982 100644 --- a/lidarr/beets-integration.md +++ b/lidarr/beets-integration.md @@ -201,4 +201,4 @@ Two scenarios where the tools can conflict: - [Custom Scripts](/lidarr/custom-scripts): environment variables available to scripts and how to register them - [Settings: Metadata](/lidarr/settings#metadata): Write Tags setting and metadata consumer options - [beets documentation](https://beets.readthedocs.io/en/stable/) -- [beets installation guide](https://beets.readthedocs.io/en/stable/guides/installation.html) \ No newline at end of file +- [beets installation guide](https://beets.readthedocs.io/en/stable/guides/installation.html) diff --git a/lidarr/custom-scripts.md b/lidarr/custom-scripts.md index 64a915039..01a0c5229 100644 --- a/lidarr/custom-scripts.md +++ b/lidarr/custom-scripts.md @@ -398,4 +398,4 @@ curl -s -X POST "$WEBHOOK_URL" \ ## See also - [Settings: Connect](/lidarr/settings#connections): where you register scripts in the Lidarr UI -- [Beets Integration](/lidarr/beets-integration): using a custom script to invoke beets for tag enrichment after import \ No newline at end of file +- [Beets Integration](/lidarr/beets-integration): using a custom script to invoke beets for tag enrichment after import diff --git a/lidarr/faq.md b/lidarr/faq.md index 96c0b6fd7..a615d760c 100644 --- a/lidarr/faq.md +++ b/lidarr/faq.md @@ -18,7 +18,7 @@ If you don't find your question here, the most common landing spots are [Metadat ## Basics -### How does Lidarr work? +### How does Lidarr work Lidarr doesn't search for files that are missing or haven't met quality goals on a schedule. Instead, it queries your indexers and trackers at a steady cadence for *all* newly posted releases, compares that feed with your monitored albums, and downloads matches. At an RSS interval of 15–60 minutes, this amounts to 24–100 queries per day and covers a library of any size. It only catches releases going forward from when you added them, though. @@ -32,7 +32,7 @@ If Lidarr has been offline for a while, it pages back through each indexer to fi - Adding an artist or album with *Add and Search*. - Albums discovered during an artist metadata refresh (for example, a new album MusicBrainz adds after you've already added the artist). -### How do I update Lidarr? +### How do I update Lidarr Lidarr runs on one of three release branches. Pick one under **Settings → General → Updates** (show advanced): @@ -60,7 +60,7 @@ Docker tag-to-branch mapping: ## Finding music and MusicBrainz -### Why doesn't artist X show up in search? +### Why doesn't artist X show up in search A few common causes: @@ -85,7 +85,7 @@ Type any of these into the Lidarr search box. Lidarr tries to resolve the MBID a > **Release vs Release Group is the single most common mistake.** For albums, Lidarr wants the *Release Group* MBID, not a *Release* MBID. A release group is "the 2005 album"; a release is "the 2005 US CD pressing" or "the 2005 UK vinyl." If you paste a release MBID, the lookup will fail or return unexpected results. {.is-warning} -### Why does Lidarr only show studio albums, how do I find singles or EPs? +### Why does Lidarr only show studio albums, how do I find singles or EPs Lidarr filters what to track per artist through a **Metadata Profile** (Settings → Profiles → Metadata Profiles). The default profile includes only *Studio* albums, which is why singles, EPs, live albums, compilations, and remix collections don't appear on a fresh install. @@ -99,7 +99,7 @@ Adjust the profile rather than per-artist settings for a library-wide change: To apply a changed profile to existing artists, go to Library, select the artists, and use Edit → Metadata Profile. -### How can I find a MusicBrainz ID? +### How can I find a MusicBrainz ID 1. Search the artist, release group, or release on [MusicBrainz](https://musicbrainz.org/search). For albums, set the search type to **Release Group**. 2. Open the entity page. The MBID appears under the **Details** tab, or at the end of the URL (the UUID after the last slash). @@ -125,7 +125,7 @@ MusicBrainz doesn't have track lengths for this release (they appear as `???` on ## Importing and renaming -### I'm having trouble importing my artists, what could it be? +### I'm having trouble importing my artists, what could it be Imports fail in one of a few ways: @@ -134,7 +134,7 @@ Imports fail in one of a few ways: - **Lidarr can't read or write the folder.** The user account Lidarr runs as must have read and write access to both the download folder and the destination root folder. On Linux this is a UID/GID/permissions issue on a mount; on Windows it's Lidarr running as `LocalService` which can't reach a network share. See [Why can't Lidarr see my files on a remote server?](#why-cant-lidarr-see-my-files-on-a-remote-server) for the Windows case. - **Untagged or badly tagged files.** Files with generic filenames like `track01.mp3` and no tags give Lidarr nothing to match on. Run a tagger such as [MusicBrainz Picard](https://picard.musicbrainz.org/) or [Harmony](https://harmony.pulsewidth.org.uk/) before importing. See [Import Troubleshooting → Untagged or badly tagged files](/lidarr/import-troubleshooting#untagged-or-badly tagged-files). -### How can I rename my artist folders? +### How can I rename my artist folders {#rename-folders} @@ -161,13 +161,13 @@ If a rename appears to have happened in Lidarr but the folder name on disk hasn' > **Renaming outside Lidarr breaks the link between Lidarr's database and the files on disk.** Lidarr tracks files by path. If you rename a folder at the OS level, Lidarr treats the files as missing and may re-download them. Always rename through the Lidarr UI when possible. See [Renaming or moving files outside Lidarr](/lidarr/tips-and-tricks#renaming-moving-outside-lidarr) for a full explanation and recovery steps. {.is-warning} -### Why does Lidarr keep trying to rename the same folders? +### Why does Lidarr keep trying to rename the same folders Almost always a case-only rename on Windows. Windows filesystems treat `Artist` and `artist` as the same path. When Lidarr renames `ARTIST` to `Artist`, the operation reports success but the folder name on disk doesn't change. Lidarr then sees the folder still needs renaming, and the cycle continues. The fix is a two-step manual rename (`Artist` → `Artist_tmp` → `Artist`) so the filesystem actually commits the case change. On Linux and macOS this isn't an issue because those filesystems are case-sensitive. -### What audio formats does Lidarr support? +### What audio formats does Lidarr support Lidarr recognises the following file extensions: @@ -179,7 +179,7 @@ A subset of these formats have named quality definitions that quality profiles a If a file with a supported extension still isn't importing, the issue is typically match quality rather than format. See [Import Troubleshooting](/lidarr/import-troubleshooting). -### Can Lidarr prefer a specific pressing or format during import? +### Can Lidarr prefer a specific pressing or format during import {#can-lidarr-prefer-a-specific-pressing-or-format-during-import} @@ -199,7 +199,7 @@ An [open feature request](https://github.com/Lidarr/Lidarr/issues/186) to expose ## Lists and automation -### Why are list sync times so long and can I change it? +### Why are list sync times so long and can I change it List sync is intentionally slow. Lists are an *"add eventually"* tool, not an *"add now"* tool. The original sync cadence overwhelmed the upstream Servarr metadata server when users ran 10-minute list refreshes. @@ -212,7 +212,7 @@ If you need faster feedback for a specific list: > **Spotify import lists can trigger rate-limit errors (429s).** When Lidarr processes a Spotify list, it resolves Spotify IDs to MusicBrainz IDs via the metadata server cache. Any ID not in the cache requires an individual lookup, and enough of those in quick succession will hit the rate limit. To resolve this, wait it out, or add the missing Spotify album links to MusicBrainz so they get cached. See [Metadata Troubleshooting → Spotify import list rate limiting](/lidarr/metadata-troubleshooting#spotify-import-list-rate-limiting) for the full mechanism. {.is-info} -### Does Lidarr download lyrics, liner notes, or other extras? +### Does Lidarr download lyrics, liner notes, or other extras No, by design. Lidarr fetches the release audio files and tags/organises them. It doesn't bundle lyrics, liner notes, or other secondary files. @@ -223,7 +223,7 @@ For lyrics, use a tag-aware companion tool: These can run alongside Lidarr against the same library. Run them after Lidarr imports so they don't fight over file ownership. -### What about Custom Scripts / Custom Formats / post-processing? +### What about Custom Scripts / Custom Formats / post-processing Lidarr supports two distinct extension points: @@ -234,7 +234,7 @@ Custom Formats score releases. Custom Scripts respond to events. They don't over ## Integrations and external tools -### Does Lidarr support Deemix, slskd, or similar tools? +### Does Lidarr support Deemix, slskd, or similar tools Deemix and slskd are third-party tools. Deemix is a Deezer downloader. slskd is a Soulseek daemon. Historically there was no built-in way to integrate them with Lidarr, and users cobbled together import scripts. @@ -244,7 +244,7 @@ Common community plugins cover exactly this ground: Soulseek, Deezer, Tidal, and Running the plugin branch requires switching to `nightly` (see [How do I update Lidarr?](#how-do-i-update-lidarr)). Database schema migrations mean switching back to `master` or `develop` afterward requires restoring a pre-switch backup. -### Which download clients does Lidarr support? +### Which download clients does Lidarr support Usenet (NZB): SABnzbd, NZBGet, NZBVortex, Pneumatic, usenet blackhole. @@ -254,7 +254,7 @@ More clients are available via [Plugins](/lidarr/plugins) on the `nightly` branc For setup recipes, the [TRaSH Guides — Downloaders](https://trash-guides.info/Downloaders/) section covers the common clients in more depth than the Lidarr wiki does. -### Does Lidarr integrate with Plex, Emby, or Jellyfin? +### Does Lidarr integrate with Plex, Emby, or Jellyfin Not directly. Lidarr manages the library on disk. Media servers read that library and serve it to clients. The common pattern is to share the root folder: @@ -317,7 +317,7 @@ Common causes: - **Permissions.** If the Lidarr user can't write to the database file, SQLite can leave it in a corrupt state. This primarily affects new installs, migrated installs, or systems where the running user/group changed recently. - **mergerFS with `direct_io` enabled.** SQLite uses mmap, which mergerFS `direct_io` doesn't support. See [mergerFS docs](https://github.com/trapexit/mergerfs#plex-doesnt-work-with-mergerfs). Remove `direct_io` from the mergerFS options. -### I use Lidarr on a Mac and it stopped working. What happened? +### I use Lidarr on a Mac and it stopped working. What happened Most likely one of the databases is corrupt — a known macOS issue when the system sleeps or crashes during a database write. See [I am getting an error: Database disk image is malformed](#i-am-getting-an-error-database-disk-image-is-malformed) above for recovery. diff --git a/lidarr/import-troubleshooting.md b/lidarr/import-troubleshooting.md index 32028bee9..d7d4b5da3 100644 --- a/lidarr/import-troubleshooting.md +++ b/lidarr/import-troubleshooting.md @@ -196,4 +196,4 @@ For advanced readers who want to verify the rules or trace a specific rejection, - [Importing an Existing Library](/lidarr/importing-existing-library) — the fresh-install import walkthrough - [Metadata Troubleshooting](/lidarr/metadata-troubleshooting) — for problems where the release is missing or wrong at MusicBrainz - [FAQ](/lidarr/faq) — shorter answers that didn't fit this page -- [MusicBrainz Picard](https://picard.musicbrainz.org/) — tag files with MBIDs before importing for a dramatically higher succes \ No newline at end of file +- [MusicBrainz Picard](https://picard.musicbrainz.org/) — tag files with MBIDs before importing for a dramatically higher succes diff --git a/lidarr/metadata-troubleshooting.md b/lidarr/metadata-troubleshooting.md index 9cd5ebc9d..1700a82ab 100644 --- a/lidarr/metadata-troubleshooting.md +++ b/lidarr/metadata-troubleshooting.md @@ -194,7 +194,7 @@ To add a Spotify relationship on MusicBrainz, open the release and go to **Edit* > A 429 from Spotify doesn't mean anything is wrong with your Lidarr setup — it's a server-side rate limit on lookups. Checking Lidarr's logs at Debug level will show the 429 responses if you want to confirm that's the cause. {.is-info} -## Retry or wait? +## Retry or wait | Situation | Action | |---|---| @@ -213,4 +213,4 @@ To add a Spotify relationship on MusicBrainz, open the release and go to **Edit* - [FAQ](/lidarr/faq) — shorter answers and the operational questions that don't fit this page - [Harmony](https://harmony.pulsewidth.org.uk/) — recommended tool for importing releases into MusicBrainz - [MusicBrainz Userscripts](https://musicbrainz.org/doc/Guides/Userscripts) — browser userscripts for MusicBrainz editing (watch the album-type caveat above) -- [Servarr Discord](https://lidarr.audio/discord) — where cache-bust reque \ No newline at end of file +- [Servarr Discord](https://lidarr.audio/discord) — where cache-bust reque diff --git a/lidarr/plugins.md b/lidarr/plugins.md index bc4c778bf..9fb31cc9e 100644 --- a/lidarr/plugins.md +++ b/lidarr/plugins.md @@ -66,6 +66,7 @@ image: lscr.io/linuxserver/lidarr:nightly > Both plugins and this documentation are community-driven. No official recommendations exist. Each developer supports their own plugin. {.is-info} + ## jtstothard/UniqueSingles [UniqueSingles by jtstothard](https://github.com/jtstothard/lidarr-plugin-uniquesingles) @@ -185,7 +186,6 @@ To search, you must also add Slskd as an Indexer. Slskd is now available for both automatic and interactive searches. During Lidarr search operations you can view the slskd `/searches` as they occur and monitor `/downloads`. - ## TypNull/Tubifarry [Tubifarry by TypNull](https://github.com/TypNull/Tubifarry) is a *multi-feature* plugin that extends Lidarr's capabilities with these key functions: @@ -219,7 +219,6 @@ Slskd is now available for both automatic and interactive searches. During Lidar > See the [Tubifarry README](https://github.com/TypNull/Tubifarry) for advanced configuration, troubleshooting, and feature deep-dives. {.is-info} - ## TrevTV TrevTV develops specialized Lidarr plugins for direct music platform integration. @@ -257,7 +256,6 @@ TrevTV develops specialized Lidarr plugins for direct music platform integration - FFmpeg required for Tidal conversions - Qobuz authentication may require custom app IDs - ## ta264/deemix [Deemix plugin by ta264](https://github.com/ta264/Lidarr.Plugin.Deemix) @@ -266,9 +264,6 @@ This plugin enables Lidarr to search Deezer using Deemix. You must have a workin [Deemix](https://github.com/bambanah/deemix) - ## lucapolesel/Lidarr.Plugin.Slskd [Slskd (Soulseek) by lucapolesel](https://github.com/lucapolesel/Lidarr.Plugin.Slskd) - - diff --git a/lidarr/settings.md b/lidarr/settings.md index d5649186a..3a813e27b 100644 --- a/lidarr/settings.md +++ b/lidarr/settings.md @@ -126,7 +126,6 @@ Click **Add (+)** to add a root folder. The path must exist and Lidarr must have > Don't point a root folder at a cloud storage mount (Dropbox, OneDrive, Google Drive). Lidarr writes audio tags and metadata frequently; cloud storage APIs have rate limits that will cause failures. {.is-warning} - ## Metadata Profiles {#metadata-profiles} @@ -155,7 +154,6 @@ You can include or exclude secondary types (Compilation, Soundtrack, Spokenword, > MusicBrainz determines release types. If a release you expect to see is missing, check its entry on MusicBrainz: the type may be `Unknown`, which Lidarr can't filter on, or the primary type may be one you have unchecked in your profile. {.is-info} - ## Release Profiles {#release-profiles} @@ -176,7 +174,6 @@ Release profiles filter and score releases based on their titles. Use them to re > Release profiles apply at **grab/download time**: they filter and score releases from indexers before Lidarr sends anything to a download client. They have no effect on which MusicBrainz release (pressing, edition, format) Lidarr matches your already-downloaded files to during import. See [FAQ → Can Lidarr prefer a specific pressing or format during import?](/lidarr/faq#can-lidarr-prefer-a-specific-pressing-or-format-during-import) for the import side of this. {.is-info} - ## Custom Formats {#custom-formats-2} @@ -211,7 +208,6 @@ Two ways to test how Lidarr will parse a release name before committing to a pro **Via the Servarr Discord bot:** In the `#bot-spam` channel, run `/parser lidarr ` (for example, `/parser lidarr Artist.Album.2022.FLAC-GROUP`). The bot replies with the same parsed breakdown. Useful for quick spot-checks without opening the UI. - # Quality {#quality} @@ -230,7 +226,6 @@ For audio, size limits use **kilobits per second (kbps)**. Lidarr computes a bit > FLAC is lossless and doesn't have a consistent bitrate; its effective bitrate varies by content. The FLAC entry in quality definitions serves primarily as a file-size sanity check rather than strict bitrate enforcement. {.is-info} - # Download Clients {#download-clients} @@ -338,7 +333,6 @@ A mapping translates a remote path (as reported by the download client) to a loc > If both Lidarr and the download client are in Docker containers on the same host with matching volume mounts, a remote path mapping isn't needed. See [TRaSH's Remote Path Mapping guide](https://trash-guides.info/Radarr/Radarr-remote-path-mapping/) for diagnosis and setup. {.is-info} - # Connect {#connections} @@ -368,7 +362,6 @@ Click **Add (+)** and select a connection type. Most connections share these fie For **Custom Script** connections, see the [Custom Scripts](/lidarr/custom-scripts) page for the full list of environment variables available per event. - # Tags {#tags} diff --git a/lidarr/troubleshooting.md b/lidarr/troubleshooting.md index 65e40a090..59bc3faf0 100644 --- a/lidarr/troubleshooting.md +++ b/lidarr/troubleshooting.md @@ -420,7 +420,6 @@ In this test, look for obvious errors and run some simple checks. The trace log ![searches-indexers-and-trackers1.png](/assets/lidarr/searches-indexers-and-trackers1.png) ![searches-indexers-and-trackers2.png](/assets/lidarr/searches-indexers-and-trackers2.png) - ## Common Problems Below are some common problems.