Lidarr-Extended 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 Unlike the standard Lidarr, the extended version focuses on automation and high-fidelity sourcing: Downloader Integration : Automatically triggers downloads from streaming services (Deezer, Tidal, etc.) to fill gaps in your library. Spotify/Tidal Sync : Syncs your "Liked" tracks or specific playlists directly into Lidarr so they are automatically tracked and downloaded. Advanced Metadata : Fetches lyrics, high-resolution covers, and artist biographies that the standard version often misses. Automatic Organizing : Re-tags and moves files based on your specific quality profiles and folder structures. 2. Setup Requirements To use Lidarr-Extended effectively, you typically need the following: Docker : It is most commonly run as a Docker container. Arl / Cookies : For downloading from Deezer or Tidal, you often need a "User Token" (Arl) or valid session cookies from those platforms. Streaming Accounts : A free or premium account (depending on the source) is required to pull track data and audio streams. 3. Installation Steps The most "solid" way to install it today is via the LinuxServer.io container mod, as it integrates directly with the popular Lidarr Docker image . Deploy Lidarr : Start with a standard LinuxServer Lidarr container . Add the Mod : Set the environment variable DOCKER_MODS=ghcr.io/randomninjaatk/lidarr-extended:latest . Configure Scripts : Once the container restarts, a new directory (usually /config/extended ) will appear. You will need to edit the extended.conf file to add your API keys or session tokens for Spotify/Tidal/Deezer. Set Quality Profiles : In the Lidarr UI, ensure your quality profiles match the downloads you expect (e.g., FLAC vs. 320kbps). 4. Recommended Workflows Self-Hosted "Spotify" : Many users pair Lidarr-Extended with Plexamp or Navidrome to create a personal streaming service that feels like Spotify but uses their own high-quality files. Library Cleanup : Use it to replace lower-quality MP3s with FLAC versions automatically as they become available on streaming platforms.
Report: Lidarr-Extended Executive Summary Lidarr-Extended is a third-party, community-developed custom script designed to augment the functionality of Lidarr , a music collection manager for Usenet and BitTorrent users. While standard Lidarr excels at monitoring and managing a library of known artists, it often struggles with music that is not indexed in its metadata databases (MusicBrainz) or finding specific rare tracks. Lidarr-Extended addresses these gaps by acting as a sophisticated search engine wrapper. It automates the process of finding downloads for ignored or missing artists, filling metadata gaps, and acquiring specific tracks that the base application cannot handle.
1. Purpose and Functionality The primary purpose of Lidarr-Extended is to bypass the strict metadata dependencies of the standard Lidarr application. Standard Lidarr requires an artist to exist in MusicBrainz to be tracked. Lidarr-Extended removes this limitation, allowing users to download music based on file availability rather than strict database matching. Core Features:
Unmonitored Artist Search: It can search for and download music from artists that are currently unmonitored or not fully indexed within Lidarr. Missing Track Search: It specifically targets tracks listed as "missing" in the Lidarr database, performing deeper searches than the native "Search Monitored" function. Metadata Filling: It attempts to bridge the gap between the file found and the metadata required by Lidarr, tagging files appropriately to ensure they are imported correctly. Custom Search Engines: It integrates with various search APIs and indexers (often beyond what Lidarr natively supports) to locate rare files.
2. Technical Architecture Lidarr-Extended is typically distributed as a Bash script (or a Docker container wrapping this script).
Deployment: It is most commonly deployed via Docker, often bundled into popular multi-container images (such as hotio/lidarr-extended or similar community forks). Interaction: It interacts with the Lidarr API to query the database for missing tracks and to trigger downloads. External Tools: It relies heavily on external command-line tools like beets or ffmpeg for audio tagging and conversion, and youtube-dl / yt-dlp for acquiring content if configured.
3. Comparison: Standard Lidarr vs. Lidarr-Extended | Feature | Standard Lidarr | Lidarr-Extended | | :--- | :--- | :--- | | Primary Constraint | Strict adherence to MusicBrainz metadata. | Flexible; relies on file availability and search results. | | Artist Management | Must add artist to database to download. | Can download for unmonitored or missing artists. | | Search Depth | Relies on configured Indexers/Prowlarr. | Uses custom search scripts and additional APIs. | | Resource Usage | Moderate (Standard .NET application). | Higher (requires periodic intensive scripting and API calls). | | Stability | High (Official release cycle). | Variable (Dependent on script maintenance and API changes). | 4. Benefits
Completeness: Users with large, niche, or legacy libraries often find that standard Lidarr misses a significant portion of their collection. Lidarr-Extended significantly increases the "fill rate" of missing albums. Automation: It removes the need for manual searching on soulseek or web-based download sites for rare tracks. Integration: It works within the existing Lidarr folder structure, ensuring that files are processed and renamed according to the user's existing naming conventions.
5. Drawbacks and Risks
Metadata Mismatches: Because it is less strict about MusicBrainz IDs, there is a higher risk of mis-tagging (e.g., downloading a "Greatest Hits" version of a song when the original album version was required, or misidentifying an artist with a common name). Resource Intensity: The script runs periodic background scans that can be CPU and I/O intensive, particularly on large libraries. Maintenance: Being a community script, updates are sporadic. If music APIs change their endpoints, the script may break until a maintainer patches it. Support: It is not supported by the official Lidarr development team. Users encountering issues are often directed to Discord communities or GitHub repositories rather than official forums.
6. Conclusion Lidarr-Extended is a powerful "power-user" tool designed for audiophiles and collectors who prioritize library completion over strict metadata purity. While it introduces complexity and potential tagging errors, it fills a critical void in the Lidarr ecosystem by solving the "missing artist/track" problem for obscure or unindexed music. Recommendation: It is highly recommended for advanced users with large libraries of rare or non-mainstream music who are comfortable troubleshooting Docker containers and manual tagging corrections. Users with standard libraries of popular music likely do not need the additional overhead.
Lidarr-extended is a specialized Docker image that integrates the standard music management application with a powerful set of "Extended Scripts" to fully automate the music discovery and downloading process. While standard Lidarr typically relies on torrents and Usenet, the "Extended" version—largely developed by RandomNinjaAtk on GitHub —uses these scripts to fetch music directly from online streaming sources like Core Features Fully Automated Downloads : It automates the process of finding and downloading missing tracks or albums from your Lidarr "Wanted" list using online sources. Source Integration : Specifically designed to work with tools like (for Deezer) to grab high-quality FLAC or MP3 files. Playlist Syncing : Allows users to import and sync playlists from services like directly into their local library. Music Organization : Like standard Lidarr, it automatically sorts, renames, and moves your music into media servers like Key Technical Aspects Base Image : Built on the stable LinuxServer.io Lidarr image, ensuring compatibility and regular updates. Setup Requirements : Users typically need to provide an ARL (Authentication Token) from a service like Deezer to allow the scripts to access and download content. Configuration : Managed via Docker parameters such as (to target specific Lidarr lists) and Concurrency (to set the number of simultaneous downloads). Common Use Cases The "Spotify Experience" : Many users use it to recreate a streaming-like experience on their own server by combining Lidarr-extended with a player like or Navidrome. Filling Gaps : It is highly effective for finding niche or rare albums that are often unavailable or unseeded on traditional trackers. Docker Compose snippet to see how to deploy Lidarr-extended on your server? RandomNinjaAtk/docker-lidarr-extended - GitHub 12 Jul 2023 —