you are viewing a single comment's thread
view the rest of the comments
[–] 26 points 1 year ago (7 children)

hey now, they're flac files and painstakingly sorted with the help of musicbrainz picard

  • source
  • hideshow 7 child comments
  • [–] 6 points 1 year ago (1 child)

    I have that too! I also have that one folder of random shit that I've avoided sorting for the last 20 years.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 6 points 1 year ago

    I also have that one folder of random shit that I’ve avoided sorting for the last 20 years.

    pff I have so many folders like that that I have folders for those kinds of folders. I should probably put those folders all into a single folder..

  • source
  • parent
  • [–] 3 points 1 year ago (4 children)
  • [–] 3 points 1 year ago (3 children)

    Why, what does it do better than picard?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 1 year ago (1 child)

    It'll destroy all your painstakingly crafted and curated ID3 tags much faster than Picard. I'm not salty or anything. Anyway, the lesson for me was that music is simply too complicated from a library perspective to trust to highly-automated tools like beets. Picard kind of encourages you to go directory by directory and release by release, and that is a good thing. These days so are does most of the library stuff for newly added things, but I usually end up fixing it all basic to my standard with Picard later.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 year ago

    Yeah, definitely agreed. There are so many edge cases. I tend to put new downloads/purchases in an "intake" dir and then run that through picard, which then saves it at the final local storage path with whatever tags I decide to use

  • source
  • parent