Selfhosted

60693 readers

682 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Beets tips & config (piefed.social)

submitted 1 day ago* (last edited 1 day ago) by BruisedMoose@piefed.social to c/selfhosted@lemmy.world

31 comments fedilink hide all child comments

I'm finally making a real effort to add beets to my life. I've been hesitant because I like what I like and I (mostly) know what I'm doing, you know? I also have a lot of local independent albums that are just not likely to get tagged anyway.

But here I am. Yesterday I was able to work through:

Implementing my preferred directory structure and naming conventions
Adding album art (embedded and in the folder)
Embedding lyrics
Adding ReplyGain information

I use Navidrome as my server and have a collection of about 2000 albums.

What are some of your tips for using beets?

What cool things are you doing?

What should I be thinking about as I go about this?

you are viewing a single comment's thread
view the rest of the comments

[–] talkingpumpkin@lemmy.world 1 points 23 hours ago (1 children)

IDK if I'd recommend this to others, but I don't trust unsupervised metadata lookup (I'm anal like that), so I lookup metadata with musicbrainz picard and then feed the files to beets only to keep my library organized.

My beets doesn't do any lookup (no lookup plugins are enabled, none_rec_action: asis, fetchart configured to only look at the local filesystem).

[–] BruisedMoose@piefed.social 2 points 17 hours ago (1 children)

This is kind of how I have been operating. Rip to FLAC. Manage the lookup and tagging manually. Then I have a series of scripts to convert to MP3, apply RG, and send the FLAC to an off-site backup, move MP3s into the library.

I thought maybe I've been too anal about my tags and I should just work through letting it standardize and add IDs to everything. But now you all have me questioning that part.

[–] talkingpumpkin@lemmy.world 1 points 16 hours ago

Picard adds IDs too (well, I think it only adds musicbrainz ids, per default anyway, but those are the only ones I care about).

The lookup is automatic as well (you can review or intervene if it fails to identify the release).

It also has a plugin for replay gain (I redo that step in my script anyways) and can be configured to delete any previous tags if you re-process music that you had previously tagged with some other software (IIRC it doesn't clean them up per default).

If you've not used it, I recommend giving it a try before deciding how to go on.