Blender AgX in darktable (proof of concept)

The fix for that one has been merged into darktable master.

1 Like

finally i prefer the 857.

1 Like

recent macOS arm64 build:
darktable-5.1.0+815~gd82ab6007a_arm64.dmg

same comments as in Blender AgX in darktable (proof of concept) - #181

2 Likes

Was hoping that I’d be able to do something with it using rgb curve, but that was optimistic. This is what you’d use LUTs for (if darktable had the feature).

I was able to use to use some of these log to rec 709 LUTs to get it in the right ballpark:

But yeah, you’d want to specify what log to output, like Arri LOG-C or Sony S-LOG3:

Then follow it up with something like ImpulZ LUTs for Arri LOG-C or Sony S-LOG3.

Again, darktable does not handle 1D LUTs, which makes a proper LUT workflow more or less impossible (or extremely cumbersome).

The right place to add this feature would perhaps be the LUT 3D module though, as @Xavier_Bourque describes in the GitHub issue. But that seems it won’t happen as the issue is marked “not planned”. I’d be forever grateful to be able to work with my video log LUTs in darktable. I guess a dropdown of common log LUTs to accompany the “logarithmic tone mapping only” checkbox.

Also big fan of the 3 tab version

1 Like

I’ve not done it with custom curves, but have made a log only curve with filmic to then apply a lut afterward. I’m not using luts much any more, but more recently have done the same thing before exporting exr, to then open in vkdt for the film sim module.

Not sure if the log curve in agx gives the same results as in filmic (will test later). I guess the primaries tab will allow for some different results.

1 Like

Just asking but don’t you find the duplication of sliders potentially a bit confusing…maybe not to someone that has followed this thread but I doubt many are going to digest the 1145+ posts …but maybe its just me…

1 Like

Todd, Can you clarify where there would be a duplication of sliders. I’m a bit confused.

First two tabs

1 Like

Actually the fact that some controls are duplicated across tabs makes it very convenient as changing tab becomes the exception, not the rule.

I would love to see this concept be applied to the Tone Equalizer module and have some controls duplicated from “masking” to “advance” tab.

Amazing work.
I’ve been waiting for something a little more straightforward to apply AGX without needing 3 steps of extra file conversion and node graphs

ART has had this feature for some time. I’m not familiar with Blender, but displaying an EXR with AgX is simple (I don’t know about actual processing and export).

Have tested now and yes, the agx and filmic log curves give very different results, with the same black and white relative values. Agx is much brighter, and of course primaries give different results.

Ya I think it will be a personal decision…I don’t find it that way…to me when the graph is collapsed you have saved almost no space and you have an extra tab and replicated controls which I still find to be a bit of a weird way to approach things in a UI but as I said its personal… i find that the relative white and black can alter the shape of the curve a lot so if you use the auto pickers they seem for the most part to give a decent result but sometimes the shape of the curve is such that it has a very sharp inflection or its basically an exponential such that the shoulder commands for example esp for highlights don’t really do much at all…you can easily make subsequent adjustments to craft the curve back to an S-shape or as you want but its often at least one or two back and forth if you are tweaking the relative white and black…

The agx log mapping, applied without the curve, does not preserve mid grey. It takes the input, performs the log, subtracts the log of the selected black level (so it maps that value to 0), and scales the result in a way that takes the selected white level to 1.

In filmic, you never get the direct output of the log mapping.

1 Like

I take whatever comes, two tabs, three tabs, one tab…

For me this is a game changer. I do all new developments with AgX. For my type of photography (nature, landscapes), besides some basic adjustments (exposure, color calibration, sharpening), it’s in most cases the only module needed to get to a good and punchy image. It’s almost as if the sliders always push the image in the ‘right’ direction.

I’m wondering whether software companies would ‘fine tune’ such a module so much before the first release. I’d rather prefer to get a functional module earlier and do ‘ergonomic fine tuning’ in upcoming versions.

Thank you very much @kofa!

5 Likes

Be careful or just note that each revision can or could break your edits so its safe for testing but you might find yourself doing a lot of re-editing…

1 Like

I would do as well, but as long as every bigger step is breaking the old edits, I won’t. No matter, how tempted I am, because it really is a fantastic module.

So I will wait patiently until @kofa decides the module is ready. Even so, it is admittedly hard.

2 Likes

…you might find yourself doing a lot of re-editing…

Would be a joy to do and very quick :grinning:

But thanks for the warning. I have it as a separate install, separate db, without xmp writing and I haven’t done a ton yet.

It doesn’t seem to crash DT but often you get a white screen with a new update to agx and need to reset the module so you will get it applied but at the defaults …. For sure its trival for a few photos but might be more of an issue for larger batches….