Displayed times are always in UTC in LMS, is it coherent with your case? Will consider local tz.
For your faked multi values in the albumartist tag, yes this can be done as albumartists is not standard anyway. Albumartist is used as display string though. Ex:
Albumartist is “Au5 feat. Danyka Nadeau”, albumartists is set with 2 values: “Au5” and “Danyka Nadeau”
For the duplicated album names (and artist names), I have put no effort on handling this yet, as this problem is easily solved by music brainz ids. I have an issue already open to improve the situation when mbids are not set.
It is UTC. I’m simply used to changing that to local time via an environment variable.
I’m pleased to hear it.
That’s perfect for my collection. This is how my main player (MusicBee) is organized.
I sort everything by albumartist anyhow (and in my case it contains what people usually put in albumartistsort). My father worked in a book store for decades and insisted that I sort like this instead of by first name when I started out the collection.
Now it’s actually hitting my cpu a bit while syncing.
I started the sync at 21:12 and it finished at 22:04 (it still says “Schließe Sync ab”, however all the albums are there).
Which makes it 10-20ish percent faster than jellyfin.
The wrong detection of albums with the same name (Maddy Prior Album mixed into the album by John Butler Trio etc.) persists, so it’s not usable for me yet.
On a side note: Is lms supporting external lyrics (.lrc)? If it does it doesn’t seem to carry through to symfonium as songs that have .lrc files don’t show up as having lyrics in the app.
Edit: Forgot to include the system load of the lms container during the sync according to portainer.
I already see it coming: Lms will outperform jellyfin considerably but jellyfin will have lyrics support before lms which will prevent me from switching to lms.
What happens when a song has both real multi value tags and multi value tags that use a delimiter?
For example if a song has 2 artist tags (a real multi value tag) and albumartist1; albumartist2 as well.
Scanning took quite a while.
Syncing to Symfonium started at 19:58.
Finished scanning tracks at 20:39.
41 minutes is pretty fast, jellyfin sync always takes 50min or more.
The “collecting Metadata” step always takes forever (and is optional I think), so I wouldn’t count it (that’s still going at 15% or something around that).
In my experience that’s not the case. mp3tag for example (which I consider to be the best tagging software) only changes the values of tags that you actually edit.
That means that there might be a multi-value tag somewhere that’s not even displayed by default which will lead to delimited multi-value tags set by the user being ignored by lms.
As an example I’ve added a second YEAR tag to these files and saved the change. That did not influence the existing '; ’ delimited artist and albumartist tags.
While mp3tag does have the option to both merge multi value fields into a single field with delimiter (action type merge duplicate fields) and to create multi value fields out of delimited tags (action type split field by separator) both of these are only applied to one field at a time and only if executed by the user. I’m not aware of a global setting that applies to all tags (which probably would be considered unwanted behavior by the majority of users).
Thanks for your feedback!
But why would you let some fields with custom delimiters when updating your file?
My point is that custom delimiters are basically a hack for legacy stuff (because of outdated tagger or because of badly implemented players). I just wanted a way to not apply delimiters on files considered fine. Maybe you are aware of cleaner ways to achieve that?
For your “home” album, are all tracks located in the same directory?
That I can answer from users feedback
Because people have history and can’t / won’t retag all their files to please a server that requires X and may stop being maintained and then they migrate to another server that will require Z.
Automated scripts can destroy all the tags on errors, not everyone can have full backup of all songs. And manual checking / updating is just too time consuming.
My collection in its current form started around 2009ish. I can’t remember which player it was that I used back then (either Songbird or Mediamonkey) but it only supported multi value tags with '; ', so that’s what I used for many years.
Performing any kind of global operation on my library is a massive undertaking so these tags stayed while new additions usually have real multi value tags.
I also saw no reason to do so as MusicBee, Mediamonkey, Symfonium and Jellyfin are all fine with both delimited tags and real multi value tags at the same time.
On principle I agree that real multi value tags are better but there’s no real functionality benefit from converting delimited tags to real multi value tags as long as the players recognize both.
On top of that if you get your files from different sources there might be real multi tags or legacy delimited tags you’re not even aware of somewhere in the extended tags.
Default behavior should be recognizing multi value tags. Optionally I’d just let the user set a custom delimiter and then use both that and real multi value tags, like MusicBee, Mediamonkey and Symfonium do to cover legacy tags.
Every one of the 20ish “Home” albums that got mixed together is in its own directory.
If I had a 26+TB SSD I might be tempted to globally adjust my library but over SMB/NFS simply scanning it into mp3tag would take literal days if it succeeds at all.
I have a hunch that the problem might be in my lms db. To test that theory I deleted the “music” library, which oddly did not delete any of the entries in lms.
That’s when I deleted the persistent lms folder and started over.
I’ll let it scan and report if the merging issue survives a clean install. If so, I’ll send you the files.
Yes modifying libraries is taken into account only on the next scan.
It may take a while to delete a lib because each track from the lib is orphaned, but the track is still here.
This is for example to handle cases where you move your files from one lib to another.
Sounds sensible as a default, however I think there should also be the option to actually purge the db for troubleshooting purposes (or at least a pool tip or something explaining that “deleting” a library doesn’t actually “delete” it until the next sync).
In my case a clean install resolved the merged albums. I checked 5ish of the “Home” albums that were mixed together, now they’re all separate like they should.
The performance of the website is really good, when searching for a song it only takes around 2 seconds until the results are there. Jellyfin loves to think around 7 seconds before displaying anything.
When syncing to symfonium I noticed that it doesn’t display any of my playlists for import. Are local m3u8 playlists not supported yet? I just put them in the root directory of my music library with correct paths for jellyfin/lms and with jellyfin as a source they import just fine.
Another thing I noticed was that a 3500x3500px 12MB cover (as Cover.jpg in the folder) was not displayed in the web version. Are there max file size constraints I’m not aware of?
All in all you’re making great progress. The performance is lovely. If playlists and external lyrics (.lrc .txt) work as well I’ll gladly switch from jellyfin to lms. Keep up the good work.
)
