Greetings!

What release of the software are you running, and are you running the developer image? You might want to try
setting up an FTP or HTTP server, or in some other way getting access to the file as saved on the empeg. Then
you can verify that the file is corrupt on the empeg's disk.

Another thought - a while back on this board I saw something with a fingerprint mechanism for MP3s. It might
be possible to get a fingerprint of the source and "on empeg" file, and compare. This could be another way to
validate if the on disk file is corrupt.

Lastly, you might want to try doing a sync of the corrupted files over ethernet, and see if you still see problems.
That would eliminate the USB upload as the cause, if you get corruption on the new batch.

Paul G.
Q# 15189
Status: In queue for a green 36GB Mk2