BrianHalcYoN
Leading Member
You are just confirming that I am not crazy.
--
D90, D60
Nikon 18-55, 55-200, SB-600, 10.5/2.8 Fish, 105/2.8VR; Sigma 30/1.4
--
D90, D60
Nikon 18-55, 55-200, SB-600, 10.5/2.8 Fish, 105/2.8VR; Sigma 30/1.4
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Well, comparing an out-of-camera(native) jpg with a ViewNX NEF-to-jpg converted image . . .As eNo mentioned in the OP, he's comparing a JPEG created from a NEF by View NX:I say again. You may not have had the raw button enabled in viewnx and were therefore seeing the jpeg thumbnail of the raw. IOW, not the recorded jpeg itself.
....with a straight (no edit) conversion in ViewNX to JPG at the highest quality setting.
Well, don't take this too far. If all you want to do is convert RAW-to-JPG in ViewNX, then it would appear there isn't much to be gained (still digging into that, though). However, if you need to adjust exposure or white balance, doing it on a 12-bit or 14-bit image will more often than not come out far ahead of the compressed 8-bit JPG data. In fact, except for being in a pinch, I would not recommend WB adjustments in JPG format at all.You are just confirming that I am not crazy.
I second that recommendation. Image 'salvage' only.Well, don't take this too far. If all you want to do is convert RAW-to-JPG in ViewNX, then it would appear there isn't much to be gained (still digging into that, though). However, if you need to adjust exposure or white balance, doing it on a 12-bit or 14-bit image will more often than not come out far ahead of the compressed 8-bit JPG data. In fact, except for being in a pinch, I would not recommend WB adjustments in JPG format at all.You are just confirming that I am not crazy.
Here is the rest of the story......I for one am convinced that, with the D5000, JPEGs converted from Raw using ViewNX (without adjustment) are superior to JPEGs created by the camera. Sharper, more detail, more depth to the color. I haven't spent a lot of time testing why that is, but it's noticeable.
When I got back the D5k from the first recall, I mistakenly left it on the JPEG Fine setting that the service technician had used. Those images stand right out in the collection on the hard drive, so much so that I had to notate them so as not to waste time wondering what went wrong with the usual excellent IQ.
The explanation that has been offered, to the effect that the desktop computer has more horsepower to process my preferred settings, makes sense, but I wonder if it's the whole story.
Leon - I'm concocting a couple of test cases that may expose the weakness in the in-camera conversion -- or not. Case 1: high-dynamic range image. Case 2: Wide range of tonality from dark to light in one or two colors. The 1st case should be easy to set up. The second, I'm not so sure about.My advice to eNo is to question everything until we know the truth. Right on, eNo! I would like to see your results. My attention span is too short to do this myself.
It has always been a puzzle to me, and maybe this is the time to find the reason, but I can never imagine how a smooth blue sky similar to the one in your signature picture gets to be posterized and blotchy. It has high values and should not show noise or steps. Could it be that the fundamental curves as I have noticed before having only 64 unique values are not effectively curved out to be smooth? Could that perfect gradient in nature just be the perfect test target to show the weakness in shortcut math? Maybe new car fenders would be a good test target if you can't get back to that lake.Leon - I'm concocting a couple of test cases that may expose the weakness in the in-camera conversion -- or not. Case 1: high-dynamic range image. Case 2: Wide range of tonality from dark to light in one or two colors. The 1st case should be easy to set up. The second, I'm not so sure about.My advice to eNo is to question everything until we know the truth. Right on, eNo! I would like to see your results. My attention span is too short to do this myself.
I full understand your process, and yet I query as to why you then even raised this thread at all? I said that the jpeg and jpeg from nef, IF converted with ViewNX will give the same result.Yes, I'm aware of that, which is why:
1) In the camera, I enabled RAW+JPG-fine.
2) When I press the shutter, the camera records a RAW file and a JPG file.
3) Later in ViewNX, I open the RAW file, and convert it to a second JPG file. At this point whether there was JPG embedded in the RAW is immaterial because ViewNX converted the actual RAW file to a JPG file .
4) Now I go to my JPG viewer of choice ( not ViewNX ) and open both JPG files for viewing: the one I took in the camera, and the one I converted from RAW in ViewNX.
So you see, whether I'm pressing the RAW button in ViewNX is, again, immaterial, because I am comparing JPG-to-JPG in a separate application. Essentially what I am doing is comparing the quality of conversion in the camera vs. the quality of conversion in ViewNX -- and for the cases I've tried, I see little if any difference.
This alone begs me to ask the question, WHO/HOW did they (side by side comparisons) get to THEIR (obviously different from your) results?I could've sworn I've seen side-by-side comparisons of RAW+JPG (fine) shot in camera, where the JPG from the camera doesn't look as good as the RAW converted in ViewNX
Well, comparing an out-of-camera(native) jpg with a ViewNX NEF-to-jpg converted image . . .As eNo mentioned in the OP, he's comparing a JPEG created from a NEF by View NX:I say again. You may not have had the raw button enabled in viewnx and were therefore seeing the jpeg thumbnail of the raw. IOW, not the recorded jpeg itself.
....with a straight (no edit) conversion in ViewNX to JPG at the highest quality setting.
:|
Sorry, probably a slightly different way of saying the same thing.
Wow, i got lost in the depths of this then, i guess i thought he was just comparing his own in-camera produced jpg with the same NEF converted to jpg by ViewNX.BUT, the point is he is comparing HIS results to SOMEONE elses' (I could've sworn I've seen comparisons) without actually linking us to THOSE results.
In effect, his (eNos') experiment just proves that a nikon converted nef vs a nikon generated jpeg is indeed similar (I have said that before too).
This is the point of this thread as I see it, nay?
Nikon's software applies your settings, just like the camera, but the actual processing isn't quite identical. The raw converter usually produces a more "crisp" image than the in-camera processing, although I think recent cameras have narrowed the gap somewhat.Isn't ViewNX using the same camera settings to produce the JPG? If so, then they should be identical. Am I missing something here?
I second this request. I only shoot JPEGs as well. I've read enough comments from "RAW only" shooters to appreciate their belief that, with the correct PP, RAW will "always" result in a "superior" image. The last poster on this thread (except for me) is one of those RAW shooters. I'm not going to say that their beliefs are just that, beliefs (opinions for their own reasons) but you know how it is in the photographic world. Opinions for some are fact.Hi eno...
I dont shoot RAW...and never seen a RAW shot from my D90...not even loaded ViewNX.
However I would like to see a comparison of your efforts..............could you shoot RAW+jpg fine...then convert the RAW to jpg with no adjustments.....
Crop the same section at 100% from both...say at 1280 wide..and post the converted RAW file, plus the OOC jpg for comparison...
Then do the same with a converted RAW, but this time with all the adjustments required to get the best out of it...that is WB, sharpening etc....And then compare your efforts, plus the untouched OOC jpg by using your best "picture control" parameters...
Much appreciated
--
Cheers
Rik