... But the images has already gone through at lest one process before you get to it.
Recording DNG, the data is not being recorded in its native format.
Hi Dom,
What you're overlooking, in all your objections to TIFF is that TIFF is a
container format, so that you can store anything you like in it - bitmap, jpeg, vector data, whatever. I see no reason why RAW shouldn't be stored in it.
AFAICT the only process that .DNG files direct from the GX-20 have gone through, is that they have had a "wrapper" placed around them, basically with EXIF data added and not much else.
I downloaded one of the sample .DMG files from
the Photography Blog review of the GX-20 (I used the
one of the purple flowers) and ran `tiffdump` on it:
Code:
$ tiffdump samsung_gx20_02.dng
samsung_gx20_02.dng:
Magic: 0x4d4d <big-endian> Version: 0x2a
Directory 0: offset 8 (0x8) next 0 (0)
SubFileType (254) LONG (4) 1<1>
ImageWidth (256) LONG (4) 1<160>
ImageLength (257) LONG (4) 1<120>
BitsPerSample (258) SHORT (3) 3<8 8 8>
Compression (259) SHORT (3) 1<1>
Photometric (262) SHORT (3) 1<2>
Make (271) ASCII (2) 20<SAMSUNG TECHWIN Co.\0>
Model (272) ASCII (2) 20<SAMSUNG GX20 \0>
StripOffsets (273) LONG (4) 1<104232>
Orientation (274) SHORT (3) 1<1>
SamplesPerPixel (277) SHORT (3) 1<3>
RowsPerStrip (278) LONG (4) 1<120>
StripByteCounts (279) LONG (4) 1<57600>
XResolution (282) RATIONAL (5) 1<72>
YResolution (283) RATIONAL (5) 1<72>
PlanarConfig (284) SHORT (3) 1<1>
ResolutionUnit (296) SHORT (3) 1<2>
Software (305) ASCII (2) 24<GX20 Ver 1.00 \0>
DateTime (306) ASCII (2) 20<2008:07:09 11:23:01\0>
SubIFD (330) LONG (4) 2<103190 103568>
34665 (0x8769) LONG (4) 1<103914>
50706 (0xc612) BYTE (1) 4<00 00 0x1 0x1>
50707 (0xc613) BYTE (1) 4<00 00 0x1 0x1>
50708 (0xc614) ASCII (2) 13<SAMSUNG GX20\0>
50721 (0xc621) SRATIONAL (10) 9<-8.02406e+06 8.14361e+06 4.15949e+06 -2.67264e+06 5.37242e+06 -1.37421e+06 -2.09459e+06 6.34419e+06 -7.99309e+06>
50722 (0xc622) SRATIONAL (10) 9<-7.55174e+06 8.14361e+06 879872 -5.49478e+06 5.37242e+06 -5.89594e+06 -4.12595e+06 6.34419e+06 4.46438e+06>
50727 (0xc627) RATIONAL (5) 3<1 1 1>
50728 (0xc628) RATIONAL (5) 3<0.628993 1 0.771084>
50730 (0xc62a) SRATIONAL (10) 1<-32512>
50731 (0xc62b) RATIONAL (5) 1<1>
50732 (0xc62c) RATIONAL (5) 1<1>
50734 (0xc62e) RATIONAL (5) 1<1>
50740 (0xc634) BYTE (1) 102400<0x53 0x41 0x4d 0x53 0x55 0x4e 0x47 00 0x4d 0x4d 00 0x63 00 00 00 0x1 00 00 00 0x4 0x4 0x1 0x2 00 ...>
50778 (0xc65a) SHORT (3) 1<17>
50779 (0xc65b) SHORT (3) 1<21>
$
If you Google for "BitsPerSample"
you will see that this indicates the number of bits per component, and if we run `tiffinfo` on the file we will see:
Code:
$ tiffinfo samsung_gx20_02.dng | grep -i rgb
Photometric Interpretation: RGB color
$
IE: the DNG contains RGB information at 8 bits per channel. This would appear to be stored under the
DNGPrivateData tag, which "provides a way for camera manufacturers to store private data in the DNG file for use by their own raw converters".
So I see
absolutely no reason whatsoever to suppose that the GX-20 is doing anything more nefarious than dumping the values obtained by its sensors straight out into the DNGPrivateData section of the DNG file.
I have to say that I am somewhat surprised by how accessible I found this DNG file's data. I'm no programmer, but I would consider this an
extremely readable & usable format. I have only glanced casually at this file, but I get the strong impression that it mightn't take me more than a day or two of hobbyist hacking in my rusty old C in order to get a bitmap out of it. Having downloaded a second file, I do see some "anomalies" - large sections of repeated "255,255,255", "0,0,0" and "192,0,0,6" in the DNGPrivateData of both DNGs - but I see no reason to believe these suspicious, and am sure they would be explained by further (more competent) analysis. The first two would clearly seem to indicate black & white, but it seems like the pattern repeats too many times to indicate blown-out highlights or an underlit area of the image.
Out of curiosity I looked at some of the .CR2 raw files from my Canon 350D:
Code:
$ file Pictures/2009/04/2009_04_15/IMG_1383.CR2
Pictures/2009/04/2009_04_15/IMG_1383.CR2: TIFF image data, little-endian
$
So I can't help wondering if you're going to find that
all so-called RAW files are in fact accursed TIFFs. :bonk:
Your posts in these two threads seem a little terse to me, so perhaps I have somehow got the wrong impression. Please excuse me if that's the case.
Stroller.