Call for extended CR3 samples (all ISO combinations needed)

I hope these CR3 samples from the Canon PowerShot G5 X Mark II are usable:

There is no crop mode on this camera. The minimum ISO level is 125 (no L mode), the highest ISO level is 25600 denoted as H in the camera menus.

1 Like

Does anyone know how to identify a C-RAW vs a RAW file? Is there a metadata field that flags this? Thanks in advance! - J

See @aadm’s exiftool line. “${Quality}” outputs RAW or CRAW respectively

The XnView MP tool (free photo viewer) also recognizes CRAW. It uses Exiftool


You’re kind to share this. I too saw this in Compressor ID, but in @aadm samples both the RAW and CRAW files I examined said “CRAW” for compressor ID. Perhaps the misalignment is related only to those files? Or user error on my side? - J

Actually you should look under Maker Notes\Quality, not Compressor ID. That’s where the distinction between CRAW and RAW is given. My screenshot was misleading, sorry for that.

$ exiftool -Quality test_RAW_ISO_100.CR3 
Quality                         : RAW

$ exiftool -Quality test_CRAW_ISO_100.CR3 
Quality                         : CRAW

Do you need anything from an EOS 6D Mk2?

Hello, here is my full ISO chain for G7X Mark III

Not very artistic, but does its thing :slight_smile:

1 Like

Thanks, fortunately 6D mk2 is CR2 :slight_smile:

Cool, although the file extension is .CR3 now?

Really? We have Canon 6D Mark II samples from 2017 and those are all CR2.

Whoops, my bad, still .CR2

How is .CR3 support coming along - will we see it in the next DT release? or alternatively can we see it now if we compile the devt release along with latest exiv2?

Doesn’t look like it will make 3.6. You can already play with it now though if you pull down rawspeed PR #271, and compile darktable against at least exiv2 built with EXIV2_ENABLE_BMFF=ON

1 Like

Thanks Matt,

I could probably do that if I had detailed instructions, as I can already compile and run the dev releases without problems. However, it would be a bit of an effort.

SO the question is, whether it will do something with .CR3 images that cannot be done with the same image converted to .dng

OK I installed exiv which should be enough.

How do I pull down rawspeed PR 271?

Is this a single command like:
git pull origin pull/271/head ? or
git-pr 271 using git-extras?

Or do I need a lot more understanding of git forks etc?

Here is what I just did:

# clone rawspeed b/c I hadn't done that before
$ git clone
$ cd rawspeed/

# pull the latest commit of pull-request 271 into local branch that I call 'canon_cr3_support'
$ git fetch origin pull/271/head:canon_cr3_support
remote: Enumerating objects: 130, done.
remote: Counting objects: 100% (127/127), done.
remote: Compressing objects: 100% (49/49), done.
remote: Total 130 (delta 83), reused 113 (delta 78), pack-reused 3
Receiving objects: 100% (130/130), 60.57 KiB | 5.05 MiB/s, done.
Resolving deltas: 100% (83/83), completed with 14 local objects.
 * [new ref]           refs/pull/271/head -> canon_cr3_support

# now I just need to checkout this canon_cr3_support branch
# and can start building it
$ git checkout canon_cr3_support 
Switched to branch 'canon_cr3_support'

The relevant section of the GitHub docs:

Another way of doing this is to add cytinox’s repo as an additional remote, fetch the branches from there and checkout their canon_cr3 branch:

$ git remote add cytinox
$ git fetch cytinox
$ git checkout canon_cr3


Thanks for that. Howver I checked out canon_cr3 and got the message:
Your branch is up-to-date with ‘cytinox/canon_cr3’.

exiv2 -V returns exiv2

Now I do git pull and ./ followed by cmake --build etc,etc

but when I run darktable, it won’t import .cr3 images

Any way to test I did it all correctly?

did you build exiv2 with the EXIV2_ENABLE_BMFF option set to ON?