LibRaw 0.17-Alpha3 and LibRaw 0.16.1

Both stable and testing branches of LibRaw are updated due to vulnerability found in Dave Coffin's dcraw.c code.

Download updated LibRaw versions here:

LibRaw 0.17-Alpha1

After approximately one year of continuous development LibRaw became stable enough to receive a new version number.

LibRaw 0.17 (Alpha1), available at download page:

  • More metadata parsing/extraction:
    • XMP packet extracted (if exists)
    • DNG Color information parsed
    • GPS data (partially) parsed
    • EXIF/Makernotes parsed for used optics (for both RAW files and DNG converted by Adobe convertor).
  • Exif/Makernotes parser callback (called for each processed tag)
  • Sony ARW2.3 decoder:

    LibRaw 0.16 Release

    LibRaw 0.16-Release changes (since 0.15.x):
    • Support for new cameras:
      • Baumer TXG14
      • Blackmagic Cinema
      • Canon EOS 70D, C500, S120, G16
      • Fujifilm X-M1, X-A1, XE2, XQ1
      • Hasselblad Lunar, Stellar
      • Leica C, X VARIO
      • Nikon D5200, P7800, D5300, D610, Df, 1 AW1
      • Nokia Lumia 1020, 1520
      • Olympus E-P5,E-M1, STYLUS1
      • OmniVision OV5647 (Raspberry Pi)
      • Panasonic LF1, GX7, GF6, GM1
      • Pentax K-50, K-500, Q7,K-3
      • Richon GR
      • Samsung NX300, NX1100, NX2000, Galaxy NX (EK-GN120)

    LibRaw-contrib repository

    New LibRaw-contrib repository is added to LibRaw's GitHub account.

    This repository is for code, contributed by LibRaw users, but not included into main LibRaw source tree.

    For now only one project is present in the repo:


    This program converts a raw image-(such as canon's cr2 or nikon's nef) to a tiff image. It accomplishes this using the libraw library available at It emulates the dcraw -D -4 -T command. It has only been tested using canon CR2 files.

    Displaying L channel in Photoshop

    Once in a while one may want to adjust L channel viewing it separately. The rub is that to do this without using extra layers one needs either to use grey Lstar profile as grey working space in Photoshop Color Settings (Cmd/Ctrl-K), or to switch on Show Channels in Color in Photoshop Interface Preferences (Cmd/Ctrl-K). Otherwise the brightness and contrast of the L channel display are wrong.

    Here are some screen shots to illustrate why one might care.

    Here is a b/w image in Lab:

    Festina Lente

    For quite some time we were suggesting that floating point implementation of demosaicking algorithms allows for higher quality results. Incidentally, some programmers who vigorously argued for years insisting integer processing is quite sufficient are now starting to code their demosaicking in floating point too. Here is a comparison of the results of original AHD demosaicking algorithm implemented using floating point and integer arithmetics.

    Bayer moire

    With the existing diversity of RAW converters and their algorithms, there is the problem of choice: which converters are better (and for which purposes). An evident methodology is often encountered in internet forums: take one or several images, process them using different converters/algorithms/settings and compare them visually. The result often looks like this: image P should better be processed using algorithm Q, and image A is better handled by algorithm Z with option f+.

    Moreover, it is simply wrong to analyze things in terms worse or better . The correct formulation is closer to/farther from the initial image .

    The problem is that here we deal with a complex system, which includes

    1. The photographed object and light.
    2. The light path in the camera with lens aberrations and light scattering within the camera.
    3. The sensor with all construction features: anti-alias filter, color bayer filters, microlenses, etc.
    4. In-camera processing, both analog and digital.
    5. And, yes, also the RAW converter in question.