My library has been static for years, but I get these updates in my logs every week still…
I have (already, long time ago) set my library update interval to be 1 day. I have also removed music from my update (not sure if this does what I think it does):
I believe that plex will continue to attempt to match any unmatched content, and refresh missing metadata during the scheduled maintenance, you can sometimes see messages similar to ‘butler refreshed x number of artists’ in the server alerts log.
the lyricsfind you have pictured above is for the last.fm agent.
there is no specific option for lyrics, but the other options for the plex music system is in the ‘advanced’ settings of the music library.
I don’t know of any way to disable the butler/metadata/matching refresh, other than disabling the scheduled background tasks and setting the maint window to like 1 hour.
Even if it does this, frankly it really only needs to do a single DNS lookup at the start of the process? Currently I have this set to once a day, so I should see 7 entries… not thousands.
Even if that was not true, and it somehow did a DNS lookup for each unmatched title (egad!), then there should still not be this many. I have a feeling that it does not adhere to the update schedule I have set.
I’ve looked through my logs, and don’t really see any big issues either…
I think this LyricFind is just a very poorly developed component with no easy way to monitor and remedy issues.
just a thought, from my own user perspective, if you have lots of users listening to music, you may notice in the settings > alerts log, that plex seems to refresh some kind of metadata for every track played.
this could be the source of the look ups?
also, lyricfind.plex.tv could be being used for other plex music metadata as well (it’s just a host name, but could be returning related artists or whatever too).
There is one possibility. Almost all of my ID3 tags are valid and compliant. I spent a lot of time fixing this up. But one thing I think This Lyricfind Agent does is assume that the Album Artist is always valid. However, I have many compilations and soundtracks, and my Album Artist is set to “Various Artists” and my track artist lists the correct artist.
I think it keeps on hammering its head against this “Various Artist” brick wall instead of using the track artist.
Or how about perhaps flagging the issues and giving us a way to fix them in the UI?
That’s possible, I have a few clients (2 TVs and some mobile devices, as well as 3 Web Apps).
But so far most of the rest of my family use Spotify (since Plex/Tidal does not work with family accounts). But, yes, merely running those apps may trigger these lookups.
Still DNS entries should have a TTL and be cached upstream…should not even hit my DNS server…
plex music tries to match to an applicable release @ musicbrainz, stuff that isn’t in mbz it will keep attempting to match over time (via scheduled tasks rolling refreshes)
plex music is more picky about folder/file naming/organization than previous plex music system (before 2 or so years before)
folders filled with random music, plex really doesn’t like (cause it can’t match to mbz)
All my music was categorized using MusicBrainz Picard, matched to exact albums, fingerprinted, and the ID3 tags were refreshed before pushing them to my NAS folders.
So the tags should mostly be pretty solid.
I’ve fixed most of the matching issues now thanks to the tip you gave about the Uncategorized filter.
The only ones that remain are tricky artists that seemingly have no Plex entry (it find the artist on the Last.FM match, but keeps showing them in Uncategorized).
I’ll be monitoring the DNS requests again hitting my local DNS forwarding master (next week).
