Absolutely YES for both points
I saw that more of an installation failure rather than a development issue, but I get your points. But onus is on me to provide better installation instructions in the future to avoid conflicts with the master release for anyone who wants to use developmental build like this.
Closed the poll. The results:
Thanks to @betazoid, the new code is already available (Anna found a simpler solution than I did, extra thanks for that!).
The updated manual page already lists the controls in that order. All: please check the manual page, it is almost complete now. I’d need your input for the ‘guidelines’ section, and of course general feedback is welcome.
@Eary_Chow : I’d be especially grateful if you could review it, too. I hope I got the part about primaries OK (it’s towards the end), but I’m pretty sure it could be improved.
You can find the manual here: dtdocs/content/module-reference/processing-modules/agx.md at agx · kofa73/dtdocs · GitHub
Version info:
- The code has been rebased on the current master, and includes all changes up to and including:
commit 51fee703c04b697bf5bf3b855d0003e2f0b43d12 (origin/master, origin/HEAD)
Author: Martin Straeten <39386816+MStraeten@users.noreply.github.com>
Date: Sat Aug 30 08:56:45 2025 +0200
Update de.po
to recent pot file
(so has the same mainline changes as master build g51fee703)
- tagged as agx-2025-08-31-15-42
The AppImage: https://tech.kovacs-telekes.org/dt-agx/Darktable-5.3.0%2B272~g1ea31b2f0a-x86_64.AppImage
@priort , @Dave22152 , @MStraeten, please update your builds.
Windows 11 executable: https://www.dropbox.com/scl/fi/lup3jp8hpv4z15bed5hep/darktable-5.3.0-272-g1ea31b2f0a-win64.exe?rlkey=gojueq687db67jiguj9prybxl&st=wvuwowae&dl=0
Please see instructions here and here to install this developmental build and prevent conflicts with your master.
I have just taken Dave’s build and made a “portable” version… Just unzip it and use the run_dt batch file…This just runs dt from the location that you have unzipped it and directs the config to an empty directory that I added called config. Its a simple one line text file that you can view…nothing sketchy.
THe first time you run it it will make a new fresh database/config files in the added config directory and DT will have all default settings…You will see it run through the setup the first time you run it…
Its simply made by installing Dave’s build and then zipping it with these two modifications…
I’ll link to the zip…using it this way should avoid any mishaps but I would still go in and turn off xmp writing before importing anything.
Just delete the folder when you are done testing or want to remove it…
Thanks for the portable version @priort. Just now getting into trying this out, mind checking if I disabled xmp writing correctly?
As I mentioned, I’m just discovering the AGX module. As I understand it, the AGX module’s main function is also to adapt all the colors contained in the scene to the typically inferior rendering capabilities of the display medium (screen or other). The curve represents the module’s transfer function and therefore, probably in a simplified way, the output RGB levels (on the medium) as a function of the input RGB levels (the scene).
I spontaneously assumed that the curve’s interpretation was similar in AGX and in filmic. It would be interesting to highlight the meaning of the abscissas and ordinates.
Explained in the manual : darktable user manual - filmic rgb
The aim is to adapt the tonal range, ensuring a good transition to white, desaturating highlights and avoiding unnatural-looking colours or other artefacts.
As for the graph: for agx, you get the EV readings under the x-axis. On the y, you see the linear output (see the horizontal guide lines). I’m not interested in mimicking the visualisation modes of filmic rgb, I’m sorry. With filmic, I only ever use the default view that shows the whole curve (your 1st screenshot).
Once/if the module gets merged, others can start adding more visualisations if they want.
ok ! i think i understand. Thanks to take time to answer to me ! ![]()
I have been using AGX since the first versions and I have reached a point where going back to filmic or sigmoid seem a step back in time and quality. Thank you for the time and effort you put into this module.
How certain are we that it will integrate a stable version of dt in the future?
The pull request is open. ![]()
It will be merged when it’s ready. I’ll try to keep addressing reported issues and apply suggested improvements.
At this stage I would say that there is 99% chance of being integrated in dt. If stable enough in the coming weeks it will be part of 5.4 otherwise in a future version.
Great news! ![]()
The docs are shaping up nicely! Big thanks to @kofa and @Popanz ! Documentation is a project all on its own!
![]()
All credits go to @kofa I haven’t done much.
You did spend the time reviewing and made suggestions. While I didn’t use much of those verbatim, they did prompt me to rephrase things and to rearrange the text. Believe me, your contributions helped improve the docs.
Everyone is welcome to correct my English, factual errors, to point out omissions and badly written (overcomplicated or potentially confusing) sections. Plus, I’m looking for practical advice to help users get started with the module.
What would you feel you’d give up by going back to sigmoid? Not questioning, just curious. ![]()
There is a huge level of control for both color and tone… and the implementation of the agx curve with the pre and post color modifications to color primaries gives really nice results for almost any situation… someone called it sigmoid on steroids I think…that might be a little strong but I think both the results and the control…
There was once a tire manufacturer with this slogan:
power is nothing without control
This describes it quite good I think. I think 99% of my edits I could do as well with sigmoid. But the level of control in AgX makes it faster and easier to get there.
Still I wouldn’t say that this counts for everyone. Beginners will be probably better off with sigmoid.


