Corrupt D300 images but ONLY in CaptureOne 4
I'm occassionally getting corrupted images that in the browser have the upper part of the image correct but the lower part from a different file entirely. Zooming to 100% shows data corruption in the lower part of the picture.
This is only happening sometimes, it doesn't seem to be predictible and it is ONLY in CaptureOne 4 (version 4.0.1.14900.14887). Bringing the files into Bridge, Lightroom or Nikon Capture NX shows NO problems whatsoever.
The corruption shows itself no matter where the files are located on the hard drive and when the same files are imported into CaptureOne on my laptop.
Anyone seen anything like this before?
This is only happening sometimes, it doesn't seem to be predictible and it is ONLY in CaptureOne 4 (version 4.0.1.14900.14887). Bringing the files into Bridge, Lightroom or Nikon Capture NX shows NO problems whatsoever.
The corruption shows itself no matter where the files are located on the hard drive and when the same files are imported into CaptureOne on my laptop.
Anyone seen anything like this before?
0
-
OK I thought, I'll try going back to version 4 before the recent update.
Remove CO4. Reboot. Reinstall. CO4 won't start - splash screen appears for a split second then nothing.
I cannot remove .net as it wont let me (other apps dependent on it).
Short of a total rebuild, I'm stuck. Very disappointed with the flaky nature of CO4 so far. I much prefered CO3 but PhaseOne saw it fit not to allow D300 users to use it.0 -
If C1v4 is like 90% of the applications I have dealt with, it will leave files and registry entries behind. Uninstall again, delete any files you find, run a registry cleaner, and then see if you can do a clean reinstall.
Alternatively, you could try a less drastic method before reinstalling again. It is possible that you have a corrupt Capture One.col file in the Capture One Library folder. You can try to move it to another location and restart CO4, to see if that helps.
Good luck.0 -
Hi Dave.
This is what I've tried this morning:
Uninstall CO4.
Search for all registry entries concerning 'phase one' and 'captureone'
Remove any .col files
Couldn't uninstall .net so went back to a Ghost image of a fresh install of XP, just with drivers.
Installed CO4, went through the installtion procedure for .net
Still will not start.
There is something really weird going on here. I've raised a support ticket and attached one of the 'corrupt' files. Hopefully they can come back with an answer as to why only CO4 is messing them up.0 -
Well that all sounds pretty drastic. But on the basis that your original installation worked (somewhat), something must be left on your hard drive to screw up the C1 installation now.
Was the recovery of the Ghost image 'clean' (on a newly formatted hard drive), or did you simply write it to the drive? If it was the latter, traces of the bad install must still be there. If you formatted the drive, I'm stumped, unless you have fallen foul of PhaseOne's esoteric registration system.
Assuming that you did not do a clean reinstall, the .net runtime may be an issue. But, if other things still work with it, it would not be my first port of call. One thing I can say is that you will not have removed all traces of C1 from the Registry. A trial installation of a registry cleaner may help (I use Ashampoo WinOptimizer and Tweaknow RegCleaner Pro, but there are many others out there - just don't let them run in the background, and check any deletions they propose).
You are, I think, allowed two concurrent installations of C1, so it may be possible for you to try installing to another machine on a trial basis; you can delete the registration of that installation in your page on the website later. Another download of the install files might also be a useful precaution.
Hope these ideas help.
David0 -
When Ghost restores a partition image it does so entirely. Everything that was previously on that partition is effectively gone for good. The file table gets completely rewritten so data can't just 'hang on'.
After a few messages back and forth with Phase One support, it seems that Capture One can struggle to handle NEF files when they've been altered in any way by Nikon's own Capure NX software.
Considering Capture NX is written to strictly adhere to the standards of the NEF format - and since Lightroom and other raw conversion apps are quite happy to work on the same 'corrupt' files - it simply boilds down to an issue with Capture One 4. This did NOT happen with Capture One LE so something has changed in the way it works on the files.
I'm still testing to see if I can find a common thread with these 'corruptions'.
The fact is, Capture NX is not corrupting the files at all, but is changing something that is causing CO4 to throw a hissy fit. Any alterations made by Capture NX to white balance, exposure - anything, are typically ignored by third-party raw converters as they all make up their own settings, so why this is now an issue for CO4 is beyond me.
I also haven't got to the bottom of the installation issues, but that's a secondary concern for the moment.0 -
[quote="robg" wrote:
When Ghost restores a partition image it does so entirely. Everything that was previously on that partition is effectively gone for good. The file table gets completely rewritten so data can't just 'hang on' ... I ... haven't got to the bottom of the installation issues, but that's a secondary concern for the moment.
When you get round to it, I look forward to hearing how you get on. I wish I had something further to suggest.[quote="robg" wrote:
... Capture One can struggle to handle NEF files when they've been altered in any way by Nikon's own Capure NX software [which] is written to strictly adhere to the standards of the NEF format - and since Lightroom and other raw conversion apps are quite happy to work on the same 'corrupt' files - it simply boils down to an issue with Capture One 4. This did NOT happen with Capture One LE so something has changed in the way it works on the files ...s, Capture NX is not corrupting the files at all, but is changing something that is causing CO4 to throw a hissy fit.
Now, I believe, we are getting somewhere. I can always be wrong, but, to me, this story has got 'metadata' written all over it. The issue here is probably twofold:- Nikon feel free to mess around in an unusual way with what they are treating as a proprietary data structure;
- C1's handling (and indeed C1 staff's understanding) of current metadata standards and realities is, not to mince words, abysmal.
At the Nikon end, I know that Capture NX supports EXIF (obviously), and also, somewhat problematically, old (IIM)-standard IPTC data. Both of these are embedded in the RAW file. Capture NX does not support XMP metadata, and therefore does not support the current IPTC standard, which is implemented as an XMP schema.
XMP data is not embedded in the RAW file, but resides in a separate 'sidecar' XMP file. This is the way that all current Adobe applications, and a number of others, handle things. They don't worry about changes that Capture NX makes to the RAW metadata , because what they need (including their own settings and a copy of much of the EXIF data) is in the XMP file.
Another issue is that EXIF is a standard designed by (and, I would say, for the benefit of) camera makers. The standard provides for the inclusion of a large block of proprietary data (the MakerNote) in EXIF; this (undocumented) block typically includes most of the shooting data that Phase One will need for RAW conversion (including the items you mention). I'd hazard a guess that Capture NX is changing the MakerNote, and thereby upsetting whatever (possibly inept) reverse engineering Phase One has done to retrieve the data needed for the conversion. It may be that the problem resides in the C1 profile for the camera, in that it possibly makes assumptions that Capture NX invalidates.
You can get a better idea of what is happening to the RAW file by using a utility such as EXIFTool (mouse over for link) to look at the RAW files before and after they have been in Capture NX.
Changing the RAW file to include settings is, in my view, undesirable, and that should be laid at Nikon's door. But I agree with you that the main problem here lies with Phase One, because of their systemic failure to get to grips with metadata in general and XMP in particular. (They may not be alone in this; I have seen similar complaints about both DxO and Bibble, but I don't use those.)
The forum has truncated this post 😭. I'll continue in another one.0 -
To continue 👿 ...
In my opinion, the only sensible way to store image settings for a RAW conversion is in an application-specific schema in the XMP file; many such schemas can co-exist quite happily in the one file. This approach would not only bring a more disciplined approach to the use of metadata in C1 (which might mean that problems such as yours would get identified and fixed before the software is released), but it would also curb C1v4's unhygienic habit of spraying settings and preview data all over the file system.
The last, rather underwhelming, information, I had on this subject was that Phase One were 'considering' implementing XMP, in some form, in C1.
Getting back to your problem, have you tried keeping your RAW images out of Capture NX, e.g by downloading them directly into C1? This would help confirm whether our shared suspicions are correct.
Please for give any tendency to rant in this serialised post. I hope that it is otherwise useful.0
投稿コメントは受け付けていません。
コメント
7件のコメント