Save RAW files in DNG format instead of RAW

antoniorc

Can you add "dng via usb" feature for ixus860/sd870 ?

Great Job!!

cedricb

vit40
From my remembering, as I used to make my own experimental raw converter 2 years ago, these four values are simply multipliers for R, G, B , G pixel linear value (divided by 1000). dcraw multiplies every linear pixel value value with appropriate multiplier to get WB corrected values and that's it. After debayerization, RGB value of every pixel is transformet from sensor color space to output color space with matrix operation, using color matrix. There are 2 green multipliers - usually their values are the same, but some sensors have 2 types of greeen pixels (slightly different green filter) and in that case values are different. From my remembering, these 4 values are stored in this form in raw file of every camera and dcraw simply extracts them and uses for white balance

Unfortunately, I don't know how to convert these values to appropriate DNG tag (AsShot Neutral or AsShotXY)

maybe we need to ask Dave Coffin... 😉 dcoffin@cybercom.net

ewavr

vit40
Unfortunately, I don't know how to convert these values to appropriate DNG tag (AsShot Neutral or AsShotXY)

In my experiments if AsShotNeutral tag is (a,b,c) then dcraw reports "using multipliers : 1/a 1/b 1/c 1/b".
If green channels multipliers are equal (it seems correct for a710) WB settins maybe can be embedded in DNG (I can make test version to verify this).

ewavr

antoniorc
Can you add "dng via usb" feature for ixus860/sd870 ?

In #644 this feature added to a610, a630, a640, s5is (dps, thm->dng) and ixus860 (cr2->dng).

Is somewhere available compilation log for autobuild (to quick fixing errors like in #643)?

PhyrePhoX

sent to you in pm.

ewavr

ewavr
In #644 this feature added to a610, a630, a640, s5is (dps, thm->dng) and ixus860 (cr2->dng).

Damn! #644 also contains errors :'(
Must be fixed in #645.

PhyrePhoX
sent to you in pm.

Thanks.
It seems that GrAnd's autobuild server also works now (Compilation reporti, build 0.8.10, revision #644).

vit40

ewavr

vit40
Unfortunately, I don't know how to convert these values to appropriate DNG tag (AsShot Neutral or AsShotXY)

In my experiments if AsShotNeutral tag is (a,b,c) then dcraw reports "using multipliers : 1/a 1/b 1/c 1/b".
If green channels multipliers are equal (it seems correct for a710) WB settins maybe can be embedded in DNG (I can make test version to verify this).

ewavr,

check dcraw code, procedure parse_tiff_idf

FORCC cam_mul[c] = 1 / asn[c]

Well, I'm not an expert in C and it's hard to read coffin's very compact code, but I think that this confirms your conclusion above

ewavr

Attached patch for "embedded WB".

embed_wb.patch

2.67KB

hotvedt

hotvedt

oversky
Is there any tool available that can convert an uncompressed DNG to a compressed DNG?

I am 99% sure that "Adobe DNG Converter" does this....

Now i am 100% sure. I have tried it on dng-files from my a540, and adobe dng converter compresses them (and maybe updates thumbnail too?).
-
One small note: The DNG-files now shows and can be copied via explorer.
However, when i select all files, press delete, then only the jpegs goes away. When i re-select the remaining DNG's, then delete, they appear to go away, but still remains on my card.
This behavior looks like the "misc"-folder that is also visible in explorer.
Is this an issue with the windows driver?

A_Str8

I've been struggling for a while, trying to view my raw files through the USB connection on my Vista machine. When I was almost ready to give up, I tried on XP, and found that the files showed up with no problem. Does anyone know why they wouldn't show up in Vista? Is there anything I can do to fix this?

rhen84

I have the same problem. I can't upload my crw/dng pictures via camera. I can only download it with a card reader.

ewavr

Build #666 (magic number 😀) - added DNG to RAW conversion in file browser local menu (if somebody wants to develop/average/subtract DNG files). IMHO, conversion in opposite direction is pointless.

PhyrePhoX

wouldnt it make more sense adding a feature that allows average/subtract/sum dngs directly? and then develop the resulting dng?
because right now, for example if i want to average 10 dngs, i have to convert 10 dngs to raw, then average them, then develop the resulting file.
the other way would save at least one intermediary step. but of course this also adds a lot of code overhead (but we *could* get rid of the CHDK raw format alltogether in the long term?)

reyalp

Another thing that would be nice would be to just save chdk raw + dng header in different files.

This would speed up DNG shooting (no byte swap) and you could have a command that's merges them into a DNG on the camera, or do it later on a PC.

Of course, there's a question of what you should actually put in the DNG metadata of, for example, an averaged raw 😳

Howdy

Hello!

I am wondering why the ewavr patch is commented out in:
http://tools.assembla.com/chdk/changeset/658/trunk/core/dng_hdr.c

He reported this very important find in
https://chdk.setepontos.com/d/156/317/topicseen.html#msg26212

Do you know if the idea of ewavr is being worked on?

ewavr

1. this feature is tested only for one camera model (a710).
2. no interest from users/developers.
However, everybody who can compile CHDK yourself can test it.

MartinBudden

PhyrePhoX
wouldnt it make more sense adding a feature that allows average/subtract/sum dngs directly? and then develop the resulting dng?

I would advise against averaging or summing dngs directly, presuming by dng you mean files containing the camera sensor output in mosaic (eg RGBG) form. This is because that, unless the images are precisely aligned, this is liable to produce false color artefacts. As far as I can tell *all* the software that supports averaging, summing, stitching etc (see Stacking Software - CHDK Wiki) demosaicks the sensor output before stacking for this reason.

It is of course possible to stack mosaic form images, but there has been very little research in this area (see http://www.duke.edu/~sf59/TIP_Demos_Final_Color.pdf)

Martin

fudgey

MartinBudden
I would advise against averaging or summing dngs directly, presuming by dng you mean files containing the camera sensor output in mosaic (eg RGBG) form.

That's what all the RAW average functionality of CHDK has been doing for quite some time...

fudgey

Actually I'm quite interested in getting RAW images with camera WB without having to resort to DNG, I just have near zero knowledge about all that RAW develop whitebalance/color matrix stuff so don't really know what to expect.

I'm guessing most people who read the post didn't even understand what the post was about... 😳

ewavr

fudgey
I'm guessing most people who read the post didn't even understand what the post was about... 😳

Currently camera WB settings are not stored in DNG file - if we choose in RAW converter WB setting "As shot", converter ignores it and uses "auto" WB.
With this patch (of course, if it works correctly) if we choose in RAW converter WB setting "As shot", converter can read camera WB setting from DNG (daylight/cloudy/.../any custom WB).

p.s. If we don't use "As shot" WB in RAW converter, this patch is not necessary.

« Previous Page Next Page »