5D mkII raw file problem
Hi,
I have been testing Capture One 4.8 with my new Canon 5D mkII and I am having big problems with developing raw files. Before capture one loads up the previews for my images, they appear normal. However, as soon as the previews are loaded, they become extremely over contrasted and saturated, even though all the controls are at zero.
It appears that capture one is interpreting the files badly, cutting off almost two full EV stops off the highlights, and only showing a narrow part of the raw's dynamic range. Even with the contrast at it lowest setting, a correctly exposed image (with space left on the right side of the in-camera histogram) appears completely blown out.
Canon's DPP outputs my files normally. Capture One reads the raw files from the original 5D mk1 normally.
Does anyone know what could be causing this ? Is it due to a bad ICC file ? I am using 5D mkII generic on a mac pro with osx leopard.
I have been testing Capture One 4.8 with my new Canon 5D mkII and I am having big problems with developing raw files. Before capture one loads up the previews for my images, they appear normal. However, as soon as the previews are loaded, they become extremely over contrasted and saturated, even though all the controls are at zero.
It appears that capture one is interpreting the files badly, cutting off almost two full EV stops off the highlights, and only showing a narrow part of the raw's dynamic range. Even with the contrast at it lowest setting, a correctly exposed image (with space left on the right side of the in-camera histogram) appears completely blown out.
Canon's DPP outputs my files normally. Capture One reads the raw files from the original 5D mk1 normally.
Does anyone know what could be causing this ? Is it due to a bad ICC file ? I am using 5D mkII generic on a mac pro with osx leopard.
0
-
I would suspect either your monitor profile or your output profile. Try to change either one and see what's happening. If you are running trial of CO4 Pro, verify the Proof Profile setting in the View menu. It should default to Selected Recipe. 0 -
Thanks for the quick reply.
I have checked the profiles, nothing seems wrong. I am outputting to Adobe RGB.
None of the raw files from other cameras I have tested have this problem. I have compared results with raw files from a P45+, a P25, and the original 5D. Capture one previews and outputs those files normally.
I don't think the problem is display related, the histogram actually appears as heavily clipped at each end on a correctly exposed image. Opening the same image in DPP shows the histogram with space at each end (no clipped blacks or whites).0 -
Based on your latest information, the issue seems more 5D mkII related. Having this camera myself, I have not encountered such a problem. As you mentioned in your first post here, you might suspect the 5D mkII generic profile. You can reinstall the program (install 4.8.1 if you do not already had it installed).
Other options are exchanging image file (another 5D mkII) or Mac. I might provide an image for download. I was thinking of the firmware version of your 5D mkII. CO4 is less forgiven compared to other converters like DPP in this respect.0 -
Capture One 4 Pro (latest version) crashes when loading 5DMK2 files, however, a 5DMK2 file exported from Lightroom as DNG opens fine and can be worked on without crash. No other file types cause Capture One to crash. thx ra
P.S. Discovered a corrupted 5DMK2 image file. Once this file was deleted, Capture One did not crash.....0 -
Hi,
It's been a while since my post and I still have not been able to process usable images from 5D mark2 files using capture one (waay too much contrast). but I have had time to do a few tests. I have tried:
-Several different PCs and macs
-Several different versions of capture one, including the latest v5 realease
-Several Canon 5d mark 2 camera models and the original 5D mk 1 camera
On all different versions I get the same results :
-I take a picture with the camera that appears as correctly exposed on the camera screen and camera histogram. At this point certain areas are close to white but there is no highlight warning flashing anywhere.
-In DPP (canon's raw software). the image show up fine, contrast is soft, no highlight information lost.
-In capture one, however, the image is very contrasted : the default white point and black point are set much closer together, crushing highlights (and some shadows). When the "exposure" slider is reduced the histogram reveals that the data is still there, just being cut off by capture one. It appears that I am losing almost 2 stops of information in highlights. The shadows are affected by about as much.
The camera is capable of recording at least 8 stops of data, capture one is only allowing me to output around 4 stops of data at any given time ! Film curves, "contrast" slider, etc. don't help as they only affect the curve's slope and not its black/white point limits. This issue is not screen related (capture one's histogram and highlight warning are showing clipped values). Even the camera's JPEGs have more dynamic range info than what I could process from capture one at its softest settings...
This narrow dynamic range problem does not occur with any digital backs I have tested, though it does with the 5D mk1, only marginally. Could the ICM profile supplied by capture one for the 5D mk 2 be to blame for this ?
I would really appreciate it if anyone could respond to this, I am sure I am not the only one out there who has noticed this issue (many of my colleagues have). Thanks !0 -
I can't imagine what you and your colleagues are doing wrong. You seem to have eliminated any possible hardware issue with your cross-platform multi-camera tests. I'm getting beautiful files in C1 4 and 5 from the 5DMII.
Dave0 -
Create a support case and provide a raw file and a jpeg and we should be able to let you know very quickly what is going on. 0 -
I have a similar issue with Nikon D3x - I get overexposed images in C1. Native Nikon software processes them correctly. I always have to set exposure compensation to -0.25 in C1 with shadows recovery adjusted as necessary, unless the image is underexposed already. I tried different approaches and this one seems to work the best, but it doesn't solve the problem completely, especially night shots are problematic. 0 -
[quote="Alxy" wrote:
I have a similar issue with Nikon D3x - I get overexposed images in C1. Native Nikon software processes them correctly. I always have to set exposure compensation to -0.25 in C1 with shadows recovery adjusted as necessary, unless the image is underexposed already. I tried different approaches and this one seems to work the best, but it doesn't solve the problem completely, especially night shots are problematic.
What ISO do you use? There was a similar problem with Canon at ISO 50.0
投稿コメントは受け付けていません。
コメント
9件のコメント