I use the full stack and all very grateful for the products.
The remaining annoyances are:
- lack of multi language support
- there is no connection between the systems when you want to remove a movie (you remove it in one place and everything knows about that and acts accordingly)
- I still did not make to fully grasp how and where to say "I do not want this particular release". I think I saw that in radarr but it never is obvious to me where it is.
Yeah I was initially surprised when learning about the *arr stack for the first time, as my intuition was very insistently telling me: "I must be gettint it wrong, these ought to be all a single service!!"
They all definitely feel like small parts of a single package, don't look like they merit being their own thing. But it's not my thing, so what do I know.
I have no idea why Radar and Sonarr are seperate programs. Surely the difference in searching for Movies vs TV is a single line of a query search string.
Honestly I just think the concept of Son/Radarr doesn't translate well to music, I find Lidarr fiddly in general.
In particular I'd add to your list that the overnight scans to update cover art are an absolute mess. It's not so big a deal on my libraries in Sonarr and Radarr, but for Lidarr? Jesus Christ. I have reasonably sized music library (~400/500 gig), and every night Lidarr starts phoning out to check, for every single album and artist, whether the associated cover art or artist image has changed. This takes hours, and is completely unnecessary, and cannot be turned off. I've resorted to just blocking the addresses it does this on, but this breaks things when I try and use it to add new music.
> there is no connection between the systems when you want to remove a movie (you remove it in one place and everything knows about that and acts accordingly)
Not following this. Settings -> Connections in Sonarr for example.
What I meant is that there is no common management of dat. When I make changes in one service, the others do not know it, or know it after the fact (via a reindexing for instance).
Say for instance I delete a movie in Jellyfin. Radarr will then pick up that it is missing and re-upload.
Or that I deleted a torrent in deluge. Radar will restart it.
Most of the things are doable, one just need to know what to do where, exactly (otherwise the other pieces may try to recover).
Right now I am making the chnages in Radarr (despite actually seeing them in Jellyfin). This is a real problem when I have, say, two uploaded versions of a movie and want to keep only one. I have to be very careful to track down in JF what I will remove in Radarr.
It would have been great if there was a common indexing mechanism across all the suite.
What you pointed me are notifiers - they work fine (but are shoot-and-forget kind of services)
The remaining annoyances are:
- lack of multi language support
- there is no connection between the systems when you want to remove a movie (you remove it in one place and everything knows about that and acts accordingly)
- I still did not make to fully grasp how and where to say "I do not want this particular release". I think I saw that in radarr but it never is obvious to me where it is.