What is Reddit's opinion of
Lidarr?
From 3.5 billion Reddit comments
➔ Lidarr website
By popularity on Reddit, this Service is:
24 reviews of this app found across Reddit:
Lidarr does that.
> Lidarr is a music collection manager for Usenet and BitTorrent users. It can monitor multiple RSS feeds for new tracks from your favorite artists and will grab, sort and rename them. It can also be configured to automatically upgrade the quality of files already downloaded when a better quality format becomes available.
Maybe not the answer you want, and also maybe something that will work for you. I've looked at this a lot and my conclusion was that it's not really viable to self host something like this for the following reason: the heart of a music recommendation system is data not software. The actual deep learning pipeline that recommends songs and generates novel playlists is not particularly novel or hart to implement (though it's not super easy either), there are several projects on github right now that can recommend songs for you today - if you bring your own data.
The magic sauce that google and spotify have is a large base of users from which they can analyze played songs, compare with other users and make recommendations. They also have a catalog of most recorded music and virtually all new music in the traditional market.
No matter what, you'll need a 3rd party source of data, if for nothing else than you need to feed in new music data when songs get released. My compremise is this: Spotify has great recommendations and playlists, better than google IMO. I use an unofficial api to create playlists and recommendations which can be downloaded from spotify directly if you pay for a sub or sent to lidarr to get it from the internet. It's all my MP3s and my player, but the song track data and playlists/recommendations come from spotify.
If you really want to host it completely yourself, you could look at a fully complete project like this.
Just a head's up for everyone here: Lidarr is still very much in development at the moment and we still have a good many issues with parsing downloads and imports, but they're one of our top priorities. To keep up with everything, please join us on Discord and feel free to report any issues on our GitHub.
Congratulations and thanks to the team for all the work. Excited to hear about Lidarr 1.0. Will it finally fix the issue with moving extra files not working? Makes Lidarr useless for those of us that want to retain nfos, cue sheets, and logs. We end up having to do everything manually behind Lidarr.
although i can't say why it runs with loads of windows fpcalc is used to help identify the tracks.
the following link explains what it does
https://github.com/Lidarr/Lidarr/wiki/Health-checks#fpcalc-missing
​
the main gist of it is as follows:
" Lidarr can use chromaprint audio fingerprinting to identify tracks. This depends on an external binary, which is distributed with Lidarr for Windows and macOS but must be provided independently on Linux. "
Here ya go. It's on Git under the "Releases" tab.
https://github.com/lidarr/Lidarr/releases
Just untar it to where ever you keep things (I use the /opt structure myself) and basically the install and setup is the same as Sonarr or Radarr at that point.
Importing Spotify data into Lidarr is a top feature request. https://github.com/lidarr/Lidarr/blob/develop/README.md
Maybe not helpful now but something to watch as that could automate downloads after import
You backup the binaries? why? there's no data within the bin folder, it's all within the app data folder + your media folder.
>Is this size increase normal/expected?
Yes, this is also evidenced by reviewing the zip sizes on github.
> Are the files in Lidarr/Lidarr.Update required?
Yes
> Is this just a directory for storing future updates?
No, it's the updater.
> Do the binaries there get recreated with a new update is detected?
N/A, see above and below
> Can this directory's contents be deleted?
Technically yes, but then you will always need to update manually and this is not at all advised.
I don’t use lidarr, but my quick research tells me settings > import lists > Spotify playlists
That said, it sounds like lidarr monitors whole albums, as usenets/torrents are packaged and distributed by the album and not by the individual track. So when you monitor a Spotify list of 50 songs, Lidarr will actually monitor for the full album of each of those 50 songs.
(source)
The only thing it could be then is if there is no download link in the results then Radarr/Sonarr/Readarr/Lidarr outright ignore them. logging for this was recently added to nightly; which would mean possibly an issue with rutracker and prowlarr
https://github.com/Lidarr/Lidarr/commit/3ac24013045efe80793a6f7e7b0c13cce9c2fed2
Looks like based on the code you can pass some page # & page sizes?
https://github.com/Lidarr/Lidarr/blob/develop/src/Lidarr.Api.V1/Wanted/MissingController.cs
Set the options in wanted missing and check the calls
Trace Logs of lidarr failing to work with transmission?
What lidarr version?
There's no validation for username/password. https://github.com/Lidarr/Lidarr/blame/develop/src/NzbDrone.Core/Download/Clients/Transmission/TransmissionSettings.cs
Not yet. Turning on debug logging didn't work for me, I've opened an issue on GitHub about it. https://github.com/Lidarr/Lidarr/issues/2394
Oddly enough I have a Readarr instance for audiobooks that is exhibiting the same behavior.
make sure albums hierarchy is as such,
Top folder - Artist
Next folder down - Album (year)
​
you can use Lidarr to rename your folders and tracks if you don't want to go through them manually.
Would you accept a pull request that implements it? I can't guarantee any timeline, but I've submitted a PR for Lidarr in the past (https://github.com/Lidarr/Lidarr/pull/1910) and imagine Readarr would be similar in terms of code style.
Lidarr. If you have used Sonarr/Radarr, the concept is basically the same.
Alternatively, setup Beets on your server, drop everything into a watch folder and let it do what it does best.
Edit: just noticed you wanted something with a webinterface. Beets won't cover that, but it's still worth a look as it'll do it all automatically.
Removed per rule #4. Not specific to torrenting thus too broad for /r/Torrents
This topic is really for the /r/Lidarr sub, maybe send a message to the the mods there if you're having trouble posting. Alternatively you can try a more general sub like /r/SelfHosted /r/HomeServer etc.
PS - Their Github page also lists other links for support if Reddit isn't working out https://github.com/lidarr/Lidarr
Please don't duplicate album releases on MusicBrainz just for Lidarr convenience. At some point in the future multiple copies of the same album is planned to be supported by the devs: https://github.com/lidarr/Lidarr/issues/729 In the meantime, messing up an already correct listing on MB is a really bad suggestion and will either get rejected outright, or worse go through be wrong. <3
Bit more info now I am not on my phone.
Looks like the Devs got fed up dealing with Musicbrainz directly and to improve performance cache responses in their API layer hopefully speeding up response times for everyone.
https://github.com/lidarr/Lidarr/issues/151
You may want to jump on the Lidarr Discord and see if there is actually a benefit on setting up a local API. I assume the Lidarr server runs Musicbrainz alongside the API so the standard Musicbrainz rate limits will not be an issue. I cannot find any details about rate limits though...
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
echo "deb https://download.mono-project.com/repo/ubuntu stable-bionic main" | sudo tee /etc/apt/sources.list.d/mono-official-stable.list
sudo apt update
sudo apt install mono-complete
cd /opt
sudo wget https://github.com/lidarr/Lidarr/releases/download/v*/Lidarr.master.*.linux.tar.gz
sudo tar -xzvf Lidarr.*.linux.tar.gz
chown -R lidarr:lidarr /opt/Lidarr
chmod -R a=,a+X,u+rw,g+r /opt/Lidarr
sudo nano /lib/systemd/system/lidarr.service
[Unit]
Description=Lidarr Daemon
After=syslog.target network.target
[Service]
User=lidarr
Group=lidarr
Type=simple
ExecStart=/usr/bin/mono /opt/Lidarr/Lidarr.exe -nobrowser
TimeoutStopSec=20
KillMode=process
Restart=on-failure
[Install]
WantedBy=multi-user.target
Cntrl x and save
sudo systemctl enable lidarr.service
sudo apt install -y libchromaprint-tools
sudo systemctl start lidarr.service
sudo systemctl status lidarr.service
These are the commands I normally use. Change the * to the version number of Lidarr and the username Lidarr to whatever your username is
Plus if you have Google music you can upload your own music and have it available in the cloud so you can fill in the gaps.
Not exactly the same since it can require a ton of additional work on your end depending on how mainstream your music tastes are, but if you're tech oriented and have the time to invest in a homelab, you can automate that difficulty away.
I'm running FreeNAS 11.2-U5 and just installed Lidarr the other day in it's own jail.
https://github.com/lidarr/Lidarr/wiki/Installation-(FreeBSD-FreeNAS)
I got the note that fpcalc wasn't installed so I installed that. I did install the latest version of fpcalc (1.4.3) but Lidarr is now telling me " You have an old version of fpcalc. Please upgrade to 1.4.3. "
If it's an EP, it won't get pulled by default. You have to enable that. Check out the FAQs:
Tried it, hated it. Same with Picard, MusisBee, Itunes or whatever. It just doesn't work the way I want for my collection. Some projects like headphones or lidarr look promising but still use that damn muzicbrainz db, which just sucks. And are geared towards torrent/usenet downloading, which I don't need.