Do you have evidence to back this up? (not being argumentative, just interested to know to understand for myself)
I think you are wrong there, especially if using a custom white balance.
Having done quite a bit of testing to achieve a white balance for shooting with welding glass as a neutral density filter, Adobe's RAW engine does not have enough latitude to correct the white balance and shows up its limitations.
Yes it is an extreme situation, but does show that there can be reasons for getting it right in camera, rather than relying on post processing after to correct.
Here's a comparison between using Canon's dedicated DPP software and ACR.
RAW or RAW ??? by Steve Bennett, on Flickr
....
When processing I like to find a mediun neutral grey and try the dropper on that. Some times that works well, if the light is constant over the entire scene. But even a known neutral grey pair of trousers can have a cast thrown into them by a near coloured object. It can be surprising how far out the colour of a scene can be when a grey is forced into being "numerically " neutral.
Provided you colour vision is good and your screen calibrated probably the nearest you ever get to "real" , is setting purely by eye perhaps helped by trying the dropper on a few greys.
Unfortunately there is no absolute way to measure colour balance. Even a grey card can give an unrepresentative result for the majority of the scene......
Does this not assume that "grey" stays "grey" in any lighting condition?
"grey" will be a lot warmer under incandescent light and a lot colder under shade or cloud - I think that 5600k seems to give the most "real" colours so that images are rendered how they actually appeared at the time.
Nope... I said white balance settings on camera will be transferred to the raw program via metadata, but white balance is not a fixed value in raw, and can be adjusted post shoot with impunity.
The OP was referring to cutom picture modes, like vivid, portrait etc... they have no affect on the raw. Nikon's raw programme may pass the settings through as metadata (never used it) but NOTHING you do to a raw file is permanent, and can be changed any way. You can "zero" a raw file with one click.
As for your welding glass shoot... take a test frame with a grey card next time, you'll be surprised.
If you're saying that Raw files are actually free of software corrections, tweaks and other in-camera interference, then that's not true.
If you're saying that Raw files are actually free of software corrections, tweaks and other in-camera interference, then that's not true. It's never been completely true and today all kinds of modifications are made to Raws and baked in with no adjustment possible. Noise reduction at high ISO for example, and lens aberrations corrections.
Leica got a red face recently with the launch of the Leica T, claiming high optical performance from the lens without software assistance. Turns out it's just the opposite, with a lot of software help that's coded into the metadata and cannot be disabled. http://www.dpreview.com/previews/leica-t-typ701/7
Does this not assume that "grey" stays "grey" in any lighting condition?
"grey" will be a lot warmer under incandescent light and a lot colder under shade or cloud - I think that 5600k seems to give the most "real" colours so that images are rendered how they actually appeared at the time.
AM I missing something here? If the corrections are hard coded into the raw data, how can RawTherapee access the data without these corrections being applied - or does it use the hard coded data and reverse the effect? Presumably it must, as otherwise the actual, unmodified raw file would be available - even if Adobe don't provide the means to access it.
Of course grey stays grey. Grey reflects all wavelengths equally.. which is why it's grey.
Just use a grey card.. white balance from it. You'll see.
If I were to look at a grey card under incandescent light I'm sure it would have a warmer appearance than if I were to view that same card outside on a cloudy day.
Of course grey stays grey. Grey reflects all wavelengths equally.. which is why it's grey.
Just use a grey card.. white balance from it. You'll see.
A grey card can appear any colour you like, depending on the colour illuminating it.
Why are so many having a problem with this.. LOL
I know.. that's the point. It will NEUTRALLY reflect the same spectrum spread that hits it without ADDING or SUBTRACTING anything from it. Hence it is a neutral white balancing point.
Instead of arguing with me.. just go and try it.
But what confuses some people is what information a grey card gives when it might appear warm.
It was that, that I was attempting to add.
I think you are wrong there, especially if using a custom white balance.
Having done quite a bit of testing to achieve a white balance for shooting with welding glass as a neutral density filter, Adobe's RAW engine does not have enough latitude to correct the white balance and shows up its limitations.
Yes it is an extreme situation, but does show that there can be reasons for getting it right in camera, rather than relying on post processing after to correct.
Here's a comparison between using Canon's dedicated DPP software and ACR.
RAW or RAW ??? by Steve Bennett, on Flickr
You can test a lens with out a camera at all , or mount it on another camera. That will tell you what and how much is being corrected in firmware.
Some camera settings can/will affect the raw file. Things like Nikon's Active D-lighting will cause the exposure to shift affecting the raw file.
And Dark Frame NR also affects the raw file.
But most camera settings (camera profile, WB, NR, etc) do not affect the raw file.
However, they *do* affect the review image and the histogram.
So if you use the review image (jpeg thumbnail) or histogram to judge/set your exposure, then what you see and what you get could be very different. And various raw editors will apply the jpegs settings as "default settings" to various degrees (and based on preferences). I.e. Nikon View NX will (can) apply all of them... but they are not "baked in" (LR only applies WB settings AFAIK).
If you want to achieve a better white balance with a welding glass, one click with levels will produce a more realistic sea colour
And therefore the raw file will be recorded differently than it otherwise would have... the result has been affected (I didn't say "adjusted" if it makes a difference).Nope... It is not adjusting the raw at all... it adjusts the metering. As the manual says, it "Adjusts exposure before shooting" (italics added by me).
And therefore the raw file will be recorded differently than it otherwise would have... the result has been affected (I didn't say "adjusted" if it makes a difference).
Or use a bloody grey card!!![]()
What and then batch process your shots?
If the lighting hasn't changed, yes. Be careful on location though, as lighting conditions can change rapidly, especially at the beginning and end of the day. You can get different colour temperatures literally minutes apart at sunset and sunrise.
The problem with long exposures though is that it can be a pain to do a grey card test if you're into minutes with a 10 stop... as the light can have changed between taking your grey card shot and the actual shot. However... if at any other time of day, or on overcast days, then yes, do a grey card test shot.
Agreed. I'm not sure where the confusion is coming from...Huh? You can do the same by just stopping down in manual exposure..
Agreed. I'm not sure where the confusion is coming from...
The second method is to partially process the raw data in camera, this is often done in response to setting a higher ISO. And can be done either as part of the capture on sensor or later or a mixture of the two.
I'm still confused. I can understand that there is a difference between data as it comes in electrical signals and a file written out to some form of storage media. I can understand that the camera maker controls the format of that file (I believe at least one camera produces Adobe standard .dng files as its raw format). I'm confused as to whether this should be taken to imply that as well as controlling the format in which the data appears, the makers also "massage" the data, which seems to be a different issue.
On the quoted snipppet above, I can think of at least two different things that you could mean - that the signal gain is applied after the data is captured (in which case ISO could theoretically be increased in post processing if the full data available from the sensor were passed on) or that noise reduction is applied to the raw data before it's written. Or perhaps something else I haven't thought of.
I'm still confused. I can understand that there is a difference between data as it comes in electrical signals and a file written out to some form of storage media. I can understand that the camera maker controls the format of that file (I believe at least one camera produces Adobe standard .dng files as its raw format). I'm confused as to whether this should be taken to imply that as well as controlling the format in which the data appears, the makers also "massage" the data, which seems to be a different issue.
On the quoted snipppet above, I can think of at least two different things that you could mean - that the signal gain is applied after the data is captured (in which case ISO could theoretically be increased in post processing if the full data available from the sensor were passed on) or that noise reduction is applied to the raw data before it's written. Or perhaps something else I haven't thought of.
I said it changes "the result"...The confusion comes from you saying that D Lighting "changes" the raw file.![]()
White balance is both a science and an art.
There is technically correct, where colours accurately match reality; and subjective, where they look the way you most like them - both are equally valid.
Agreed.White balance is both a science and an art.
There is technically correct, where colours accurately match reality; and subjective, where they look the way you most like them - both are equally valid.
The subjective side comes into it because of the way we interpret colours, with a our brains applying large amounts of correction so everything looks the same, regardless of the colour of the light source. Technically correct white balance works for that, but not always. Common examples are candle light, or a bonfire or sunset where correct WB just looks wrong.
Then there is an inbetween option where correct WB is just tweaked a bit to make it look nicer - usually a bit warmer often looks attractive. But don't try that with a bride's dress (unless she's on fire).
As a comment, our vision is often quite tolerant of slight colour inaccuracies when viewed in isolation, but very sensitive to it when presented with a series of images of the same subject rendered with slightly different white balance. Ask any wedding photographer that has to cope with everything from bright sun to cloud to shade to indoors under all kinds of artificial light and still come up with a consistent set of images.
Something I've never quite understood...
Why is it that "if you shoot RAW it doesn't matter", when you can change the WB of a JPEG just as easy? Is the outcome really that much better with RAW files?