submitted 2 days ago by matey@lemmy.dbzer0.com to c/piracy@lemmy.dbzer0.com

13 comments fedilink hide all child comments

Are there any functional alternatives to Lidarr that function similarly? (Integration with the *arr stack, integration with download clients. I doubt there's another that would integrate with something like Jellyseerr or Ombi, but that would be a huge perk.)

top 13 comments

sorted by: hot top controversial new old

[-] ragebutt@lemmy.dbzer0.com 23 points 2 days ago

Headphones I think it’s called? But lidarr has the best integration given it’s a fork.

If this is about the lidarr metadata being fucked you can try something like https://github.com/blampe/hearring-aid, which has its own issues but is working.

All of the arr stack developers flip their shit if you so much as suggest adding support for a custom metadata server. It is by far the biggest weakness of the stack and it is mind boggling that all the major forks have inherited this behavior from sonarr.

Lidarr shows how foolish this approach is, musicbrainz makes one change and the app is fucked for over three months now with no end in sight. Thetvdb could do this to sonarr, themoviedb could do this to radarr. Adding a method to add other database sites with api access (or even just local data) should be a priority, but they not only dislike the idea, they get mad about it. Oh well, free project, fork it if youre so great, etc etc

[-] Appoxo@lemmy.dbzer0.com 8 points 2 days ago

The issue isnt the metadata providers changing the API.
The issue is that the devs insist on implementing an API proxy/metadata mirror to lessen the burden.

Bro, just le me pull my own API key and let musicbrainz decide how much free API calls I can execute.

[-] siskourso@odin.lanofthedead.xyz 11 points 2 days ago

At this rate lidarr will have the same fate as readarr did as it seems the main focus of the servarr devs are focused on radarr and prowlarr.

The problem is they have only one person left with the keys to the metadata server and if they are busy then it’s not a priority. Which I understand as a free project but just emphasizes how bad this approach is to have just a single metadata sever.

But with that said I’m still holding out hope for Lidarr, now finding a good readarr replacement that’s another sad story.

[-] srasmus@slrpnk.net 11 points 2 days ago

On the readarr front, check out chaptarr. It's currently in a closed beta, but it's looking like a great replacement.

[-] Confused_Emus@lemmy.dbzer0.com 4 points 2 days ago

Lidarr is not in danger of being abandoned like Readarr. The new metadata server for Lidarr is already up and in closed beta. A few final issues are being worked out before it’s opened to the public.

[-] Appoxo@lemmy.dbzer0.com 3 points 2 days ago* (last edited 2 days ago)

Says who? A pull request?
If there is a beta/nightly branch I can install, I'll be glad to use that so I can finally import the music I have acquired so far.

[-] Ghoelian@lemmy.dbzer0.com 4 points 2 days ago* (last edited 2 days ago)

Apparently they keep posting updates on their discord for some reason. This is the last response someone shared on github:

Hi everyone, it's July 25. Yesterday, the devs and mod team here have begun (early) alpha testing of the new Lidarr metadata server.

In general, things are working fairly well. There are a few issues to resolve before it can go live. But we wanted to let everyone know that we have some concrete forward movement happening behind the scenes.

NOTE: This stage of testing is NOT OPEN to users. We appreciate your patience, but at this stage you cannot help. This update is meant to let you know that the project is not dead, as some have incorrectly theorized, and that there is behind-the-scenes work heading toward getting the new metadata server up and running as quickly as possible.

Please continue to be patient, and continue to use this channel for Lidarr support questions. If you have other conversation topics, please use ⁠general or another more appropriate channel for that.

Thank you from the devs and mod team.

[-] Appoxo@lemmy.dbzer0.com 4 points 2 days ago

Yeah...I saw that update. But I wouldnt count an update from the end of July recent in any capacity.
Because this sort of message has been repeated since the beginning of July with minimal changes to the content.
It's mostly a "We are still alive and sometimes working on it".

No issues with that. It's their volunteered free of charge time they are giving for our entertainment. Which I heavily appreciate. It's just a bit annoying how little information they give out (and their, sorta understandable, tone used in their support channel).

[-] Confused_Emus@lemmy.dbzer0.com 1 points 1 day ago

They’re standing up a new metadata server, which takes time. What more information are you expecting from them? I mean I suppose they could just lie and say sure it’ll be up next week, but it would be a lot more frustrating for them to keep saying that and pushing back the date.

[-] Confused_Emus@lemmy.dbzer0.com 2 points 1 day ago* (last edited 1 day ago)

Says the official support channels, which you should be checking for information anyway, unless your only intention is to scream your frustration into the void. If that’s the case, best of luck on that resolving anything.

ETA: like I said, it’s a closed beta, so not something you can install. And it won’t be a pull request because this fix won’t require an update to Lidarr, it’ll just start working again when the new server is done.

[-] Confused_Emus@lemmy.dbzer0.com 5 points 2 days ago

What the devs keep getting irritated about is people coming into the Official Lidarr Branch support channels and asking for support for something the devs have no control over or ability to assist with. Keep in mind that an individual user’s Lidarr instance does not connect directly to musicbrainz - the volume of API requests generated by Lidarr would be unsustainable without subscriptions. It connects to an intermediary metadata server set up and maintained by the Lidarr volunteers.

If they add a built-in option to add custom metadata servers, people will have an expectation of support. Even a note right next to the option that states custom metadata servers get no assistance wouldn’t help much since most people can’t seem to read. Basing that on the number of people who come into the Lidarr support discord channel every single day and ask if something is wrong with the metadata server despite there being a stickied message with very bold lettering explaining the issue and its current status.

I will agree that the devs in the discord have a shit bed-side manner, though. But there’s a reason that, if this were software produced by a company, you’d be speaking to a customer support specialist instead of directly to a dev. As someone who long ago worked my way up the IT ladder out of the rage-inducing pits of user-facing support roles, I definitely get it.