RawDigger 1.2.17

RawDigger 1.2.17

Changes/New features

  • Camera support added
    • Nikon D5600
    • Panasonic GX800/850/GF9
    • Sigma Quattro H
  • Support for DNG files with multiple images with different linearization data in one file and Magic Lantern "out of camera" DNG
  • Fixed some problems (display of some old Canon sRAWs, incorrect black level for Sony A350 etc.)
  • Handling of black level tag for Canon (Kodak) D2000C files and Sony A7RM2 files without black level metadata
  • Exiftool updated to version 10.40

RawDigger 1.2.16

RawDigger 1.2.16

Changes/New features

  • Exiftool updated to version 10.37
  • Camera support added:
    • Canon EOS M5
    • Google Pixel and Pixel XL
    • Hasselblad X1D and True Zoom
    • Olympus E-M1-mkII
    • Panasonic DMC-FZ2000/2500/FZH1, DMC-LX9/10/15
    • Samsung Galaxy S7 and S7 Edge
    • Sony ILCA-99M2 (A99-II), ILCE-6500
  • Fixed display problem with some (old) Canon sRAWs

Color Differences Between Cameras

RawDigger. Placing a Grid

When a new camera reaches the market one of the most discussed subjects is if the color it records is the same, better, or worse compared to a previous model. It often happens that the color is evaluated based on the rendering provided by some RAW converter. That is, an unknown parameter, that being the color profiles or transforms that a RAW converter uses for these models, comes into play. Another problem with such comparisons is that often they are based on shots taken with different lenses, under different light, and with effectively different exposures in RAW (while in fact the exposure settings itself may be the same).

Let's have a look how cameras compare in RAW if the set-up is kept very close to the same and the exposure in RAW is equalized.

RawDigger 1.2.15

Changes/New features

  • Exiftool updated to version 10.30
  • Camera support added:
    • Apple iPhone/iPad DNGs
    • Olympus E-PL8
    • Sony DSC-RX100V
    • Canon sRAW/mRAW format for modern cameras (80D, 5D4)
  • Better exiftool subprocess handling
  • Better handling of corrupted Foveon files
  • Additional integrity checks for Samsung NX files

The Three Most Obvious Reasons to Look at RAW and Not Cull Based On Previews

"...Really, why do you even want to look at RAW files? The whole point of RAW is to be processed according to your taste into a JPEG. I never look at RAW files; I never need to. They are loaded into LR, processed, and I look at the processed images.”

FastRawViewer. Pink azaleas. JPEG prevew vs RAW

So here's a question - is it really necessary that one look at RAW when you're selecting RAW files, whether to convert or to present? Isn't a preview enough? You might not know exactly what settings were applied to it, but so what? What's so untrustworthy about embedded and rendered JPEGs and previews? And what's wrong with the preview and histogram on the back of the camera?

All these questions and more will be answered, and we intend on top of that to show how large of a gulf there is between real RAW data and the previews of it.

Very often images that are technically fine are being tossed out, and technically inferior ones are kept. Why? Because people aren't shown the truth about RAW. Here, we intend to show why people need to see and analyze actual RAW data, in advance of choosing which images to discard and which to keep and edit.

How to Use the Full Photographical Dynamic Range of Your Camera

FastRawViewer. Optimally exposed RAW

Consider the following scenario - you've just found out that your camera, at a certain ISO, has a dynamic range of 11 stops. Now, that's all well and good, but how does one go about using all 11 stops? It's not an automatic process, after all. Our answer? Expose optimally for RAW.

To elaborate on that a little, let's start by showing you the consequences of non-optimal exposure for RAW.

Pages

Subscribe to RawDigger RSS