Lidarr-extended
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.
Standard Lidarr tags files using its internal database. Lidarr-Extended can leverage beets (a music library manager) to fetch high-quality metadata from MusicBrainz and clean up file tags automatically.
A typical "Extended" script or fork adds functionality beyond basic Lidarr:
Custom Post-Processing
Quality of Life Enhancements
Integration with Other Tools
Search Improvements
Related search suggestions: (functions.RelatedSearchTerms) "suggestions":["suggestion":"Lidarr Extended features list","score":0.9,"suggestion":"Lidarr vs Lidarr Extended comparison","score":0.8,"suggestion":"install Lidarr Extended docker","score":0.7]
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:
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. lidarr-extended
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.
The primary difference in this version is how it handles downloads and metadata. lidarr-extended/ ├── post-process
Lidarr-Extended often comes with a "Queue Cleaner" script. In standard Lidarr, a stuck download (one that errors out) can hang the entire queue.