Photo looks like it has been blown up by 400% at 100%

Hi all.

Any idea what is going on in here? Left is darktable without any modules. Right is Lightroom. Both at 100%. I have checked the settings, can’t find anything that would do be the cause. As you can see, you can’t even see the individual pixels in darktable. It’s as if I have zoomed in a few times. Screenshot taken by the way, no exports. If I export, it looks the same. It seems like it’s using a generated low res version while editing? Might have a feeling it could because it’s a CRAW from my R6II.

Latest insider edition per 6/13/2023 (4.3)
Windows 10

Thanks in advance!

please help to help you: provide the image, the xmp and maybe the darktablerc file

Well for sure you have some color noise reduction in LR and likely something more applied to the image than the starting point in DT but as others said if you share that image and the xmp we could likely give you some insight…

I will upload those later for you, gotta go. (been thinking, could it be because the photo was shot in C-RAW?)

Version of darktable and the OS as well

it’s seems like the left is a thumbnail view

Is the r6-ii even supporter ? Is craw even supported? (I don’t know).

It almost looks like Darktable reads a preview jpeg / heic from it instead of raw data.
For my curiosity: is the demosaic module available and on? (To check if it has Bayer data or regular RGB data).

The samples from RPU, tagged with c-raw, can be opened, although R6 II support doesn’t seem to be completed yet (if I understand github correctly). So, WB, black/white points, colours, whatever, might be inaccurate, but it propably shouldn’t be that pixelated.

I think Darktable has a list of camera models for which it uses libraw instead of rawspeed to open them.

Might be completely wrong, but i remember something like this.

And it might explain why a new camera but with extremely similar file format might be completely different in how it’s treated.

libraw is just used for canon cr3 since there’s no cr3 support in rawspeed yet

Based on model, or just on file extension?
If the 2nd… Then I’m all out of ideas.

it’s the file format that counts -cr3 isn’t decoded by rawspeed yet