Originally posted by Nicolas06 It is not meant for that... As said the Jpeg is just there to get a quick view and heavily compressed to not consume too much additional space. If one use raw format, it should be to get the full dynamic range of the sensor and so more possibility of post processing... If one change the white balance, push a the shadows or want to remove noise, a raw is far better.
But if one is ok with default rendering of camera then it should chose JPEG directly, it is much more practical and higher quality than embedded preview jpeg.
As I said in a previous post, I think this is heavily dependent on the camera. My K200D puts a very high quality JPG in the RAW file.
I don't know about other photographers, but I usually don't know ahead of time that I'm going to need to fix exposure, white balance, etc. Often, I am perfectly
happy with the rendering of the camera, but even if I am, I might not necessarily be happy with a JPG version of it. What if I need a TIFF?
With the K200D, I would always shoot RAW. That way, if I needed to fix exposure, white balance, etc, I had the option. Also, if I got that 1 in a million shot, I could produce a TIFF
version if I needed it from the RAW.
But with the photography I do, much of the time I only need low resolution crops of the images I take for sharing via email, etc. For that purpose, the embedded JPG that my K200D
produced was more than adequate. That camera was slow writing to memory cards, RAW+ was not a realistic option.
If you use a program like FastStone to pull JPG from the RAW file, it's a bit like shooting RAW+ with the JPG of varying quality ( depending on the camera ) stuffed into the RAW file.
FastStone doesn't "extract" the embedded JPG explicitly. When you click on the raw file, it brings up a full screen view of the embedded JPG ( unless you have it configured to render from RAW ).
You can then perform whatever crops/edits/adjustments you like, and when you hit save, you get to choose what format you want to save the result in. If you don't do any edits, then the file that
gets saved is a copy of the embedded JPG.
With my K30, I shoot RAW+. When I open a folder of photos in Faststone, I see 2 copies of each image, one DNG and one JPG. If I click on a DNG and bring it up in the image comparitor with the corresponding JPG,
I'm really comparing the embedded JPG in the DNG with the full JPG generated by the camera. The two look identical, except you can see that the embedded JPG lacks some detail and you can see some JPG artifacts.
It's not too bad. If you're going to be resizing the image down to, you'd probably never notice. Now that I've looked at this more closely, I will probably switch backing to just shooting RAW. Why fill my Hard drive up with both RAW and JPG?
All my old photos that I shot with my K200D are RAW, so I can't do the same direct comparison, but I know that when I "extract" the embedded JPG, it looks almost as good as a TIFF rendered from the DNG by any of the following: ACR, PDCU, Silkypix, or Rawtherapee. For whatever reason, the K200D seems to save a very high quality JPG embedded in the DNG file. Maybe Pentax goofed when they originally made cameras capable of saving RAW in DNG format.
I just checked. The DNG files generated by my K200D are often BIGGER than those generated by my K30 ! The K200D pretty consistently generates 16.1M DNG files. With the K30, it varies. Some files are up over 16M, some are smaller. Worst case, the K30 files are only slightly bigger. This makes no sense - the K30 has a 16M sensor vs the 10M sensor in the K200D.
The K200D is probably always embedding a full resolution JPG in the DNG file. That's the only explanation that makes any sense.