Nikon D2X color balance goofy
Hi,
I'm in the middle of editing and correcting a recently shot job, and noticed that all the images I shot with a preset white balance, where the camera has an external sensor that measures the ambient color temperature, if I make any adjustments to the color temperature in C1 Pro, and then go back to the \"as shot\" value, the as shot value is always the same, 4750K and -200 green. But if I select the auto correction button, it reverts back to my original color temperature and tint.
Can someone please explain why the software is misbehaving?
When I shoot jpg with the same color balancing method, the color is perfect. So I'm pretty sure it's a glitch with C1Pro.
-Catfell
I'm in the middle of editing and correcting a recently shot job, and noticed that all the images I shot with a preset white balance, where the camera has an external sensor that measures the ambient color temperature, if I make any adjustments to the color temperature in C1 Pro, and then go back to the \"as shot\" value, the as shot value is always the same, 4750K and -200 green. But if I select the auto correction button, it reverts back to my original color temperature and tint.
Can someone please explain why the software is misbehaving?
When I shoot jpg with the same color balancing method, the color is perfect. So I'm pretty sure it's a glitch with C1Pro.
-Catfell
0
-
!@()$%_(%&*%^%!
Now the apply settings to selected photos is not working consistiently.
I correct one photo, then select a few similarly lit pictures, press the apply to selected captures button, then make sure all three boxes are checked (white balance, color balance and icc profile) press ok or return, and the other selected photos color temperature and tint do not match the image that the settings are supposed to be copied from.
And while I wait for thumbnails to load, the pictured image in the preview seems to turn the wierd color that I mentioned in my earlier post, then after a second, it returns to what looks like the original color.
C1Pro is makin' me really angry right now.
Anyone out there have similar problems and possible explanations/solutions?
-catfell0 -
Hello
Since you refer application to \"C1\" I presume you are using a older version.
The first versions of Capture One that supported D2x, it did not completely support the D2x's custom white balance.
If you upgrade to 3.7.4 it will support it fully.
This does not explain you second post.
I would recommend that you make a case out of this at http://support.phaseone.com0 -
Ulf,
I am using Capture One PRO, V3.7.4 (v2784)
-catfell0 -
I have the same problems as described. I just opened a support case with the following text:
I'm having a number of white balance problems with Capture One PRO 3.7.4 on Mac OS X 10.4 (Tiger) and my Nikon D2x. They include:
(1) My understanding is that of 3.7.3 white balances are read correctly on D2x raw files. However, there are several instances where the default white balance (I believe all of these are when AUTO WB is used) is way off. It looks nothing like the embedded preview or like the white balance in other applications (Photo Mechanic, Nikon Capture, Apple Aperture, etc.)
(2) Selecting \"As Shot\" for White Balance gives a Color Temperature of 4750 and a Tint of -200 every time for every image I've tried. The image has a distinctlvely green cast (due to the tint). There's obviously something wrong here.
(3) Most aggravating of all, white balance settings are not persistent across program restarts. That is, if I load Capture One PRO and make white balance settings to an image or a group of images, then exit the program and restart it, the images revert to the originally detected white balance. This means that for any image (re)processing I need to go through the white balance correction process again for each image.0 -
I'm not sure if the auto white balance settings is part of the problem.
I never shoot with auto white balance. I either use a custom white balance set with the sensor on top of the camera, which yields excellent results when shooting jpg, one of the built-in camera presets, or if in the studio use a color meter and then manually input my color temp.
I too have opened a support case, but so far all suggestions have had no impact on the problem.
Also, if I change the K and tint values for one image, then attempt to apply the settings of another image onto the first, the first images K and tint values go back to what they were the first time I selected the image, not the values of the second image nor the manually changed values.
!@#$%&&*&(*%$^$!)*%^$%@!@~! 🤬 🤬 🤬 🤬 🤬 🤬 🤬 🤬 🤬 🤬 🤬 🤬 🤬 🤬 🤬 🤬0 -
After some additioinal investigation I've noticed that NEF files that are brought straight in from the CF card do not have this problem. In fact, it appears that the problem originates, at least in my case, from using Photo Mechanic to write IPTC tag information into the NEF files before processing them. If the \"Add IPTC-NAA Resource when embedding IPTC\" is checked when adding IPTC using Photo Mechanic, the file gets corrupted (at least from the standpoint of WB in Capture One PRO).
I also agree, after more investigation, that Auto WB isn't the factor here. Any NEF file that has been altered in the manner described above is affected.
The problem now is how to completely undo what PM has done. It has an option to revert TIFF-based RAW to original, which gets rid of the problem, but of course it also gets rid of the IPTC data. My hope was to tag once in PM, then have those tags carry all the way through the workflow.0 -
I do use Photo Mechanic to rename, edit and caption my images before using Capture One Pro to process, but I have not, until now had any problems with white balance.
-catfell0 -
My apologies for some misleading information posted thus far.
After some additional testing it appears that, in my case, the problem is exclusively caused by (1) using Auto White Balance and (2) writing IPTC data of any form (outside of an XMP sidecar file that isn't picked up by Capture One PRO anyway) to the raw file.
To test this I shot the the same image three times with three different WB settings, the first one Auto. I then applied IPTC data to all three images and then brought them into Capture One PRO. The image with Auto WB had the problem; the other two (one shot with Sunny and the other with Cloudy +3) didn't.
I realize you don't use Auto WB, so I can't say what the problem is in your case, unfortunately.0 -
I am experiencing a similar white balance problem with the D200 in Capture One Pro. I use Auto WB when I shoot. Then I use Photo Mechanic to edit, and apply IPCT info to the files before I use Capture One PRO to process the raw images.
I did a test like you did and did not apply the IPTC data to the D200 images and the color balance was fine in C-1. The TIFF-Based RAW to original option in Photo Mechanic does solve the problem. but it puts the IPTC data in a separate XMP file.
This is a frustrating issue because it disrupts the workflow. I did not have this issue with the D2H.
🤬 🤬 🤬0 -
Hello,
same problems with a D2X and a D200, using C1 in the last version , downloading pictures with picture project and some times using Iview...
Nef files have problems with iview too.
so....i am going on holidays , hoping nikon will work a bit to help third developpers and perhaps the next version will be OK!
happy summer eveybody
Luc0
Post is closed for comments.
Comments
10 comments