91–100 of 124 posts
How do you all handle FLAC/CUE releases? A problem I have is that I want to have processed/tagged tracks, but I also want to keep FLAC/CUEs. I end up have redundant and separate organized library and original data.
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.…
Thanks for saving me time, I guess? I just maintain very spartan id3 tags on my music, artist, album, song name, track id, and that's about it.
What more would beets give me? How would it improve my experience?
If you're using Navidrome or similar to stream your music then check out beets-alternatives [0]. It lets you sync (and optionally convert) your library or a subset of it to another location, in my case my music storage mounted with Rclone. It's especially useful if you need to have a different naming structure in your target directory for whatever reason. I like to keep each disc of a multi-disc album in in its own s…
One of my favorite beets projects is beets-flask. It lets you set up fully or partially automated import pipelines with a nice web UI to manage any manual steps needed. Importing is usually as simple as dropping a zip in a folder and the rest is managed automatically. https://github.com/pSpitzner/beets-flask
Earlier quoted context omitted.
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!
Be sure to enable canonical so it converts the specific genres into their parent genre.
Is there any software that can use this to break up the single mp3 into the numerous individual song tracks ? And insert metadata ? And perhaps also fingerprint each track to match it to a specific version of the song ?
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.…
Can I ask what you choose to manage your library with today? I feel like streaming has made me stray so far from the joy (and pain) of library curation, and I’d really like to get back to it, I just don’t know what folks are using these days.
I guess my point is that I like having a directory of music (organized by artist/album) and make the discovery applications I use do the work of finding and playing the music I want.
Consider a case where a DJ's entire show can be downloaded as a single MP3, AND there is a complete playlist for the show. Is there any software that can use this to break up the single mp3 into the numerous individual song tracks ? And insert metadata ? And perhaps also fingerprint each track to match it to a specific version of the song ?
Been using this for several years now. It's definitely not for the average user. But nothing is quite so flexible.
(Only because I have an axe to grind) I really dislike "genre" and work hard to strip that metadata tag. It is so reductive. And flawed as well. Do we assign a "genre" to an artist? Album? Song? The band R.E.M.: "College Rock"? "New Wave"? "Alternative"? (Wow, don't even get me started on all the ways you can further slice up "alternative" into "shoe-gaze", "twee", etc. It's, ha ha, naval gazing for the music intelli…
Same, glad to know I'm not alone!
There are probably broad categories that I might find myself using, but for my own core collection of music (deeper than it is wide, mostly), it barely matters.
How do you all handle FLAC/CUE releases? A problem I have is that I want to have processed/tagged tracks, but I also want to keep FLAC/CUEs. I end up have redundant and separate organized library and original data.
I just split everything into tracks like they are on the album. Is there a tangible benefit to a single large FLAC with a CUE to tell the player where the songs are?
- The CUE maps the audio in a "CD-native" way, like each track can have 1 or more indices, which enables things like pregaps. When you split FLACs into discrete tracks you need to figure out how to project that onto files, do you put the pregaps at the end of previous tracks? At the beginning of next tracks? In short, with a CUE you can emulate the CD experience more accurately.
- If you are seeding a torrent, you need to keep the original data intact.