Why aren't we utilizing embedded previews more in Darktable?

[rvietor]

@Igor64

It would be the same for both programs - embedded jpeg is the same size, no matter which program you use to extract ad view it.

@Igor64

@rvietor

If dt wants to show a 1:1 of raw size, it has to process the raw data,

And this was mentioned as big disadvantage by few guys in this topic. No possibility to show 1:1 (pixel by pixel) jpeg in DT, which would be fast and accurate method when evaluating/sorting photos. Processing full demosaiced raw for this purprose is too slow. And, what I mentioned with examples, DT deforms details in “fit to screen” jpeg previews, and when processing raw for 1:1 preview purproses - picture details (especially edges) are even more deformed. (see screenshots - the same bug for Panasonic RW2 and Canon CR2 files).

So - recommended view modes are not only unusable but also make good pictures looking like they were only worth deleting.

I guess I’ll drop out of this discussion, you ignored most of my questions (or misunderstood them?)

Once again, if you ask dt to show a 100% preview(*), then you have to demosaic the raw. dt offers several options for that, but of course it’s slower than just slamming a jpg on the screen. If that is not what you want, stick to a zoom that is acceptable for your embedded jpgs. For my current camera, those are 1616×1080, vs 6000×4000 for full size raw, so 1 px in jpg represents ~16px in raw… Not ideal to see those fine details in the jpg…

And if you use a 4k screen, a jpg with 1080 on the short size must be scaled up to “show in full screen”. Of course that gives the artifacts you showed.

Both of these points you chose to ignore in your reply…

Bye

(*: as dt is a raw processor, it is not illogical that relative sizes are relative to the raw image size, i.e. in 100% view, 1 screen pixel == 1 raw pxel)