This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Rockbox frontpage
FS#10441 - USB transfer as Rockbox USB corrupts flac files
Attached to Project:
Rockbox
Opened by Chris (churrell2375) - Thursday, 16 July 2009, 02:44 GMT+2
Last edited by Dave Hooper (stripwax) - Friday, 30 October 2009, 13:55 GMT+2
Opened by Chris (churrell2375) - Thursday, 16 July 2009, 02:44 GMT+2
Last edited by Dave Hooper (stripwax) - Friday, 30 October 2009, 13:55 GMT+2
|
DetailsMany flac files copied to device when connected as Rockbox USB device, rather than original firmware USB device become corrupted.
This also happen with the c200. Unknown if other audio formats are affected. Operating system typically used for transfer is Windows XP 64bit. The problem is not the files themselves, because the original ones from the computer play fine on the computer, or when the files are transferred to the device using the original firmware USB device. However, the files that were corrupted on the device, when played on the computer show signs of skips and pops, but still play through the problem areas. Rockbox skips to the next song when the problems are encountered on the device. |
This task depends upon
Closed by Dave Hooper (stripwax)
Friday, 30 October 2009, 13:55 GMT+2
Reason for closing: Invalid
Additional comments about closing: Problem with the audio files themselves, not a problem with USB/corruption
Friday, 30 October 2009, 13:55 GMT+2
Reason for closing: Invalid
Additional comments about closing: Problem with the audio files themselves, not a problem with USB/corruption
Such a problem should not be limited to FLAC files. It just shows up there because FLAC files are big (giving more opportunities for errors) and the Rockbox FLAC decoder doesn't recover from file corruption very well.
In this case, it might be useful to see how files differ. On Windows you can use "fc /b" and in Unix you can use "cmp -b". Redirect the output to a file or pipe it to the head command, because there may be a lot of output.
I will do some more testing with larger files to see if this will trigger it. So for now I can not reproduce this.
If nothing happens on this task in the next (say) three weeks or so, it will be closed...