Lyrics for existing library

[lcbobit]

Hey,
I'm usingTubifarry with the lyrics plugin. So far it only works for files newly downloaded, not for existing ones. Is this by design, or am I missing something? Can I force to generate lrc files for exitisting songs?

Tubifarry version 1.8.1.2
Lidarr version 2.13.3.4692

[TypNull]

ld s'd categorize this as a Lidarr issue.

First off, Tubifarry uses the import consumer feature, which does update the .lrc file during import. The problem, however, lies in how metadata consumers are handled: album-based metadata is consistently executed, but track-based metadata only runs once either during the very first import of a track or when a download client retrieves the song.

I’m not sure why it behaves this way. When I discovered it, I was honestly a bit shocked and disappointed.

It would be great if Lidarr could apply track-based metadata updates to existing library files as well, but I haven’t found a function or setting in Lidarr that allows for that.

[dramikei]

+1 works perfectly for newly imported tracks, would be amazing if lyrics can be fetched for existing tracks as well

[TypNull]

I'll see if I can set up a task for this in Lidarr, though I’m not sure it’s even possible, so don’t get your hopes up. Right now, I’m using the lrcget Docker container once a month, and honestly, it’s a total mess. I’d really love to find a cleaner solution.

[dramikei]

Thanks a lot! :D
thankfully I only have 2-3 albums without lyrics, found this cool plugin sooner than later :)

[TypNull]

The upcoming release will also support fetching lyrics for older tracks, because the proxy system seems to be stable enough now, so I could add this feature.

[karldonteljames]

I think i'm missing something as I cannot see where to add the lyrics settings.

I'm running this as a docker contianer on unraid. my docker run command is:
docker run
-d
--name='lidarr'
--net='br0.25'
--ip='192.168.25.83'
--pids-limit 2048
-e TZ="Europe/London"
-e HOST_OS="Unraid"
-e HOST_HOSTNAME="Maximus"
-e HOST_CONTAINERNAME="lidarr"
-e 'TCP_PORT_8686'='8686'
-e 'PUID'='99'
-e 'PGID'='100'
-e 'UMASK'='022'
-l net.unraid.docker.managed=dockerman
-l net.unraid.docker.webui='http://[IP]:[PORT:8686]/system/status'
-l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/lidarr-logo.png'
-v '/mnt/user/MediaMusic/':'/media':'rw'
-v '/mnt/user/downloads/':'/data':'rw'
-v '/mnt/user/appdata/lidarr':'/config':'rw' 'ghcr.io/hotio/lidarr:pr-plugins' && docker network connect dlservices lidarr
857221432a5fb475159bcc19cb14648a4340e553f79645d02b4c7a8755729209

The command finished successfully!

I've changed from linux server so i can get the lyrics embeded into my growing library.

[karldonteljames]

I was convinced that i used that url, and thought earlier that if I removed it and re-added it (as ai saw that 1.9.0 didn't have lyric support) it would be there. As a sanity check:

as setup:

after removal and restarting

new URL before installing:

confirmation showing url:

after restarting the container:

[dramikei]

@karldonteljames
Dont remove the previous plugin when trying to install the develop version.

You essentially have to install the plugin twice

• install once (doesnt matter if you use the develop url or the master url). It will install the stable release of the plugin (version 1.9.0.0)
• Restart lidarr
• Install Tubifarry ensuring that you use the develop URL. (Do not remove the existing plugin)
• Restart lidarr
• Enjoy Tubifarry on develop (version 1.9.0.1)

The process had confused me the first time too :P

[TypNull]

Why is everyone uninstalling Tubifarry? 😭
You can thank Baker for this message, even if it’s not accurate. I already told him, but…
Check out the discussion here: #86 and dramikei is completely
Or, if you’d like to help fix it, you can vote or leave a comment here: Lidarr/Lidarr#5641

[karldonteljames]

did it twice and it did the trick! thank you so much!

I've spent some time this evening setting up a docker container built on lrcget that will recursively go through my music sort the folders alphabetically and start processing them by adding the .lrc files and embedding them into the files.

I'll give this a go though. Will this do all existing (as outlined above) or just new at the moment?
it makes little difference to me atm, as the container i've built is processing my library. - although i;m not 100% sure how accurate it will be! lets hope for the best. At least I have a backup i suppose!

[TypNull]

It can handle both existing and new tracks. New ones are always processed, but existing tracks only when you set up. I recommend triggering the first run manually or you have to wait a week.