Hi All, brand new to Beets (first post). I recently installed it via docker, and spent a good few hours setting up the env and my config file. I started the first import yesterday afternoon, and so far it’s working wonderfully!! I’d love to buy the Dev(s) a beer, or 12… This thing is exactly what a geek like me needed to get my library in shape.
I’d like to try and explain a little problem I’ve got; with hopes that beets can help solve it…
It’s quite irritating, and a little comical really…
So my current collection is just over 100Gb; and most of those albums were ripped, by hand, in the late 90’s and early 2000’s, using tools like lame, or abcde (dating myself a bit here). Did my best to keep everything organized, and backed up over the years. At some point, the system I was using to keep everything organized was lost, which is where the problem began…
So lets say I ripped/encoded/tagged a brand new album, from CD, the day after it came out; which produced something like:
Then stored the CD, on a shelf, or milk crate for X years…
(forgetting that I already had it encoded, or loosing track via the aforementioned organization method)
Re-ripped/encoded/tagged the same album, several years later… Resulting in:
(Silly right; In the early years, programs like abcde, or others, didn’t check to see if the file already existed, it just appended to it)
So now, I’ve got a few dozen albums in my library with tracks that are exactly double the length they need to be. The tags on the files are accurate (thanks to beets), the directory structure, naming scheme, etc all look good. But when you listen to the track, it repeats, exactly twice. I hope this makes sense. If someone would like a more detailed example, I’d be happy to find one, and break it down…
Any idea how I’d rectify this?