Lidarr-extended ✯ | Official |

To help tailor this setup for your specific home server environment, tell me:

: Fetches lyrics, high-resolution covers, and artist biographies that the standard version often misses.

in various formats including FLAC (lossless), MP3 (320/128), and AAC. Music Video Automation

: It can automatically add artists to your library that are related to your existing artists using data from Quality Management

To keep your automated music library running flawlessly, implement these routine practices: Use MusicBrainz IDs lidarr-extended

It automatically finds, matches, and downloads high-definition music videos for your tracks using sources like YouTube.

However, the intended use case for the "Extended" features is .

Plex supports local music videos, but they must follow strict naming conventions. Lidarr-Extended handles this automatically by naming the video file exactly like the audio track and appending -video to the end (e.g., SongName-video.mp4 ). To view them: Go to your Plex Music Library settings. Enable in the agents tab.

Ensure your music videos are named with the -video suffix if you want them to appear right next to the tracks. For Jellyfin Users Turn on the library type. To help tailor this setup for your specific

: Can convert lossless FLAC files to preferred lossy formats (like MP3 or AAC) and specific bitrates before Lidarr receives them.

is an enhanced version of the standard Lidarr application. While standard Lidarr is excellent for standard releases, it often struggles with specific music formats like individual tracks, YouTube rips, or specialized torrent formats (like those converted from deezer/tidal).

While standard Lidarr typically relies on torrents and Usenet, the "Extended" version—largely developed by RandomNinjaAtk on GitHub

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" However, the intended use case for the "Extended"

: Ensure Lidarr-Extended is set to use the Artist Name/Album Title/Track Number - Track Title naming convention.

Setting up lidarr-extended is most commonly done via Docker. Because the container includes additional scripts, the volume mapping is slightly more complex than the standard version. According to the Unraid App List , key paths include: : Stores the core database and application settings. /music : The destination for your organized music library.

Ensure your music paths match exactly between Lidarr and your downstream media servers so metadata syncs flawlessly. Optimizing Your Media Server for Lidarr-Extended

User feedback has been a mix of high praise for what the tool enables, coupled with practical considerations.