![]() But this may mask other cases of data corruption where WPD_OBJECT_SIZE is correct, but the stream is too short/long. ![]() Or it could ignore the mismatch and copy the full stream, no matter how long it is. Unfortunatly FreeFileSync doesn't have good options to remedy this situation: It could behave like Explorer and only copy WPD_OBJECT_SIZE bytes, but that's deliberately copying corrupt data. I ran a consistency check on both jpg files and the Explorer version is cut short missing data:Ĭopied with Explorer.jpg 1944 x 1944 24bit Exif N 843831 Premature end of JPEG file Ĭopied with FFS.jpg 1944 x 1944 24bit Exif N 844085 Īnd indeed, visually comparing both images, the Explorer version is missing pixels at the lower right. However FFS reads 844085 bytes until reaching end of stream.įreeFileSync's version seems to be the correct one, the file really is 844085 bytes long: Both WPD_OBJECT_SIZE and WPD_RESOURCE_ATTRIBUTE_TOTAL_SIZE of WPD_RESOURCE_DEFAULT report an expected file size of 843831 ![]() From all the data gathered so far this looks like bug or data corruption of the MTP device: Thanks for the screenshot of the WPD Info tool.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |