Hello. I have the problem that my exported JPEG Images looks so different than the preview of my Image. I read that i have to swap my setting to sRGB but it wont help. My Image is still a bit blue although i edited it.
Please help 
Welcome…What version of DT??
Do you use the dehaze module…if so try without it just to see
Also depending on your settings there is a mode to do high quality reprocessing when you export. If this is set to yes then you should enable the matching preview mode in the darkroom view (its one of the icons at the bottom of the screen…assuming you are on a current version…If you don’t like that then you can set the export option to no for that parameter and use the default downsampled preview… then that combination would be a better match
Does any of that change what you see…
Is your monitor calibrated?? Is it likley to be quite different in gamut from sRGB… this could also be something to check out…finally how are you assessing the jpg…back in DT or some other viewer…if so ie the other viewer you need to be sure that it is setup right as well…
Finally sharing an example can be very informative for others to aid you…
Hello! Thanks for your quick response. Im using the newest version 5.0 of DT. Indeed im using Dehaze Module. Im going to try without that. My monitor should be calibrated. → So it wont any changes, when i switch from “system display profile” to “sRGB”.
Okay, i removed de Haze Removal Module and it looked better. But i need the Dehaze Module to have the perfect image. is there a option to keep that Module and have the same result?
You can try to blend the dehaze module in lightness blend mode it might not impact color as strongly and still give you the look of dehaze. Also what profiles are you changing…just to confirm…output profile for your export and you should use your calibrated color profile for your display profile or if you are confident that you have it set properly in your OS then system will be okay for your display profile…
I am not sure if the dehaze presets in the diffuse or sharpen module will achieve what you desire. Probably worth a look.
1 Like
In my experience it’s a different look but the tone curve just set to blend in subtract and then a really low opacity of like 8 to 10 percent can sort of be a similar look…
1 Like
The haze removal module is fundamentally broken in ways that are almost impossible to fix. Can you perhaps share the raw file as a PlayRaw to see what others can make of it? Post a screenshot of your darkroom preview as an example of what your desired look is, and mention that it should be done without the haze removal module.
@kofa, can the methods in RT or ART be ported to DT?? I know that @agriggio Alberto took a few things from DT and was able to integrate them into ART… in this case can it go the other way or is it likely not possible and or that is not the issue that needs to be fixed wrt what the dehaze module is doing to output??
1 Like
I don’t know, I’m not a darktable developer. What I found on Github were comments by @hannoschwalm , namely:
https://github.com/darktable-org/darktable/issues/17358#issuecomment-2307552479
https://github.com/darktable-org/darktable/issues/17358#issuecomment-2307728568
It calculates some intermediate data from all available areas and does some maths using this intermediate stuff.[…]
The problem is: the mentioned intermediate step happens in the preview pipe iirc.
While I’m sure it could be fixed somehow (I don’t think the export pipe also runs the preview - if it did, there wouldn’t be a difference), I trust that Hanno knows what he’s talking about (more than I trust myself 
).
1 Like
Thanks I was thinking you would recall the threads… I wonder then is it only a problem when exporting with HQR on, ie the issue would be that with the two modes would need different data from dehaze to be accurate??
I think I read that AP in order to simplify things took the downscaled elements for export out of Ansel so it only does the equivalent of HQR exports now…
Based on what I understood, no, but what each pipeline does is not clear to me. The manual lists:
- the center image (full) pixelpipe;
- the preview pixelpipe
- the export pixelpipe
- the thumbnail pixelpipe
- preview pixelpipe for the second window
On the page about the pipelines, we see:
- the export pixelpipe processes the full-sized image at full quality
- the thumbnail pixelpipe is optimised for speed […] multiple small images […] lighttable or filmstrip […] thumbnail generation
- the standard darkroom pixelpipe […] only processing the pixels that are visible on-screen
- a cut-down darkroom pixelpipe […] used while interacting with some darkroom modules that display the full image with overlays (like retouch, crop and liquify) […] excludes some long-running modules (like diffuse or sharpen)
It also notes that
In order to overcome the above limitations within the standard darkroom pixelpipe, you can enable high quality processing mode in the darkroom view. This mode processes the entire image using the export pixelpipe
And in the code the HQ processing option is called full_preview, even though it affects the centre view → full pixelpipe / standard darkroom pixelpipe, according to the first / second list. I guess it shows the UI and dev terminology are not completely aligned – and that I have no clue, which is of course my own fault.
1 Like