this post was submitted on 12 Sep 2023
30 points (96.9% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54424 readers
365 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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 https://github.com/beetbox/beets .
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.
I like this approach
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?
Here you go, someones (slightly horrid) basic layout of how it can work.
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.
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.