Corrupt files using P30 on H1 with H2 upgrade using C1 3.7.8
after shooting last week one third of our images after being captured tethered to a powerbook G4 have become corrupt and will not open in any way. The image files are still in the capture folder and subsequent sub folders, preview, thumbnail. The owner of the camera has sent an email to phase one and has no response so far. I have been trying to work out how to recover these images, instead of a costly reshoot. I have tried the phase one work around i.e. Hex edit with no luck.
Details are as follows
Shot tethered to a Powerbook G4
running OSX.4.11,
using Capture one pro 3.7.8
with a Hasselblad H1 with H2 upgrade
and a phase one P30 back.
The images whilst shooting came up on the screen as shot, including the ones we can no longer open.
One image file was processed @6:45pm after we finished shooting.
Session folder was copied to an external hard drive and the session deleted from the powerbook G4
When the session is opened in C1 3.7.8 only the first nine looks out of 15 are readable.
The image data loss starts at the point at which the only image that was processed out was processed .
I have copied the whole session folder and have tried the Phase one hex edit suggestion on the copied files with no success.
I have tried numerous times with various salvage and recovery tools (disk salvage, data resue II) to recover images from the original laptop the images where captured to as no other work had been done on it.
All I can recover are the images that we can already open.
Please help I am desperate and need your help, or atleast put me out of my misery and tell me that I have done all I can do.
Details are as follows
Shot tethered to a Powerbook G4
running OSX.4.11,
using Capture one pro 3.7.8
with a Hasselblad H1 with H2 upgrade
and a phase one P30 back.
The images whilst shooting came up on the screen as shot, including the ones we can no longer open.
One image file was processed @6:45pm after we finished shooting.
Session folder was copied to an external hard drive and the session deleted from the powerbook G4
When the session is opened in C1 3.7.8 only the first nine looks out of 15 are readable.
The image data loss starts at the point at which the only image that was processed out was processed .
I have copied the whole session folder and have tried the Phase one hex edit suggestion on the copied files with no success.
I have tried numerous times with various salvage and recovery tools (disk salvage, data resue II) to recover images from the original laptop the images where captured to as no other work had been done on it.
All I can recover are the images that we can already open.
Please help I am desperate and need your help, or atleast put me out of my misery and tell me that I have done all I can do.
0
-
Have you tried creating a new session, then moving the raws out of the old session (leaving the side car files behind) to the fresh captures folder?
Or tried opening them in 4?0 -
Hi,
I'm curious about one thing, you said you copied the session to an ext HD, then
said you have tried open them, etc... but didn't mention which computer you are working on.
I agree with the other post about trying a new session, but I would take it farther,
I would try another computer --preferably with the same OS as the capture computer... build a new session in 3.7.8... then manually copy only the RAW files to the capture folder, re-open 3.7.8 and try.
Tim0 -
I used the same OS on a Macpro Quad, Macbook pro and a powerbook G4, all using os 10.4.11. Tried transferring original files and new session, no luck. Tried the Phase one Hex edit, ie. open the first corrupt file in a hex editing program , remove the first 8 bytes till IIII then save as .cap. did not work. I tried removing the first corrupt file and starting a new session, no luck. I could go on, having stared at code for 4 days and going back to test out my theories on the phase one back working with a Macbook pro. ( the data and resource forks are missing from the corrupt files) turns out that it could have been a low back battery paired with a 15' cable. as the shoot went on the battery was not changed on the back and subsequently not all data was transferred correctly as the power ran down and the firewire port on the Macbook pro does not give the back enough juice. Unless someone else knows how to rebuild resource forks on zeroed out data files or has a different solution. it looks like the images are gone and a re-shoot is called for.
BTW I even tried opening in 4.1 with no luck. so i tried replicating the situation with 4.1 re low battery and image corruption occured intermittently also. still is annoying that neither the back nor C1 informed me that that the images where not transferring in a usable form.
thanks for your interest in solving this issue.
cheers.0 -
Sorry, I can't do code very well. But I will check around with a few contacts, if I can find anything of importance I will let you know.
Best of Luck
Tim0 -
Hi,
As we discussed in the support case, if the files were corrupt when transferring to the capture computer form the back , you would have visually seen the corruption as they were coming in in the form of striped images or no image at all, and the files would never have been usable. The corruption in your case occurred later on, most likely during the transfer from capture computer to external drive. The corruption is completely independent of the back and software. The back and software could not have warned you that the files were corrupt because at the time of capture they were not.
When shooting to a laptop, simply set the back to Battery power in configuration and it will not attempt to draw power from the computer.0 -
Please explain. if the files are captured to the HD as fRaw files and visible during capture, then as you say the captured images from camera >digital back >comp > via firewire should be intact and completely readable files at that point.
I was not aware that backwards corruption occured when transferring data? Surely even transferring the images to an external hard drive should not corrupt the original images or am i mistaken?
If the files were corrupted before transfer then at what point could the corruption occur?
Still seems a very strong coincidence that from the point in time which a single image was processed on location all corrupt images came after that.
6:46pm image processed
6:47pm all files after the processed image are corrupt. starting with image names changing from the pocessed image "abc.tif" to "~.tif" then names are in sequence and images unreadable. Has anyone else had this problem. Files changing names. prior to corruption.
C1 is not infallible and it think saying that it purely is a computer or transfer issue is brushing it off a little too quick.
That being said i have had to move on and am back at work, keeping an ever watchful eye on the capture files in the capture folder and the integrity of files as they are captured.
I really only want people who have answers or have had similar issues to reply. this is an open forum for user to user and i think it important to keep it that way and not have blanket statements like "The back and software could not have warned you that the files were corrupt because at the time of capture they were not. " from phase one.
How is it possible to make that statement, i know C1 and P1 have a good product but to say it could not possibly have happened due to a C1 or P1 issue is close minded. I know that they do not want to show any form of liability and that is why a user to user forum exists, so that we can talk about our issues and not feel inhibited, this is a think tank and if you don't want to dive in get out of the water.
Cheers0 -
"6:47pm all files after the processed image are corrupt. starting with image names changing from the pocessed image "abc.tif" to "~.tif" then names are in sequence and images unreadable. Has anyone else had this problem. Files changing names. prior to corruption. "
Please explain... did you change the name from the RAW file or simply process?
I have seen name changes cause problems in the past, rarely when done in the capture software but most definitely if done in the OS.
As coincidental as it may seem, transferring files to another drive can create a corruption should there be any issues with the final destination (HD) or even the connection cable/port to the drive. Stranger things have happened.
But look at this logically... if there is a issue with the DB it will occur again, I would suggest trying to recreate the situation as soon as possible... remove your DB battery and use only the computer as a power source (TESTING not live job), if the failure occurs in the same manner chances are it may be related to the low power situation, that is actually a problem with Apple, not Phase. We have found the need to create a few special products at our dealership because of this low power issue. Place a fully charged battery in the DB and repeat... if problem is gone, well you get the point.
If you don't have a problem during testing it then I would take a close look at that external HD... how often do you preform maintenance on it? Could have a bad sector or one going bad. Just a thought.
You sound like you've tried everything so my suggestions may be a moot point, just trying to help.
Tim0 -
[quote="cjlt" wrote:
How is it possible to make that statement, i know C1 and P1 have a good product but to say it could not possibly have happened due to a C1 or P1 issue is close minded. I know that they do not want to show any form of liability and that is why a user to user forum exists, so that we can talk about our issues and not feel inhibited, this is a think tank and if you don't want to dive in get out of the water.
Cheers
Actually we are not being closed minded, the architecture of Capture One simply cannot write to raw files, it can only read them. Therefore we know that if the files came in properly, then any corruption is the result of the disk itself.0 -
Thanks Tim, i tried to force the issue with 4 hours of testing the
db tethered, low battery, no battery, full battery, on MacPro and MacBook Pro, even my old Powerbook G4 and could not create the same issue, of the images displaying in C1 and not readable. I could however make unreadable images with a low DB battery on MacBook Pro and Powerbook G4. I checked the structure of these files and although the image was black it still had a full resource and data files. I will try transferring those files to the external drive and see if that takes the rsrc data off the images, similar to the original issue. Just looking for answers and i really appreciate your input and stimulus.
cheers0
Post is closed for comments.
Comments
9 comments