Hello everyone!

I have been having a hard time finding a solution to my problem of sorting music from both Youtube music and Bandcamp. I have tried Picard and while it is good I have had problems with it. For example it has made songs shorter (they now end to soon.). So far the only solution I have found is to use Picard and manually review every song I own, and since I have thousands of songs It would take quite long.

I’m using Jellyfin with Finamp to play my music, and sometimes add lyrics via the Jellyfin app when they are missing.

How have you people solved this or similar issues? Does someone have a automated setup that works well?

  • exuAEnglish
    11·
    11 hours ago

    I just started properly tagging new music at some point and now my library is largely tagged correctly.

    For tagging I use kid3, great KDE application for that.

    I also sort my music into a folder layout like this to know where I got it from and potentially upgrade the quality.

    MusicRaw
  - Artist1
    - Bandcamp
      - Album1
    - Tidal
      - Album2
      - Album3
    - Youtube
      - ytrip album
  - Artist2
    - Album1 (not moved to a separate source)
    - Tidal
      - Album2
      - Album3
    - ytrip album

    I then have a script to loudness-normalize (come fight me) all music and write it to another subfolder.
    A second script takes those normalized files and symlinks them into a structure like this:

    Music
  - Artist1
      - Album1
      - Album2
      - Album3
      - ytrip album
  - Artist2
      - Album1
      - Album2
      - ytrip album

    I tried switching to Picard, but for somewhat obvious reasons it doesn’t support my insane structure.

    • jake@lemmy.worldEnglish
      6·
      9 hours ago

      Why not use ReplayGain tags to capture the normalisation information and let your player adjust non-destructively? Of course I don’t care if you do it by actually re-normalising – they’re your files. Just curious!

      • Localhorst86@feddit.orgEnglish
        4·
        8 hours ago

        Depending on what device/software/etc. you use, your player might not be able to read that normalization info. For that reason alone, I still use mp3gain to actually modify my files, I don’t have to worry about whether or not the player will use the replaygain info, or not.

      • exuAEnglish
        3·
        8 hours ago

        That feature didn’t exist when I started and I haven’t bothered to change it yet. Since this also needs support on all clients, it’s somewhat less portable than my solution.

        Edit: Reason 2 I’m not sure how different clients handle the dynamic adjustments