Lidarr-extended |best|

It notifies Plex/Jellyfin to scan individual artist folders immediately after import, reducing scanning time. Lidarr vs. Lidarr-Extended: What’s the Difference? Standard Lidarr Lidarr-Extended Automation Level High (search/download) Extreme (search/download/convert/tag) Music Videos No native support Fully automated downloads FLAC Handling Excellent (with auto-conversion) Tagging Advanced (Beets integration) Setup Complexity How to Install and Set Up Lidarr-Extended

Lidarr-Extended is best installed via Docker. The most popular method is using the RandomNinjaAtk docker-lidarr-extended image. 1. Prerequisites Docker and Docker Compose installed. A media library structure. lidarr-extended

Most users prefer the Hotio or LinuxServer.io-based extended images. A sample docker-compose.yml snippet: It notifies Plex/Jellyfin to scan individual artist folders

Lidarr-Extended is typically distributed via GitHub (look for the lidarr-extended or Lidarr-Extended-Release repositories). It runs on the same infrastructure as standard Lidarr – Docker, Windows, Linux, or macOS. Prerequisites Docker and Docker Compose installed

: Some users report that while the output quality is high, the scanning and searching process can be slower than the standard version.

Instead of a separate UI, this project relies on a configuration file called extended.conf located in your /config directory. Users typically configure this by adding their own tokens (e.g., a Deezer ARL or Tidal token) to unlock specific download sources.