Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exported images have changed exposure #18189

Open
dshot92 opened this issue Jan 11, 2025 · 5 comments
Open

Exported images have changed exposure #18189

dshot92 opened this issue Jan 11, 2025 · 5 comments

Comments

@dshot92
Copy link

dshot92 commented Jan 11, 2025

Describe the bug

Exported images differ from the imported one, even without modifying them.

I just want to convert my raw .nef images to .tiff to ble able to use them in hugin, but the converted images do not keep the same settings as the original ones.

The 3 images i am using now are a bracket of exposures, and the exported tiff present a neutral exposure

Steps to reproduce

  1. Import raw .NEF images
  2. Export images as TIFF

Expected behavior

Expected result should look the same as the imported images

Logfile | Screenshot | Screencast

1
2
3

Commit

No response

Where did you obtain darktable from?

downloaded from www.darktable.org

darktable version

5.0.0

What OS are you using?

Windows

What is the version of your OS?

Windows 10 Pro

Describe your system?

No response

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

GTX 1050

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

@ptilopteri
Copy link

ptilopteri commented Jan 11, 2025 via email

@ralfbrown
Copy link
Collaborator

By default, darktable applies the opposite of the in-camera exposure compensation. Uncheck the box in the exposure module.

@dshot92
Copy link
Author

dshot92 commented Jan 11, 2025

By default, darktable applies the opposite of the in-camera exposure compensation. Uncheck the box in the exposure module.

Thats fix it, but it does not seems right, especially since i never even opened that tab.

Why is this the default behaviour?

If the option is applied, why does it not show in the previews?

@kmilos
Copy link
Contributor

kmilos commented Jan 11, 2025

why does it not show in the previews?

https://docs.darktable.org/usermanual/4.8/en/lighttable/digital-asset-management/thumbnails/

The lighttable initially shows embedded OOC thumbnails, not what dt would produce.

@wpferguson
Copy link
Member

You have your processing set to scene referred.

When you open a new image in darkroom, the default modules are applied. When you return to lighttable, the thumbnail is updated.

When you export an image it is processed by the pipeline to build the image for export, hence the scene referred default modules are applied, thus the exposure changes. Since the image wasn't opened in darkroom, lighttable doesn't know to update the thumbnail. Export takes long enough, you don't want thumbnails updating while you're doing it.

If you want the same exposure on export for an image you just imported, select none for processing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants
@wpferguson @kmilos @ralfbrown @dshot92 @ptilopteri and others