-
Notifications
You must be signed in to change notification settings - Fork 1.8k
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
badfiles: config options/command for fixing files #3126
Comments
Sounds like a good idea! Have any leads on fixer commands for other formats? |
Nothing compiled for now... For .flac and .ogg files, supplying a script that decodes and reencodes while preserving metadata should work for some errors. For .ogg the procedure is described here, for example. |
Ogg Vobis is a lossy format, and re-encoding the files will will lead to quantization errors and thus an audible loss of quality. Maybe it is possible to use |
Just having an option to set the command for fixing the files would be great. In my case, I create a par2 file for each song on import. I would set the "fix" option to run a par2 repair on it. |
Repairing files doesn't normally work imo. You'll get a skip where it has removed the audio piece that is corrupt. I'd rather not have a bad file, than have a poor file in a music collection. Just my 2p |
How about a separate config entry for commands to fix bad files instead of just listing them. Also one could possibly run a separate command (for example
beet fix
orbeet bad -f
) to fix every file in the library instead of just checking.Suggested config structure:
The text was updated successfully, but these errors were encountered: