With Lidarr being not very functional due to the Unable to communicate with LidarrAPI - Lidarr API “Internal Server Error” 500 | Invalid response received from LidarrAPI | HTTP Request Timeout · Issue #5498 · Lidarr/Lidarr I have been thinking about getting rid of it altogether. I have only started using it recently and don’t like it.
What I use Lidarr for:
- Find metadata for music
- organize files in a consistent way base on metadata
- obtain album art
- create .nfo or other files
- Identify desired music and instruct download utility to get it (this is optional for me— I can handle myself if needed)
- Do the above via a web interface which can be browsed nicely
I don’t like about Lidarr:
- The not-really-open-source nature of it, e.g. this current problem, where you are reliant on their external server to run your own home server. I feel this might be a more pervasive issue in the Arrs but not sure of all the implications
- How unsupported it is to include work that the lidarr servers don’t know about. There will never be a metadata database which includes all music. There is just too much music in the world!
- no audiobook/podcast support
I also have Jellyfin going for the actual serving/streaming of the music. Am not sure if it is able to fully manage the metadata and files?
Lots of options in the awesome-selfhosted list.
I could use a linux desktop app if it was better than a selfhosted server.
Thoughts?
Well it looks like just what I wanted! I’ll put it on my “when I get comfortable with Docker” list. Which due to it’s rapid growth, is becoming a “reasons to get comfortable with docker” list.
Looks pretty new, since June or July this year. I will admit I am suspicious of projects making claims like “Learning curve ✅ None”. I find they tend to assume a lot of prior knoweldge. I will check it out in a while, I think.
BTW the link you posted has tracking, not sure if that was on purpose.