incorrect white balance readings on E-M1 raw files
Hi
I'm currently trialing C1 pro and I am finding that it reads white balance differently when compared to other raw processing software such as LR5 and DXO optics. Every image seems to read higher on the kelvin scale in C1.
Eg: C1 will say its 6550 WB with the Tint at -1.9. the same file in LR5 will read 5300 with no tint adjustment.
The files do look to have too much orange hue to them and the reds are heavily saturated as well. So even if i pull back the WB to match LR5 i have to make adjustments in the red channel on nearly every image.
The RAW files are from the OM-D E-M1 set to auto white balance.
Is this a common issue with .orf files and C1?
Does anyone else have this problem with E-M1 files shot in auto WB?
Love the software but this is a really annoying issue.
Peter
I'm currently trialing C1 pro and I am finding that it reads white balance differently when compared to other raw processing software such as LR5 and DXO optics. Every image seems to read higher on the kelvin scale in C1.
Eg: C1 will say its 6550 WB with the Tint at -1.9. the same file in LR5 will read 5300 with no tint adjustment.
The files do look to have too much orange hue to them and the reds are heavily saturated as well. So even if i pull back the WB to match LR5 i have to make adjustments in the red channel on nearly every image.
The RAW files are from the OM-D E-M1 set to auto white balance.
Is this a common issue with .orf files and C1?
Does anyone else have this problem with E-M1 files shot in auto WB?
Love the software but this is a really annoying issue.
Peter
0
-
What firmware are you running on your M1 ? The firmware has recently been updated, but CO support is currently based on the original firmware. 0 -
I'm currently using V1.4, but this was a problem from when i first purchased the camera with V1.1.
As far as i can tell the firmware upgrades have had no impact on this problem either negatively or positively.0 -
Is there no solution to this problem out there? 0 -
Have you created a support case for this ? 0 -
[quote="NN186445UL" wrote:
Hi
I'm currently trialing C1 pro and I am finding that it reads white balance differently when compared to other raw processing software such as LR5 and DXO optics. Every image seems to read higher on the kelvin scale in C1.
Eg: C1 will say its 6550 WB with the Tint at -1.9. the same file in LR5 will read 5300 with no tint adjustment.
The files do look to have too much orange hue to them and the reds are heavily saturated as well. So even if i pull back the WB to match LR5 i have to make adjustments in the red channel on nearly every image.
The RAW files are from the OM-D E-M1 set to auto white balance.
Is this a common issue with .orf files and C1?
Does anyone else have this problem with E-M1 files shot in auto WB?
Love the software but this is a really annoying issue.
Peter
No solution for you, but you may be interested in this blog article which compares 8 different RAW converters. One aspect checked was the default white balance for each converter starting with the same RAW image. The temperatures are all over the map... I believe he used the same camera as yours for the test.
http://www.nomadlens.com/raw-converters-comparison/2
One thing I notice with C1P7 is that the WB presets seem to be off with my RX100. If I take an image shot in daylight and use the daylight preset instead of the Auto WB from the camera, it will be way too warm. Not useable in fact. With Adobe Camera RAW on the other hand I often find the Daylight preset is more accurate than the Auto WB, and I use it.
I also notice that even when I use my camera Auto WB the color cast is bias toward red-orange compared to Adobe Camera RAW, which I consider very neutral and accurate.0
Post is closed for comments.
Comments
5 comments