Lidarr-extended Page

Lidarr-Extended represents a fascinating evolution in music automation, bridging the gap between traditional media management and modern streaming service integration. While the original Docker container may be deprecated, the project lives on through modular scripts that continue to serve a dedicated user base.

Because this is a third-party fork, it is not officially supported by the core Lidarr development team. Users encountering issues with specific extended features (like script errors or downloader integration) should refer to the GitHub Wiki or community discussions on platforms like Reddit. RandomNinjaAtk/docker-lidarr-extended - GitHub

The Ultimate Guide to Lidarr-Extended: Automate and Enhance Your Music Library

Contribute scripts, profiles, or translations. Report issues on GitHub. This project is not affiliated with the official Lidarr team.

To fully enjoy your new automated media empire, your media server needs to understand Lidarr’s output. lidarr-extended

Example post-process script snippet (bash):

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.

Which (Plex, Jellyfin, etc.) do you use to stream your music?

Lidarr-Extended relies heavily on metadata processing. Go to . This project is not affiliated with the official Lidarr team

is a collection of scripts and a modified Docker container (maintained by RandomNinjaAtk ) that enhances the base music management tool by adding high-quality metadata and automated downloading from sources like Tidal, Deezer, and Spotify . 1. Key Features

is not a replacement for Lidarr ; rather, it is a wrapper around the Linuxserver.io Lidarr container (specifically the develop tag). It enhances the base Lidarr application by injecting additional scripts and tools into the container.

The most efficient way to deploy Lidarr-Extended is through Docker. This ensures all dependencies—like Python, FFmpeg, and yt-dlp—are pre-configured and will not conflict with your host operating system. Prerequisites A running Docker environment. Docker Compose installed.

After starting the container and allowing Lidarr to fully load, perform a second restart. Due to how the container copies and executes scripts, a second restart is required for new scripts to take effect. For future updates, you'll need to restart twice as well—once to load the application, again to activate new scripts. How It Works

The extended script automates several tasks that the base Lidarr application does not handle natively: Automatic Artist Discovery

Here’s a concise, informative text for based on the typical purpose of such a project (an enhanced or modified version of the Lidarr music downloader/organizer). If you need it tailored differently (e.g., GitHub README, Reddit post, feature list), just let me know.

The background Queue Cleaner script acts as a digital housekeeper. It automatically drops downloads that have stalled out or failed, enabling Lidarr to immediately initiate a secondary search for an alternate file. Comparative Overview: Standard vs. Extended Standard Lidarr Lidarr-Extended Usenet / Torrents Direct CDN Streaming APIs (Tidal, Deezer) Music Video Support Fully Automated (MKV + NFO metadata extraction) Advanced Tagging Integrated Beets Pipeline & ReplayGain Self-Cleaning Queue Manual intervention required Automated Queue & Unmapped Folder Cleaners Discovery Logic Import Lists only Automated Deezer Top Charts & Related Artist Scrapers Configuration and Setup Guide RandomNinjaAtk/docker-lidarr-extended - GitHub

: Once the download and tagging are complete, the script notifies Lidarr to import the files into the main library. How It Works