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

Different export result from the final settings in the darkroom #16683

Closed
Vincent1712999 opened this issue Apr 25, 2024 · 4 comments · Fixed by #16748
Closed

Different export result from the final settings in the darkroom #16683

Vincent1712999 opened this issue Apr 25, 2024 · 4 comments · Fixed by #16748
Labels
scope: image processing correcting pixels

Comments

@Vincent1712999
Copy link

Describe the bug

After exporting the image, the result differs from what I see in the darkroom. I have tried exporting settings from the "Intent" property (perceptual, relative colourimetric, image settings, etc.) but nothing works.
dt_screeshot
dt_export
image

Steps to reproduce

Darkroom-->Export

Expected behavior

No response

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

flatpak

darktable version

4.6.1

What OS are you using?

Linux

What is the version of your OS?

Fedora 39

Describe your system?

No response

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

NVIDIA GeForce GTX 1660, 550.67

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

No response

@ralfbrown
Copy link
Collaborator

What modules are you using? Screen display works with a downsampled image for speed, and while most modules attempt to compensate for the reduced resolution, several are known to produce somewhat different results on the downsampled image (local contrast, tone equalizer, diffuse and sharpen, etc.). You'll know that this is the problem if the results match the screen display when you export with size set to screen resolution and "high quality resampling" set to no in the export module.

Current master has a new feature to toggle on full-resolution processing in darkroom view. It's a toggle because when enabled, editing will be just as slow as exporting....

@ralfbrown ralfbrown added the scope: image processing correcting pixels label Apr 25, 2024
@todd-prior
Copy link

I second what @ralfbrown mentions...set it to no for HQR and it will look more like the screen preview. Also don't worry about rendering intents with the default srgb profile as it doesn't support them you will get the same result. If you do want to see that then download one of the srgb profiles from color.org...they will support outputing to the differnet intents...

@Vincent1712999
Copy link
Author

Thanks, @ralfbrown and @todd-prior , for the suggestions. I do indeed use the modules mentioned above, but whether I use HQR or not, the output is the same. The darkroom image is much darker, which I want to export in this situation. Can I deliver some other info that will help you understand this problem?

@todd-prior
Copy link

You could share an image and your xmp ... Also how are you viewing the result... maybe color management issue??

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: image processing correcting pixels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants