Redcrown wrote in post #15260599
I'm not familiar with OSX Image Capture or the FW800 Delkin reader. But a little search led to something interesting.
The Wikipedia entry for OSX Image Transfer says it works "with no need for drivers." Don't know if that's true, but if it is then it's possible that the OSX Image Capture software, by bypassing the Delkin driver, is unable to keep up with the high speed of the Delkin reader. That could lead to "buffer overflows" which means dropped bits or bytes which means corrupted data.
So, you may be right that the OSX Image Capture software is the culprit, when combined with a such a high speed reader. That would be strange. Buffer control problems were common in the dark past of 10 years ago. But I'd expect anything developed in recent history to not suffer that problem.
Your repeated tests should confirm. If you continue to suffer corruption using OSX Image Capture, but have no such corruption under other transfer methods, then the finger points directly at OSX Image Capture.
Might be interesting to transfer using OSX Image Capture, but straight from the camera via a USB 2.0 connection. The USB 2.0 camera connection is pretty slow. If OSX Image Capture keeps up with that connection (no corruptions), that would be a good indication of buffer control problems in the OSX Image Capture + Delkin path.
I think we were on the same page. I finally had time to test out all the options that were corrupting minimal files.
I have done this-
I imported the entire CF Card (Kingston 32GB 133X Elite Pro)- [~200 files including RAW files]
In my first OSX Image Capture import that included 7 corrupted files.
- I have now found that ZERO damaged RAW files in that same import (Which I didn't even test the first time since I generally browse the jpegs first rather looking at doubles until its necessary)
Of course, at this point, The first import VIA dragging files off the CF and there was ZERO corrupted files (RAW and JPEGs).
The tests were-
I imported the entire CF 6x w/ OSX Image Capture and the results-
- The first test that left me with 9 corrupted files but which was strange... It came with the same 7 corrupted files and plus 2 extra corrupted files-
IMAGE LINK: http://smg.photobucket.com …view¤t=_J6A0069.jpg IMAGE LINK: http://smg.photobucket.com …view¤t=_J6A0064.jpg The strange thing is- 4 import runs w/ Image Capture that didn't cause any corrupted files at all or RAW files.
Dragging files off the CF-
- I dragged files off 5x. Not 1 single file is corrupted out of all.
Conclusion-
It seems that only 2/6 imports [OSX Image Capture] had corrupted files out of all.
Dragging files off the CF is working flawlessly and 5/5 imports left with ZERO corrupted files.
I went through all RAW files (luckily I didn't take many shots this time since it was my first time out with the 5D3) and they were all fine.
I am planning on researching through the mac forums to see if anyone else had issues with Image capture since its obviously to be blamed for the corruption.
- I am also unsure if perhaps the CF card could be causing it but its the only CF card that I have. I feel that its not the problem. I would have expected (in my thinking) that the 5D3 would have given me errors while shooting but there weren't any issues, right?
I still feel that the corrupted files were taken w/ higher f/ rather f/4. It may be a coincidence in this case. I would have expected a very large amount of corrupted files. Very strange.
Short story- Dragging files off the CF is the most reliable option so far.
