lidarr-extended/
├── post-process.sh # runs after import
├── inject_lyrics.py
├── refresh_metadata.py
├── config.json # enables flags like "WriteBPM", "FetchKeys"
└── docker/Dockerfile # layered over hotio/lidarr
Are you looking for a specific script, feature, or the source of a Docker image named lidarr-extended? If you can provide the exact GitHub link or registry name, I can give you a precise content breakdown.
Unlocking the Full Potential of Your Music Library with Lidarr-Extended
Lidarr-Extended is a specialized Docker container (based on the linuxserver/lidarr develop branch) that adds advanced automation scripts and metadata enhancements to the standard Lidarr music manager. Unlike the base application, which primarily monitors torrent and Usenet indexers, Lidarr-Extended integrates with high-fidelity streaming platforms like Deezer and Tidal to automatically download lossless audio and music videos. Key Features of Lidarr-Extended
While Lidarr excels at organizing local files, Lidarr-Extended transforms it into a proactive discovery and acquisition tool:
Automated Streaming Downloads: It uses a script to check your "Wanted" list and automatically grabs missing tracks from Deezer or Tidal in formats including FLAC (lossless), MP3 (320kbps), and AAC.
Music Video Integration: It can automatically search for and download music videos associated with your artists (via MusicBrainz) in MKV or MP4 format, complete with thumbnails for Plex, Jellyfin, or Kodi.
Intelligent Discovery: The autoArtistAdder feature can automatically add related artists from streaming services to your library based on what you already listen to.
Advanced Tagging: Before importing files into Lidarr, the container can pre-match and tag files using Beets, add ReplayGain tags, and embed high-quality cover art.
Spotify Playlist Support: You can import Spotify playlists, which Lidarr-Extended then monitors and downloads automatically without manual intervention. Installation and Setup
Setting up Lidarr-Extended typically requires a Docker environment. For platforms like unRAID, users often add custom scripts to a standard LinuxServer container or use the dedicated RandomNinjaAtk image.
Deploy the Container: Use a Docker Compose file or unRAID template to map your /config, /music, and /downloads volumes.
Configure extended.conf: This is the core configuration file located in your appdata folder. Here, you must provide your Deezer ARL token or Tidal credentials to enable streaming downloads.
Adjust Script Settings: You can toggle specific features like autoArtistAdder or the music video script by editing the configuration file before restarting the container.
Set Quality Profiles: In the Lidarr Web UI, configure your quality cutoffs. The extended script will only trigger for items that are monitored and haven't met your desired quality. Lidarr-Extended vs. Standard Lidarr RandomNinjaAtk/docker-lidarr-extended - GitHub
Lidarr-Extended is a community-driven enhancement for the standard Lidarr application, typically delivered as a Docker container. It integrates additional automation scripts—primarily those from the RandomNinjaAtk/arr-scripts repository—to significantly expand Lidarr's native capabilities. Key Features
Automated Content Acquisition: Automatically searches for and downloads music from online sources like Tidal and Deezer.
Extended Metadata & Lyrics: It can automatically fetch and embed LRC lyrics and high-quality metadata from Gazelle-based trackers.
Discovery Tools: Features an Auto Artist Adder that finds and adds related artists based on your existing library, though users are cautioned to limit this to prevent endless library expansion.
Video Support: Includes scripts to automatically download music videos for artists in your library from sources like IMVDB.
Pre-Processing: Downloads are often tagged and paired with cover art before Lidarr even "sees" them for final import. Implementation Details
Base Image: Usually built upon the LinuxServer.io Lidarr develop branch.
Configuration: Requires an extended.conf file where users must provide tokens (such as a Deezer Token) and toggle specific features like video downloading. Web Interface: Typically accessible on port 8686. RandomNinjaAtk *arr-extended docker containers
Once upon a time in the quiet, glowing corner of a home server rack, there lived a software manager named Lidarr. Lidarr was diligent, spending its days organizing vast libraries of music and scouting the digital horizon for new tracks from MusicBrainz. But Lidarr was also a dreamer; it wanted to do more than just search—it wanted to discover. The Transformation
One day, Lidarr met a powerful collection of scripts known as Lidarr-extended. This wasn't just a minor update; it was like Lidarr had found a magical map. By integrating with high-quality streaming sources like Tidal and Deezer, Lidarr-extended gained the ability to see beyond the user’s current library. lidarr-extended
It began to act like an expert digital curator. If the user liked a specific rock band, Lidarr-extended would whisper to the server, "If they like them, they’ll love these five related artists," and automatically add them to the "monitored" list. It even had a clever rule to prevent "endless loops," ensuring the library didn't grow into an uncontrollable digital jungle. The Quest for Quality
But the story didn't end with discovery. Lidarr-extended was a bit of a perfectionist. While standard Lidarr was content with what it could find on trackers, the "extended" version reached out to Tidarr and other specialized tools to pull down Master-quality FLAC files. It worked tirelessly to:
Auto-Add Artists: Scouring Tidal for related musicians based on the user's existing taste.
Manage High-Fidelity Streams: Triggering downloads of lossless audio that would make any audiophile weep with joy.
Sync with Ease: Using shared volumes in Docker containers to ensure the music moved seamlessly from the cloud to the hard drive. The Modern Legend
Today, users often call it "Lidarr on Steroids". It sits as a crown jewel in many self-hosted setups, tucked away in dashboards alongside other "arr" legends like Sonarr and Radarr. While it occasionally runs into a "connection refused" gremlin or a "wget" hiccup, its community of tech-wizards on GitHub always manages to find the fix.
And so, the music never stops. Thanks to Lidarr-extended, the server isn't just a storage box anymore—it's a living, breathing concert hall that knows what you want to hear before you even do. arr-scripts/lidarr/extended.conf at main - GitHub
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. lidarr-extended/ ├── post-process
Lidarr Extended is a specialized Docker container project that enhances the standard Lidarr music manager by integrating automated downloading and post-processing scripts. It is developed and maintained by RandomNinjaAtk and is designed for users who want to automate music acquisition from sources beyond standard Usenet and BitTorrent indexers. Core Functionality & Features
The container is based on the LinuxServer.io Lidarr develop branch but adds several powerful tools:
Automated Downloading: It automatically monitors Lidarr’s "Missing" and "Cutoff Unmet" album lists and downloads them using third-party clients for services like Tidal.
Media Quality & Conversion: Supports FLAC (lossless), MP3 (320/128), and AAC (320/96) formats. It can automatically convert FLAC files to your preferred bitrate before importing them into your library.
Advanced Tagging: Uses Beets to pre-match and tag files with high-quality metadata and cover art. It can also add ReplayGain tags and embedded lyrics to tracks.
Artist Discovery: Features an automated script that can add top artists from online services or similar artists based on your current library.
Music Videos: Includes functionality to download music videos for the artists in your collection. Technical Setup Base Image: LinuxServer.io Lidarr (develop branch).
Configuration: Settings are managed via an extended.conf file, which controls script intervals (e.g., checking for new audio every 15 minutes) and file paths.
Architecture: It does not modify Lidarr’s core code; instead, it interacts with Lidarr via its public API to push updates and notify it of new imports. Status & Alternatives
Support: It is a community-driven project and is not officially supported by the Lidarr team. Troubleshooting typically happens on the RandomNinjaAtk GitHub Discussions or community forums like Unraid.
Migration: The developer has recently transitioned from the "extended" Docker containers toward a more modular arr-scripts format, which offers similar functionality as standalone scripts.
Comparison: Similar "modded" containers include Lidarr-on-Steroids (LoS), which focuses on Deemix integration for downloads.
The primary difference in this version is how it handles downloads and metadata.
The ultimate goal of Lidarr-Extended is a seamless Plex experience. However, Plex hates folder structures that mix "Albums" and "Singles" in the same root folder.
The Lidarr-Extended Strategy:
Because Lidarr-Extended writes excellent ID3 tags (including RELEASETYPE), Plexamp will display "Singles – Artist Name" as a separate entity, keeping your album view clean.
Look for repositories named:
Once the container is running, access the UI at http://localhost:8686.
Use Lidarr Extended if:
Skip it if:
Would you like a ready-to-use custom format JSON collection for live/remastered/bootleg handling, or a sample post-processing script for Lidarr?
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. Are you looking for a specific script, feature,
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 —
Lidarr-extended is a specialized Docker container (typically based on the linuxserver/lidarr image) that adds scripts and extra tools to the standard Lidarr application. Its primary purpose is to automate the downloading of high-quality music—often in FLAC format—from streaming services like Deezer or Tidal. Key Features & Capabilities
Alternative Download Sources: Unlike standard Lidarr, which relies on Usenet or Torrents, Lidarr-extended uses scripts to pull music directly from streaming platforms.
Automatic Tagging: It includes Beets, a powerful music library management tool, to automatically tag and organize music upon import.
Lyrics & Metadata: It can embed .LRC lyrics directly into files and gather additional metadata that standard indexers might miss.
Supplementary Nature: It is designed to work alongside your existing Lidarr setup. It acts as a "gap filler" for albums your usual indexers can't find. User Experience & Pros/Cons
Lidarr-extended is an automated script and Docker container suite designed to expand the capabilities of the standard
music manager. While the default Lidarr is primarily built for managing existing libraries and searching Usenet/BitTorrent indexers, Lidarr-extended introduces the ability to download high-quality audio directly from streaming services like and manages music video acquisition. Key Features of Lidarr-extended
The "extended" version functions as a middleman that interprets Lidarr's "missing" or "cutoff" lists to trigger downloads through third-party scripts. Streaming Downloads : Supports direct downloading from
in various formats including FLAC (lossless), MP3 (320/128), and AAC. Music Video Automation
: Automatically searches for and downloads music videos for artists in your Lidarr library, saving them in MKV format with metadata for , Kodi, or Jellyfin. Library Expansion
: Can automatically discover and add new artists to your library based on "Related Artists" from online streaming services. Enhanced Metadata : Pre-matches and tags files using Beets, adds ReplayGain
tags, and ensures cover art is included before Lidarr even sees the files. Post-Processing
: Can convert FLAC files to preferred bitrates/formats before they are imported into Lidarr. Core Functionality & Configuration
Lidarr-extended operates differently than standard plugins; it typically runs as a script that monitors your Lidarr database. Lidarr (Standard) Lidarr-extended Primary Sources Usenet & BitTorrent Tidal, Deezer, & YouTube Video Support No native automation Automated Music Video downloads Artist Discovery Manual or RSS Automated "Related Artist" adding Download Client QBittorrent, Sabnzbd, etc. Internal scripts (Deezer-dl, etc.) Installation Overview Most users deploy Lidarr-extended using . The setup requires: RandomNinjaAtk *arr-extended docker containers
Since "Lidarr Extended" is not an official product from the Lidarr team, here is the most likely content you are referring to, based on existing GitHub projects and community scripts:
While standard Lidarr has webhooks, Lidarr-Extended adds granular triggers: