C1 Corrupt Files with Credo40 Tethering
*Updated 4/23 1pm PST.
I have a whole bunch of corrupt files from a tethered session last night. I was shooting a deep stack using a macro lens (about 95 photos) and of the last 25 raw files at least 5-7 are corrupt when I try to process them. I can edit them in C1 I just can't output them. When I go to process these files C1 Log pops open and I get a date,time and "could not process file".
****Additionally the supposed 'good' files that were processed have corruption as well. When I attempt to stack the processed files in Zerene Stacker it starts generating errors about half way through the 95 or so photos. I am unable to open these same .tiff files in PS or Finder.
Its frustrating that C1 did not warn me that the files were corrupt. Basically half day was wasted... If I knew the files were corrupt I could have re-shot them then and there... The entire stack of photos is use-less because there are missing photos.
I'm not sure if this is a problem with the Credo40 or Capture One or something else computer hardware or cable related. Prior to purchasing the Credo40 I had a P20+ shooting in the same style that never had any issues. They are too many factors to consider here so I would love advice on where to start chasing this down.
Has anyone had this issue or something similar?
I upgraded my system hoping that would fix the problem.
MacBook Pro: 2.66 GHz Intel Core i7 (MId-2010)
System Specs: OSX 10.10.3 (at the time the issue started I was using the previous build)
Capture One : 8.2.1 (at the time the issue started I was using the previous build)
Credo40 DB, Mamiya 645DF+ (2M FW800 Cable)
Some of my thoughts and what I think the problem might be:
•Are there issues with FW800 downloads and the Credo40?
•Are there bugs in C1?
•Is the hard drive or computer I'm tethered to having issues?
I will attempt to reshoot this shot tonight or tomorrow with a different computer and see if I can replicate the issue (hopefully not). Any help in the meanwhile would be greatly appreciated.
I have a whole bunch of corrupt files from a tethered session last night. I was shooting a deep stack using a macro lens (about 95 photos) and of the last 25 raw files at least 5-7 are corrupt when I try to process them. I can edit them in C1 I just can't output them. When I go to process these files C1 Log pops open and I get a date,time and "could not process file".
****Additionally the supposed 'good' files that were processed have corruption as well. When I attempt to stack the processed files in Zerene Stacker it starts generating errors about half way through the 95 or so photos. I am unable to open these same .tiff files in PS or Finder.
Its frustrating that C1 did not warn me that the files were corrupt. Basically half day was wasted... If I knew the files were corrupt I could have re-shot them then and there... The entire stack of photos is use-less because there are missing photos.
I'm not sure if this is a problem with the Credo40 or Capture One or something else computer hardware or cable related. Prior to purchasing the Credo40 I had a P20+ shooting in the same style that never had any issues. They are too many factors to consider here so I would love advice on where to start chasing this down.
Has anyone had this issue or something similar?
I upgraded my system hoping that would fix the problem.
MacBook Pro: 2.66 GHz Intel Core i7 (MId-2010)
System Specs: OSX 10.10.3 (at the time the issue started I was using the previous build)
Capture One : 8.2.1 (at the time the issue started I was using the previous build)
Credo40 DB, Mamiya 645DF+ (2M FW800 Cable)
Some of my thoughts and what I think the problem might be:
•Are there issues with FW800 downloads and the Credo40?
•Are there bugs in C1?
•Is the hard drive or computer I'm tethered to having issues?
I will attempt to reshoot this shot tonight or tomorrow with a different computer and see if I can replicate the issue (hopefully not). Any help in the meanwhile would be greatly appreciated.
0
-
I suggest you send in some raw files to support for review and analysis. They might ask for your log files or whatever they need as well. 0 -
Hi Paul,
Might take me a couple days but I'll get to it. I switched to another computer while I'm sorting this out. So far it seems like an issue with the hard drive on the other computer. I was able to shoot a few hundred photos today with a MacBook Air via USB3 without issue.
It would be great if C1 could flag issues when frames come in if there is an issue with the file. I'll send raw files and see what you guys can do.0
Post is closed for comments.
Comments
2 comments