Skip to content
This repository has been archived by the owner on Mar 21, 2023. It is now read-only.
RandomNinjaAtk edited this page Aug 9, 2020 · 5 revisions

Q&A:

Q: How is music found? (process)

  1. The script connects to Lidarr to pull artist list.
  2. The connects to "https://musicbrainz.org" or a mirror (if configured) and pulls every release for each artist in your Lidarr instance and caches the data locally (only updates cache as needed).
  3. The script will pull your monitored/wanted album list out of Lidarr and begin processing it.
  4. When processing a wanted album, it will first look in the local cache to see if a Album URL for an online resource is already attached to the particular album. If found, it will use that link to process the download. If it is not found, it will attempt a fuzzy match search and download the first match it finds.
  5. If URL found, download the requested files, if not found, log it in the "notfound.log" file
  6. Notify Lidarr to scan and import the completed download

Q: How are music files named?

The naming is completely controlled by your Lidarr configuration upon successful import

Q: It cannot find albums that I know should be available

Musicbrainz (https://musicbrainz.org) is a community managed database, while not perfect, it empowers users to be able to add/update/enhance it. Adding the music album (with url) to the relevant artist on Musicbrainz, will enable the script to automatically download the requested album.

Q: Why should I spend time updating Musicbrainz?

Updating Musicbrainz means you are helping the world! If everyone in the community spent a small amount of time updating the database with the Music. Then everyone in the community would benefit from those updates. IE: User1 updates their favorite artist with new albums and User2 does the same thing for their favorite artist. Now both users can download music for both artists as a result of both putting in a little effort.

Q: Why does it seem slow to cache artist information for music?

Musicbrainz is limited to 1 api query per second. So depending how many api requests are needed, it can take considerable time to build the initial cache. The only way to speed this up is to use a mirror and in that case, you can increase the ratelimit to a desired setting. Linuxserver.io conveniently provide a dockerized Musicbrainz mirror that you can self host for this purpose, for more info: https://hub.docker.com/r/linuxserver/musicbrainz/

Q: How do I import the Music into Lidarr:

Lidarr is automatically notified and will import files if it matches a release using its internal matching engine. Files that are not imported will be found in the download directory /downloads-amd/amd/import