better support for corupted/damaged files
Audacious gives up immediately (or too fast), when trying to decode damaged files. It should keep seeking ahead, until it finds something it can decode. A bit like VLC.
That would minimize the inconvenience of a library with bitrot. It's particularly annoying, when the damage is near the beginning of the file.
#2 Updated by Anonymous about 1 month ago
It's not about recovering anything. The files stay damaged.
I'm saying, it should seek ahead for stuff that it can decode, instead of immediately skipping to the next file in the playlist.
Typically, a file is damaged at a few spots. Audacious should skip those spots. I'm not saying that it should try to reconstruct the damaged parts.
When you read a book, you don't stop reading the book, at the first spelling error you encounter.