I’ve started using beets to manage my music library, but it doesn’t work well with jellyfin. As you can see, it creates about a million artists off of features, and this makes it hard to use. I can’t find a way to fix this in beets, so I’m considering switching, but haven’t found any proper alternatives. Do you guys solve this in any way, or use a different management software that is more standard? Thank you!
You must log in or register to comment.
Bro you leaked your ip wtf 🤯🤯😂💣💣🧨✈️
For those wondering why this is downvoted 192.168.X.X are local ips. Meaning on local connections use that IP, and is not available to the wider world to use.
It was most likely a joke.
Yes, but there’s a lot of people that lurk to learn in these forums. So I just wanted to explain it to them.
It’s a joke, I know it’s a joke, I’ll give you your upvote.
Not mine, my servers 🤣. I hope it doesn’t get hacked
I tried Jellyfin for music in addition to tv and movies, but ended up dropping that part. I set up Navidrome with beets - the adjustment is using album artist instead of just artist everywhere.
Full stack:
- Navidrome server
- beets for management
- Feishin client (local on my desktop, though I do have it hosted too for the hell of it)
- Symfonium (mobile app, abour $6 but absolutely worth it)
- Lidarr
- slskd
- Soularr (integrates the two above - it’s a bit hacky but it works fairly well)
Not sure if you already know this, but there is a plugin called “Tubifarry” for Lidarr, that directly integrates slskd as an indexer and download client in Lidarr. I’ve recently switched from Soularr to the plugin and it works really well. In combination with the “Search Sniper” Import List you can still get that random backfill behavior of Soularr.
Here is some general information on lidarr Plugins. You have to use a special branch/image. There’s also a link to Tubifarry at the bottom of the page.
Oh shit I hadn’t heard of this one. Soularr feels kind of like a hack and is annoying to wrangle, so a direct integration would be huge.
I didnt know soulseek integration with lidarr was possible.
I am also using Navidrome and Symfonium. It’s about as good as local library playback can get! Thanks for a new one to try Feishin, never heard of it before. I have tried setting up Lidarr, but I never got it to grab stuff and rename it to what i like, so I stopped. I’m sure I probably could, but I didn’t want to spend the time trying.
My current setup is grab from Orpheus or redacted, run it through program generically called tagscanner (been using it for years and love it) then drop everything into musicbrainz Picard with custom setup to only grab genres for everything and will attach up to 5 different ones. From there, i move everything to the music library by artist and subfolder for albums. Once there, i load Musicbee, which is my pc app of choice because of the customization and audio playback quality. Once there, if any album art is missing, it’s easily discoverable and then loaded into navidrome.
The hardest part was discovering that I should organize properly after a decade of collecting music, and it took months to reorganize and tag everything properly. I had to do that once more with genres. Once I figured out how to automate that and would take chunks at a time and have it do it over days, which also took months. It’s been about 10 years of me doing it this way and has worked great if not a bit tedious.
This is the way
deleted by creator
This is a Jellyfin problem; not a beets problem. You can easily solve it with beets config if you’d like to, though.
The distinction between what you want vs. what you’re getting is that Jellyfin is grouping by the “Artist” tag instead of the “Album Artist” tag. I haven’t touched Jellyfin in years, but look for a builtin setting or alternative view to group by album artist - you’ll almost certainly find it.
If you want to solve it in beets, you can do that through a custom script, the FtInTitle plugin, or a combo of the inline + advancedrewrite plugins. Remember to run a re-import on the Jellyfin side after making your tweaks to the beets pipeline to make your changes show up without duplication.
I use Lidarr. I know its primary purpose is downloading but if you just never configure those parts, it can do all the renaming, folder organization, and metadata tagging. It uses MusicBrainz primarily, iirc. You can also configure scripts to run it through beets or other tools too.
There’s no perfect solution for this because music metadata is a lot more complicated than movies or tv. But Lidarr gets pretty close to set-and-forget.
I’ve also tried MusicBrainz Picard with pretty decent results but I found it sort of suffered from the problems you described for your current system.
Musicbrainz Picard --> mp3Tag --> MusicBee
- Picard handles the initial tagging.
- mp3Tag handles the clean-up. I like things “just so”, and some of the time Picard goes rogue. The Actions function is super powerful for automating “fixing” tags. Oh, and you can cut, filter and paste an entire directory’s worth of song tags if you want to bulk remove a bunch of unwanted tags that Picard adds.
- MusicBee is the database. I like the Inbox feature that allows me to do a last check before “promoting” the files to my master library.
There are portable versions of all three, so you can lock a version in your music directory and never worry about updates ruining your tags.
I have the same setup with Picard --> mp3tag, it works very well for me. I prefer to overwrite the artist field with the album artist field for cleaner sync to my iPods with MediaMonkey (iPods handled multiple artists in the worst way imaginable).
Picard did take some light up front tweaking to get the directory naming to albumartist\yyyy - albumname\01 songtitle.flac but it was worth it
First, I made ‘Album Artists’ my landing page. 'Artists" includes everyone tagged in the metadata, ‘Album Artists’ only contains the primary artists. For me, the difference is 350 album artists vs 1412 artists.
I run everything through Picard when I add something to the server. Sometimes I have to change the metadata (for example I hate having an entry for ‘&’ like Elton John & Hans Zimmer and I’ll change it so the album is included in both Elton John and Hans Zimmer but theres no entry for them together). But generally it’s pretty simple and smooth.
Looks like this:
I use picard, which works great, but is by no means automatic. Keep an eye on https://github.com/sentriz/wrtag, I think it’ll be really clean and highly functional in the near future.
I gave up on automating it, I download with slskd, and run musicbrainz Picard (import slskd download folder, and set it to always save to the jellyfin music folder/rename with my preferred sorting method). This has the bonus of downloading the cover art, and rarely has issues.
You can automate soulseeked with a script that connects slskd to lidarr.
For music. I use navidrome. It works a load better then jellyfin for this IMO. You can use the same file location for both jellyfin and navidrome if needed.
Use one artist for album artist. For the artist field, look up how to properly split entries. This is different for IDv3 vs Vorbis. Split the artists and Jellyfin will handle it fine.
I tag all my music through MusicBrainz Picard before adding to my server. I think most of the artists are good after that (i.e. if there is a featuring artist, it becomes a separate entry), but I typically use the album artist field to browse by artist.
ETA: I have run into enough cases of Picard wrongly tagging my music that I wouldn’t want it automatic. It is not often, but enough that I would be annoyed.
hello, maybe try wrtag which was written to be a faster version of beets. it handles album artists out of the box (multi valued tags instead of one string with ft. delimiters). it can be configured with the path format syntax to be similar to your current beets config
I come back to this problem every year or so because I’m never satisfied with my music metadata. Years ago I had my musicbrainz picard settings dialed in really nicely, where I could drag folder over and it would spit out the right thing like 7 out of 10 times. It still required a lot of doubled checking and manual oversight though, so I was never satisfied.
I tried mediamonkey for a while, because it has decent metadata support and plugs into most of the expected APIs. But when all is said and done, all these tools use the same data sources, and none of them are exactly consistent with each other so matches aren’t as straightforward as they should be.
Lidar never quite did it for me, so I haven’t looked at my install in a couple years. But based on @skoberlink@lemmy.world’s recommendation I’ll try a fresh install and see if get I better results this time. I’m always happy in the arr interfaces.
Have you tried enabling the FtInTitle Plugin? https://beets.readthedocs.io/en/stable/plugins/ftintitle.html
I too was unsatisfied with jellyfin’s music handling. Not only was the website disorganized and bad at using the built-in album art, but all the android music players i could find for it were also barely usable as well.
I can’t use musicbee because it’s windows only. I still want synchronized play history, metadata updates, and everything between my phone, pc, and mp3 player so a single OS software was out of the question.
I use a combination of beets, navidrome, and tempo. Beets is the metadata manager; once i’ve beet imported an album, it’s ready for navidrome to pick it up and serve it to any of my devices. (I have a custom sync script for my mp3 player that does the same). Navidome serves the music to any connected devices, converts it on the fly to lower quality (for low speed phone network situations) and also keeps track of my play counts, and my playlists for me. It’s not nearly as complicated as some of the other setups, which I also prefer.
I use tempo on my phone to connect to navidrome on the go and it has worked out incredibly well so far.
