CR2 and CRW files created are not working with any Raw Editors / Viewers - Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes) - CHDK Forum  

CR2 and CRW files created are not working with any Raw Editors / Viewers

  • 14 Replies
  • 4187 Views
Advertisements
I hacked my Canon SX40 HS with CHDK (00I) successfully, the main intention is to get RAW files.

I tried both CR2 and CRW format in RawTherapee 4.0, RawImageViewer and Canon Zoom browser, none of them could open it.

Just to make sure that the programs are right, i downloaded a sample CR2 file from the internet and it worked fine in all the programs.

Please help!!!


*

Offline msl

  • *****
  • 1261
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
The CHDK RAW format isn't a standard file format. Its a simple image of the sensor. You need also color informations for further processing.

Activate the DNG option in RAW menu and you have a standard file format with color and Exif data.

http://chdk.wikia.com/wiki/CHDK_User_Manual#DNG_format
CHDK-DE:  CHDK-DE links

I tried both CR2 and CRW format in RawTherapee 4.0, RawImageViewer and Canon Zoom browser, none of them could open it.
This is probably the most common question people ask on this forum once they have succeeded in getting CHDK to load and run.   CHDK RAW files are not the same thing as the RAW or CR2 files produced on DSLDR and higher end P&S cameras.  They are simply a dump of the raw information directly from the camera sensor.  They contain no format or size information to tell a PC software package how to interpret the information they contain.

Having said that, some PC software packages can guess the layout on the sensor information in the file based on the file's size if the author of that package has been informed that a new CHDK port has been released  and told of the file format.  Until that happens, DNG format files contain the information necessary for PC software to interpret the image data so its best to use them.

Here's some additional reading if you would like to learn more :

link> CHDK Wiki Page about RAW
link> CHDK Forum thread on RAW
link> CHDK Wiki Page about Raw Software
link> CHDK Forum Board for RAW
link> How do you fix lens distortion with CHDK RAW files?
link> Decoding CHDK RAW images from a new cameras
link> CHDK Tools : rawconvert.c


Ported :   A1200    SD940   G10    Powershot N    G16

Maybe would be good to have DNG support set to "ON" by default in CHDK? It would decrease nymber of such problems;)
if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick


Maybe would be good to have DNG support set to "ON" by default in CHDK? It would decrease nymber of such problems;)
That was actually discussed at some length a month or so ago on IRC.  I'm not sure that the discussion reached any agreed conclusion though.   As for myself,  I tend to agree with the idea - once you have DNG's,  why would you want CHDK RAW files ?  Other than RAW taking less processing in camera and therefore saving somewhat faster.

I think RAW was historically implemented first and DNG added later.  And when you are porting a new camera, RAW is easier to get working first.  Neither of which is a good reason not to make DNG the default.   

Ported :   A1200    SD940   G10    Powershot N    G16

*

Online philmoz

  • *****
  • 3107
    • Photos
Maybe would be good to have DNG support set to "ON" by default in CHDK? It would decrease nymber of such problems;)

I made it default to ON in the 'unstable' development trunk when I implemented DNG 1.3 support.
(Defaults to DNG on, .DNG extension and DNG version 1.3)

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)

I made it default to ON in the 'unstable' development trunk when I implemented DNG 1.3 support.
(Defaults to DNG on, .DNG extension and DNG version 1.3)
Does it also now "work" and bypass the badpixel.bin if that process breaks ?
Ported :   A1200    SD940   G10    Powershot N    G16

*

Online philmoz

  • *****
  • 3107
    • Photos
I made it default to ON in the 'unstable' development trunk when I implemented DNG 1.3 support.
(Defaults to DNG on, .DNG extension and DNG version 1.3)
Does it also now "work" and bypass the badpixel.bin if that process breaks ?

DNG 1.3 does not need a badpixel.bin file so it won't ask you to create one if this version is selected.
If you switch back to DNG 1.1 then it will require the badpixel.bin file.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)


DNG 1.3 does not need a badpixel.bin file so it won't ask you to create one if this version is selected.
If you switch back to DNG 1.1 then it will require the badpixel.bin file.
Will it use a badpixel.bin file if you have one ?

Either way, I think that this is yet another reason to push the stable version to obsolete status and rev the dev trunk to stable status.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Online philmoz

  • *****
  • 3107
    • Photos
DNG 1.3 does not need a badpixel.bin file so it won't ask you to create one if this version is selected.
If you switch back to DNG 1.1 then it will require the badpixel.bin file.
Will it use a badpixel.bin file if you have one ?

No. It sets an opcode in the DNG file to tell whatever file is processing the image to map out bad pixels.

So far it seems only Adobe software has implemented support for DNG 1.3.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)

 

Related Topics