Make camera raw preview available to compare with current edit

[Waiwei8k]

Camera raw preview images can be a usefulhint for raw processing. Often they contain sensible colour rendering defaults and are at least a consistent reminder of the scene as shot.

I would like a way to conveniently compare my current processed image to the RAW file's embedded jpg.

This might be a pre-populated snap-shot in the snapshot dialogue (my favourite option), a module which would introduce the embedded JPG into the pixel pipe with all the usual opacity/masking options, an entry in the duplicate manager or whatever best fits the code.

[parafin]

Not sure it's a good idea for general public - there's already a lot of questions "how to get the same result as camera JPEG" even without proposed easier access to it...

[Waiwei8k]

I don't think this will make things any worse, but certainly anyone who does want to match camera JPEG results can use this feature as a starting point. It may be a good way to keep those people happy whilst encouraging them to learn how to drive the tool. Conversely, it's often quite nice to see how much you've improved the picture over the camera's attempt.

[wpferguson]

There is a lua-script, examples/multi_os, that does this. The embedded jpg is extracted, imported, and grouped with the raw for each selected image.

[elstoc]

I like this idea but I wouldn't want it as a separate image in my library (grouped or otherwise). The embedded JPEG is already displayed in the lighttable before you load the image in the darkroom so people can already view it - it's just that the only way to keep it available (in the lighttable only) is to have a separate duplicate version with no edits.

[wpferguson]

The embedded JPEG is already displayed in the lighttable

Only if you leave the preview as the default. If you select half size raw, then this isn't the case.

[wpferguson]

Also, if you've imported the embedded jpg, then you can open it and take a snapshot, then go back to the raw and the snapshot will still be there so you can overlay the snapshot of the jpg over the raw.

[elstoc]

Or it could be an extra option in the duplicate module and you could do the same.

[wpferguson]

The duplicate is a duplicate of the raw image. The embedded jpg is a different image, extracted from the raw, so it's not actually a duplicate.

[elstoc]

It could have its own independent keyboard shortcut and/or button on the bottom of the darkroom then

[aurelienpierre]

Having that in snapshot or duplicate module is not super difficult to do, however, what should we do with cropping/rotation/perspective distortions ?

1. Apply the same distortions on the JPEG thumbnail ?
2. Keep it as-is ?

And if 1., how do we manage inconsistencies between OOC lens correction and Lensfun correction ? They often don't match.

[elstoc]

I'd say we should keep the JPEG unmodified - treat it as we would a "differently-edited" duplicate in the duplicate module. For example, the duplicate module should be able to handle images that have different crops and/or where one image has lens correction enabled and one does not. We shouldn't worry about those inconsistencies.

[Waiwei8k]

The JPG may well already have a lens correction applied in camera, so no need to apply that. An option to match the crop would be nice, but as a very low priority addition. Certainly not required.

[github-actions[bot]]

This issue did not get any activity in the past 30 days and will be closed in 365 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

[Waiwei8k]

Pinging to stop auto-close. I would still like this feature.

[johnny-bit]

I think the best option here would be to use snapshot module for this and on opening image create snapshot from extracted JPEG preview from RAW file. Don't do ANY processing on it. Just thumbnail dump onto snapshot. And hide that behind some option. Would be usable enough IMO.

[github-actions[bot]]

This issue did not get any activity in the past 60 days and will be closed in 365 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

[Waiwei8k]

Just pinging because I don't want this to time out.

[github-actions[bot]]

This issue did not get any activity in the past 60 days and will be closed in 365 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

[Waiwei8k]

Another ping to keep this live.

[github-actions[bot]]

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

[afranke]

I think the best option here would be to use snapshot module for this and on opening image create snapshot from extracted JPEG preview from RAW file. Don't do ANY processing on it. Just thumbnail dump onto snapshot. And hide that behind some option. Would be usable enough IMO

That sounds good and unobtrusive. In addition to that, it could be handy to have a side by side mode similar to culling in the lighttable, but just the snapshot idea would already be very useful.

[TurboGit]

I think the best option here would be to use snapshot module for this and on opening image create snapshot from extracted JPEG preview from RAW file.

This idea would fail short as it would be impossible to align properly the embedded jpeg preview with the RAW processed picture.

[github-actions[bot]]

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

[Waiwei8k]

Pinging to stop auto-close. I would still like this feature.

[ptilopteri]

you already have the requested ability.

duplicate your image remove all edits from the dup view original and dup to compare

[Waiwei8k]

Do you mean duplicate and remove history stack? When you go into the darkroom view, the default stack gets processed and you get the RAW again, so there's no way to put the image on the snapshot viewer stack. Sorry if I've miss-understood your suggestion.

[ptilopteri]

• Waiwei8k @.***> [06-02-24 18:09]:

  Do you mean duplicate and remove history stack? When you go into the darkroom view, the default stack gets processed and you get the RAW again, so there's no way to put the image on the snapshot viewer stack. Sorry if I've miss-understood your suggestion.

Message ID: @.***>

open your image in dt take a snapshot open history panel select "O original" and take a snapshot

and you have both images

or I have no idea your purpose.

-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

[github-actions[bot]]

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

[afranke]

you already have the requested ability.

No. We are asking for the embedded jpeg, which is processed by the camera and stored in the RAW file, not the bare RAW with no edits as you are suggesting. It is shown in the lighttable before any edits are made, and then it is not available anymore. This issue is asking for a way to access it from the darkroom at any given moment, to compare with current edit, as the title says.

[wpferguson]

There is a lua-script that extracts the embedded jpg and groups it with the raw in lighttable, examples/multi_os.

The extracted jpg is not the same resolution as the raw, at least in recent cameras, so overlaying won't work.

[afranke]

I understand this may not be the case for all formats, but my camera (Canon EOS R6) has a full size JPG available (JpgFromRaw for exiftool). We are also not after extreme precision here. The point is to use it as a reference, not to match details.

[wpferguson]

So why not just shoot raw+jpeg?

[Waiwei8k]

Jump though enough hoops and you can do anything, but that misses the point. The real value is having the image easily available with minimum friction. Also, different resolutions could be resolved by scaling the embedded image.

[victoryforce]

The real value is having the image easily available with minimum friction

This will be done soon with the addition of system styles that replicate the processing of specific cameras.

[Waiwei8k]

If it respects the processing settings you have on the camera, that would be a reasonable alternative and a great addition. Sounds like a huge amount of work.

[github-actions[bot]]

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

[Waiwei8k]

Ping to mark as not stale.