When it comes to checking for corrupted files, what would be the difference between these? Is there any benefit on using one over the other?
I tried “check” but I got:
C:\Users\REDACTED\Unorganized\Unorganized>beet import -C "M:/Media/Audio/Perfume/level"
** error loading plugin check:
Traceback (most recent call last):
File "c:\users\REDACTED\appdata\local\programs\python\python36-32\lib\site-packages\beets\plugins.py", line 254, in load_plugins
namespace = __import__(modname, None, None)
ModuleNotFoundError: No module named 'beetsplug.check'
check an external plugin that doesn’t ship with beets? If so, you might consider asking the author who maintains it. (And that might also explain why you aren’t finding it installed on your system.)
Ooooooh, that makes sense. I see now it was included under the section for plugins written by the community. I saw no instructions on how to add the plugin so I assumed it was included.
If you could do a quick glance, could you make any guessing on it being significantly different than the bad files plugin? Talking about the recognition process itself rather than the configurations available.
Hmm… I’m not an expert on this, but it looks like a primary difference may be that beets-check can store checksums in the database. This can help you detect when another tool, or even your hardware, corrupts your files. The
badfiles plugin doesn’t do that; it just runs off-the-shelf validation tools
Thanks for that. It’s not something I’m interested in so I I’ll try the badfiles plugin instead.
Badfies is great. If only I could find a checker for AAC files!
I finally got around trying and this, but I get:
badfiles: command not found: mp3val when validating file: [redacted]
I tried specifying the location like this:
But it resulted on the same message.
I see nothing on the guide about how to to install mp3val (on Windows), so any help would be appreciated.