C1 3.6 not seeing in camera color ballance

Comments

7 comments

  • Dudenbostel
    To follow up on my post, I looked at the images shot under tungsten on another computer that installed 3.6 pc on and the problem still exists. The images look as though they had no color correction even though color was captured off of a gray card and set in camera. I can only conclude there is a bug with the 20D and captured color from tungsten light.
    0
    Comment actions Permalink
  • kcphoto
    I've had the same problem. I always use a grey card and am shooting with a 20d. Daylight balanced flourescents look fine, but tungsten is very yellow. Hope this problem is recognised and gets fixed right away, as it is a pain.
    0
    Comment actions Permalink
  • Ulf Liljegren
    Tungsten colour temprature is quite different so you will need a profile to follow the colour temprature (can ofcourse be corrected with grey balance) for all the higher end cameras there is a tungsten profile but the lower end we only provide a generic profile which should work quite well in flash/daylight.
    0
    Comment actions Permalink
  • kcphoto
    I've had capture one LE from the beginning and never had to worry about this before. My 10d always worked fine with Tunsten Light .the preview and pic needed no tweeking. (I have a 20d now)I do far to many photos to have to worry about this stuff. I just want it to work.You have obviously dumbed down the latest version
    0
    Comment actions Permalink
  • Flashram_Peter_AUS
    Why such minimal support for what PhaseOne perceives to be lower end cameras. Everyone pays the same price for the software, supposed to be across the board total camera support with both the LE, SE (version 3.6 only) and PRO versions.

    For people like me, that can afford to get a 10D or 20D and those that get the Rebel, you are saying we only get partly profiled cameras for WB etc.

    This seems totally unfair. If you are really only supporting the higher end cameras like Canon 1DsMKII for example and having complete profiling for that camera and only passifying everyone else who have say 300D, Canon 10D (which does have a few profiles, all be it left over from previous versions) and 20D as examples, then this is a very strange way to do software development.

    I wonder how many other Software Developing companies only support high end users, who can afford to pay squillions for things and also supply cut products for others. I don't think there would be many.

    PhaseOne needs to learn very quickly, it is that masses that support the product, with a smaller percentage, being the higer end product purchases. Get this right and supply complete profiling for all the cameras support. Surely it isn't that hard to supply the profiles. Look at the comments about the Tungsten not being supported in the profiles.

    It really sucks.
    0
    Comment actions Permalink
  • NN160077UL11
    I see the same problem with 10D in CO 3.6SE.
    The problem has nothing to do with tungsten though (unless there's a difference between the 10D and the other cameras). What happens is that CO does an auto white balance for images shot with in camera custom white balance. This explains why tungsten shots are yellow and daylight shots are close to what you expect.
    You can easily check this by clicking on the WB presets \"as shot\" and \"auto\".
    If you then click on the preset \"camera custom\" (which is highlighted) you should get the correct white balance.
    Again this is with a 10D but I would expect that it is the same for the 20D and 1DsII.

    This is definitely a bug in 3.6.
    0
    Comment actions Permalink
  • Charles Beasley
    As nordstrom says, it has nothing to do with tungsten or camera profiles. v3.6 simply doesn't recognize incamera Custom White Balances for either the 10D or 20D. I have spent an entire afternoon proving this [at least to my (dis)satisfaction:]

    http://www.pictureflow.com/forum/showthread.php?t=6665

    At least with the 10D there is a workaround in that as Nordstrom discovered, for that camera there is a setting in the White Balance drop down menu called \"Camera Custom\" which will set the image to the correct CWB. This setting is missing from (at least my version of) 3.6 for the 20D. So unless you keep the image of the neutral object that you used to set the incamera CWB, for the 20D, you're screwed.

    What v 3.6 does when viewing images that were shot with an incamera CWB is to do a Auto White Balance.
    0
    Comment actions Permalink

Please sign in to leave a comment.