• Avid Amoeba@lemmy.ca
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 month ago

    I do. It could be this:

    After the migration it is recommended that you perform a full scan through the admin dashboard. We have observed that for some users, some elements might not work properly otherwise (e.g parental ratings). As of RC8 a scan for missing metadata may be required for music libraries to function properly. The first scan after the migration might also take quite a bit longer than usual, though subsequent scans should be as quick as before.

    From the release notes.

    The last messages in the log are from music lib scanning. I’m leaving it be for now.

    • ragebutt@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 month ago

      Interesting. I will say music is the weakest point of jellyfin db. Mine is currently good but I nuked my db for the new db style in 10.11 and created a new db, mainly bc of issues within music library. But this went back to like 10.9 and were probably from me fucking around in the db manually to try and override tags. I’ve since retagged my music as it was just the easier solution (artist ft artist got me all fucked up, I hated having 900 entries for like 1 artist who did frequent collabs)

      https://github.com/jellyfin/jellyfin/issues/15070

      This is the issue thread re the very long scanning after upgrading to 10.11

      Edit: also one thing I learned from the db editing and again from the 10.11 migration is that the jellyfin db can get “stuck” in such a way that nothing I can find will overwrite db entries, even manually opening the db in an sql editor (which makes me think there are hard to find tables I could never track down but db stuff is not my forte so I dunno)