Live data from Hacker News

Beets: The music geek’s media organizer

beets.io

41–50 of 124 posts

Re: Beets: The music geek’s media organizer

#41
post #39

I organize everything into Mixxx. It is tagged not only by genre, crates, some songs belong into more than one crate. Also by mood, which I tag with colours. And how much I like the song, which is by stars. I tried Beets and it was very underwhelming in comparison =)

Correct me if I'm wrong, but different target users here :) Beets seems to be for consumers who want to organize their music collection, and while Mixxx can help with that too, it's mainly for music connoisseurs who play for others (AKA DJs). I'm not sure how well someone looking for the first could use Mixxx, the interface isn't exactly the epitome of user-friendliness if you just wanna organize then press play :)

Re: Beets: The music geek’s media organizer

#42
post #35
post #28

I spent a truly obnoxious amount of time importing my music library into beets. It took a couple of weeks to get to 95% imported, and got so bogged down in the last 5% that I never completed the import and never switched over. This isn't necessarily a fault with beets, really, but a model mismatch. The model of beets is very, very strongly tied to associating each imported item to one well-known, commercial release.…

Fan recordings/edits/anything that shouldn't be on Musicbrainz just gets imported as-is, with maybe some metadata additions/tweaks. > * brand new indie label releases (bandcamp) > * commercial albums variants missing from musicbrainz/discogs This is a great opportunity to fill in those blanks for those services :) I didn't have much to contribute to MB but did have a few albums to add.

>Fan recordings/edits/anything that shouldn't be on Musicbrainz

Those should be on MusicBrainz. There's even a bootleg release type for fan recordings/illegal copies, and official style guides for live bootlegs.

https://musicbrainz.org/doc/Style/Specific_types_of_releases...

Re: Beets: The music geek’s media organizer

#43
post #28

I spent a truly obnoxious amount of time importing my music library into beets. It took a couple of weeks to get to 95% imported, and got so bogged down in the last 5% that I never completed the import and never switched over. This isn't necessarily a fault with beets, really, but a model mismatch. The model of beets is very, very strongly tied to associating each imported item to one well-known, commercial release.…

> * brand new indie label releases (bandcamp)

> * commercial albums variants missing from musicbrainz/discogs

I fixed those two by adding the missing releases to the database beets uses as its data source (musicbrainz.org), and importing the album in Beets afterwards. I still get notifications for edits to entries I contributed over a decade ago!

Re: Beets: The music geek’s media organizer

#44
Tried Beets once because it pairs well with Navidrome, it's pretty feature packed and exhaustive in what it does. Though after fiddling with it and realizing that it's more effort for my use case than I'd like I ditched it and now I don't really bother tagging. I hope to do the same thing for Navidrome too and find something to replace it with similar to KDE Elisa which makes it easy to make playlists on the fly and organize music around folders instead of tags.

Different strokes for different folks, that's not to say that Navidrome and Beets aren't amazing pieces of kit.

Re: Beets: The music geek’s media organizer

#45
I currently use OneTagger https://onetagger.github.io

It's more for adding tags before you add them to your collection. You can setup shortcuts to often used tags. Of course it can also rename and move files based on tags.

I then can auto create playlists based on those tags (with a different program)

Re: Beets: The music geek’s media organizer

#46
I've tried to use beets a number of times and given up each time.

- beets can't delete transcoded files which have been deleted at source.

- beets can't re transcode existing transcoded files when the source has been modified.

- It's impossible to preserve the original directory structure when transcoding because it strips all path separators for "security".

I use a Bash script I've been maintaining for a number of years instead.

Re: Beets: The music geek’s media organizer

#47
post #4

I love beets - the one thing I can't figure out is how to set the genre very wide. I like having a small number of broad genres - Rock, Hip-Hop, Jazz etc - but the tagging comes up with hundreds of distinct genres :(

I assume lastgenre with canonicalization[0] enabled is what you need, along with count=1 if multiple genres are an issue. [0] https://beets.readthedocs.io/en/stable/plugins/lastgenre.htm...

I think I'm using that already.

Limiting to one genre I don't think will fix it - what I want is to define the allowable values for genre, and then limit to one.

It's probably better with the limit one though!

Re: Beets: The music geek’s media organizer

#49
If anyone is looking at options in this space, I used to use Media Monkey for organising and curating my large offline music collection. It did things like metadata and album art management, album-level volume levelling, and would even reorganise the file structure of your music to whatever pattern you set.

I also loved that you could set up separate "libraries", so I could have metal and classical arranged by album, and EDM as a bunch of single tracks that are organised into playlists. Only downside is that it's Windows software.

Re: Beets: The music geek’s media organizer

#50
post #5

I recently looked into beets, but it seems it’s focused on automation, is that correct? I often buy stuff that has just been released, and that’s not yet in any database, so no automation works. My current workflow is download, unzip and manually tag (mainly genres, sometimes badly named artists/albums) with MusicBee (which gives me autocomplete for genres so I can reuse existing ones), and then copy the files to the…

I use MusicBee for everything too and sounds like my workflow is the same as yours. I basically take whatever is tagged on the file straight out of Bandcamp and then manually follow Discogs-like rules for normalization of the artist name so the directory structure works out, plus adding iTunes compilation metadata to deal with the "various artists" issue, adding BPM, customizing genre and comments etc.

I think I started all this fussiness exactly because back in the old days when you synced to CDDB, you'd get somebody else's useless record label classification for a reissue or international release that obscured the original label, which in certain genres of music is quite important to be able to better categorize the music for auto playlists. Original year is also critical for auto playlists where you're looking for tunes around a certain era. I also have a vague memory of old CDJs or Serato or some damn thing not displaying the name I wanted so having to shuffle stuff around to Composer or Album Artist or something to make it work, and now here I am with custom-tagged all the things.

My problem is I was considering replacing all my 320k MP3s with FLACs, which I have for all my Bandcamp purchases and most of my CD rips (although not from Beatport and other online stores)... but I realized it was going to be absolute hell to try and match the untagged files that I downloaded and put straight into cloud storage with the tagged files I already have in the library. It would need some kind of heuristics to fuzzy match the files with what's already there, then retag them with my preferred tags from the MP3, then move the file into the same location the MP3 is, then move the MusicBee proprietary metadata (play count, add date etc) across, then delete the MP3. I keep thinking there has to be a program or a plugin for this, but seems like not, so for now I've just given up and decided that 320k is good enough, actually, which makes me wonder why I'm keeping all these FLACs around in the first place. Not like I'm starting the Library of Alexandria here, I just like music.

Post reply on HN