Hey all, I just happened upon a trove (~100gb) of MP3s from when I was a sweaty teenager with a DSL line and a 5-disc ripper. Anyone have recommendations on OSS toolsuites to begin indexing/sorting out the files? Everything apparently got flat dumped from a directory structure to a folder. There’s metadata in about 90% of the content - ~10k songs to sort through shouldn’t be too rough with hashing.

I’d be more than willing to seed once everything is in a happy place, there’s probably a few hundred studio cuts of songs that haven’t seen the light of day yet.

  • ProgrammingSocks@pawb.social
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 hour ago

    Music isn’t torrents in 2026. We’re all on Soulseek. You could certainly start there but make sure it’s tagged well.

    • Jo Miran@lemmy.ml
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      10 hours ago

      Now that’s a name I haven’t seen in a loooooooong time. Excellent tool last time I used it…about 15 years ago.

      Good recommendation.

    • veee@lemmy.ca
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 hours ago

      I used this very recently to clean up multiple iPod backups (80-120GB) from my high school days. You still need to delete duplicates manually, but the software makes the task immensely easier.

  • TwilightKiddy@scribe.disroot.org
    link
    fedilink
    English
    arrow-up
    5
    ·
    9 hours ago

    Picard mentioned in the other comment is great. If you want a more manual approach, on a Linux machine you can use exiftool to extract the metadata and then use that information to do whatever, e.g. organise them by folders.

    A bit long code block
    $ exiftool -j 救世主.ogg 
    [{
      "SourceFile": "救世主.ogg",
      "FileName": "救世主.ogg",
      "FileSize": "3.4 MB",
      "FileType": "OPUS",
      "FileTypeExtension": "opus",
      "MIMEType": "audio/ogg",
      "OpusVersion": 1,
      "AudioChannels": 2,
      "SampleRate": 48000,
      "OutputGain": 1,
      "Vendor": "Lavf60.9.100",
      "PictureType": "Front Cover",
      "PictureMIMEType": "image/jpeg",
      "PictureDescription": "",
      "PictureWidth": 0,
      "PictureHeight": 0,
      "PictureBitsPerPixel": 0,
      "PictureIndexedColors": 0,
      "PictureLength": 102126,
      "Picture": "(Binary data 102126 bytes, use -b option to extract)",
      "Totaldiscs": 1,
      "Genre": "J-POP",
      "Encoder": "Lavf60.9.100",
      "Releasetype": "single",
      "Album": "救世主",
      "Language": "jpn",
      "Date": "2023-05-07",
      "Title": "救世主",
      "Totaltracks": 1,
      "Artist": "月詠み",
      "Duration": "00:03:20.868000000",
      "TrackNumber": 1,
      "Tracktotal": 1,
      "Disctotal": 1
    }]
    
    • Pomal@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      4
      ·
      9 hours ago

      My sushi roll experience was going to be iterating the byte-string headers and grabbing out anything of value, so essentially this. My hope was that there was a solution present to reduce the hand-rolling… tbd but it appears that Picard is a viable option based on yours and others commentary/upvotes

  • unitedwithme@lemmy.today
    link
    fedilink
    English
    arrow-up
    3
    ·
    9 hours ago

    You’re saying each mp3 is ~10MB? That’s probably 320Kbps quality, so should be at least better than topical 128Kbps.

    My maths: 10,000,000B ÷ 240 seconds song = 41,666B(yte).

    41,666B × 8(bit) = ~333,333b

    333,333b ÷ 1,024 = 325bps (thinking kibibit vs kilobit depending on your IS)

    (again, rough numbers)