Thought so. 
http://tech.kovacs-telekes.org/dt-agx/Darktable-5.1.0%2B801~gae59f735be-x86_64.AppImage
Thanks for testing!
@MStraeten , @Dave22152 , @priort : not a major update, build if you have time, but it’s also OK to skip it.
I’ve tried creating tabs (OK, I tried asking Gemini to create tabs), but it failed, so the UI remains.
Ya sorry I had problems with getting the links to specific images…likely just me overlooking how to grab the link in their site
I love the progress this team is making with the module. I can almost completely edit a RAW file with just this module alone, and the highlight recovery is amazing.
My workflow today normally involves processing my ORF raw files with DXO PureRAW to produce DNG files with no noise and excellent colors. On my Mac, when I open these files in darktable with AGX I get a blank white screen before I reset the module.
If I use the auto tune levels, it produces some strange color artifacts in highlight areas.
Your screenshot shows you have both sigmoid and agx enabled. This should not cause artefacts, but does not make sense.
Which version are you using? I don’t see the checkbox that was added in the build wise post you replied to.
I am using version darktable-5.1.0+704~g1acda16091_arm64 on macOS. On another image, I am having difficulty removing a red color cast from the t-shirt.
including the dng should anyone wish to try.
20241012-_A120827.dng (70.8 MB)
Sorry, are you sure this is the right time? It should be number 800 with a different hash.
keep in mind that this is no production ready software - new versions of the module can break older edits …
Here is another one where you can see the difference.
The difference is similar to your example: the blue attenuation is weaker/different in the experimental variant:
Standard:
Experimental
The raw file is my own and is licensed under Creative Commons, By-Attribution, Share-Alike
yes, the numbers are irrelevant since i include agx.c into my local macos build and test environment (see comments in Blender AgX in darktable (proof of concept) - #181 )
I just share my own dogfood …
Yes, I encountered the same problem (white picture) on my windows system, when I moved to a higher build. As someone pointed out (don’t remember who) the parameters are not forwarded, hence the problem. When it will get into the mainstream development, it will be. The current solution is to compress the history stack to the first instance of Agx and start over
This is most likely caused by overexposure. DXO PureRAW does not seem to correct it properly.
I recommend offering original raw file as play raw to see what can be done. Please not here in this tread.
Done…version with the checkbox
It’s in the original RAW file as well and it is not overexposure.
I can remove the red color cast with the Color Lookup Table. Otherwise, Agx is very powerful and developing nicely.
recent macOS arm64 build - hard to follow the agx evolution… 
:
darktable-5.1.0+704~g1acda16091_arm64 (1).dmg
same comments as in Blender AgX in darktable (proof of concept) - #181
OK, so the gamut nightmare is not yet over.
Both build 800-g892743 and 801-ae59f735 can be forced to corrupt colours by lowering the offset (which can lead to negative values, that should be desaturated and fixed by the low guard rail):
So, for now, don’t push the offset too hard. Other than that, you should be OK, I think.
That’s the problem that I’d seen before, and it can also occur with black relative exposure. As I said in some earlier posts, setting preserve hue to a non-zero value completely corrects the issue, even at the lowest setting of 0.01
I’ll have to check that again, thanks.
I’m still working on the management of the most problematic colours.
Darktable / Blender side by side and difference. The transition around the bright lights is better in Blender.
Hmm, I find the surroundings around the blue light source in the center unnaturally dark in both examples.
