What is your go to music grabbing solution?
angielski
I’m looking for a YR-DLP GUI for just music, or a good way to access music in general. I had a lidarr-on-steroids instance running but it kept disconnecting from deezer and i’d love to get that back up and running but it looks like it’s not supported any more. Yt-dlp looks like a decent enough plan B, but i’m open to other discussion
Nicotine+ to grab what I want, EasyTAG to edit metadata, move the files to my self hosted instance of Ampache which I can then access either with SublimeMusic on desktop or SubStreamer on my phone if I’m traveling.
Youtube-dl to download things in flac format from youtube (and sometimes rarely other sites when what i want isn’t on youtube, which is rare because people upload everything under the sun). I haven’t the need for anything more complicated.
I don’t support the .NET Framework which is a dependency of most (all?) of the -arr suite. It’s a fairly divisive and niche argument so I didn’t bring it up initially, but I try to reduce my reliance on proprietary software and hardware as much as possible.
I use Lidarr for most music grabs. spotdl when Lidarr fails to find (which is uncommon since I use usenet). Then I use beets to manage music files <a href="">https://github.com/beetbox/beets</a> .
I have beets setup to run as a cron every 10 min, and it looks in the location that nzbget downloads to, and it automatically converts, fixes ID3s via musicbrainz db, and moves the completed files to my music section. Anything that beets doesnt see as a 95% match, I then manually run the script and choose the correct musicbrainz ID for the band/album.
It works well, and you can trigger LMS (logitech media server) and Airsonic to update automatically. So if something goes in all automated, then your players will also ‘just’ have it available.
That sounds like a dream. We’re there any specific tutorials you followed and could recommend or did you just try to click things into place until it all worked smoothly?
So Lidarr/NZBGet (or whatever you use) are pretty straight forward.
It gets complex with beets. Not that it is inherently complex, it just has an absolute shit ton of options. You want to start with a yaml config, and just get the feel of how it operates. There are lots of “howto’s” online, but unfortunately “beets” is a way to simple search. So you need to beef it with some specifics related to ahem music.
The manual and github do have it well documented. I would suggest starting with a subset of your collection, and just tinkering, (move files from /home/a to /home/b, convert to mp3 and fix ID3). It comes together pretty quickly. But the configurables of beets is crazy (in a good way).
Other things like triggering scans from LMS etc, they are documented on their respective sites.
I’ll fess up - its not immediately for the faint hearted, but its probably not that hard for most people - who actually read documents and learn.
You do not have to run a local of Musicbrainz (I do - because I can, it removes API limits but its expensive in storage and data) just point to the public instance. Also you could do Headphones, but I moved away from that years ago and have had a much happier experience with Lidarr.
I literally make a Spotify playlist then run it through a website that lets me download metadata and a MP3 of the song (usually it’s from YouTube). I usually look on Bandcamp for albums I like tho because .flac sounds slightly better.
Dodaj komentarz