The other day I enabled the database in foobar2000 and added my entire music collection. I noticed it popped up the console and said there were a couple of musepack files here and there that it couldn't scan.

This comes as no real surprise since I've had hard disk crashes from time to time over the years and untold numbers of BSoDs.

Unfortunately, going though one-by-one to find the bad ones isn't feasible since there are about 1200 files to go through, and re-ripping would take forever. Even converting to null output would take about 5 hours, and foobar's console only retains so much data.

So are there any utilities out there that can scan for corrupted musepack files, and possibly other file types as well?

If all else fails, you can still tell foobar2000's console to log its output to a file.

MPCscan?

Search for MPCScan.

Edit: I could vow that other MPCScan post wasn't there 10 seconds ago

Thanks! MPCScan did the trick. Fortunately it only came up with one bad file.

I would have tried foobar's log saving feature, however it didn't say which file was invalid, but just that it found an invalid file.

(BTW... I did do a few searches of the internet and this forum first and didn't get anything meaningful. I kinda feel silly now for not checking the Musepack site first. )

I really miss all the programs being developed by CASE. The guy is a pure god in understanding what people need in order to get the job done.

MPCScan should report back the bad filename, play with it a bit more.

yeah but its some dos prompt window -- isntthere anything that wil csan a whole directory with mpc albums ??

No it isn't. It's a windows gui app. You can drop files, directories, or a combinations thereof. The best thing is that you can drag and drop more than once and it adds to the queue. Nice if you have stuff in multiple locations that you can't select at the same time.

Seconded! These are my favorite programs, the ones that do one thing and do it well. I loathe feature creep in all forms.

jwz's law: Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.

There's both a console and a GUI version of MPCScan floating around. Or atleast there used to be. For recursive scanning you could put the console version plus Sweep in your searchpath, then CMD to your top directory and execute
sweep mpcscan

If I understood this right...?

I've got the MPCScan gui program here if anyone wants it. Just drop your shit onto it and it scans the files for errors. I haven't heard any negatives about it, yet, and after listening to encoded songs it 100% passed, it appears to work fine. I can send it out or give it to the hierarchy here to post it.

It took me a while to find it but here it is. For those of you looking for the Windows version of MPCScan get it here:

http://home.comcast.net/~splatdrums/mpcscan_installer.exe
Cheers.

I have this corrupt mpc on my computer and it states that the stream version is 8.14. ive never downloaded that encoder and could swear they were only on 7.x.

I have a related question, I'm trying to find broken mpc files only I'm running linux.

Flac files were real easy to scan since there is a test option. I'm trying to use mppdec but either it gives no output (--silent) or tons of output=- theres no way to only print errors.

I've ended up doing:
find | grep .mpc$ | while read line ; do mppdec "$line" /dev/null ; done >& output
and then when its done grepping the output... the only 2 errors I've seen are
mppdec: broken frame 8560/9180 (decoded size=7265, size in stream=7271)
mppdec: unexpected end of file after frame 9154/10406

I'm wondering if this is even doing what I want, is mppdec going to find any file errors? I mean its obviously found these 2 errors but how likely are change to an mpc file to result in an error like this?

Oh yea are all mppdec errors prefixed with the 'mppdec: ' I don't want to accidently skip over any other type of errors.

it is probably a presv8 file (presv8 encoded files shouldn't be distributed)

you can get a decoder, just look for 1.95z67


later