Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - piotrus3333

Pages: [1] 2 3 ... 17
1
ok, so at least we know that it used to work as expected for a brief moment:


2
Wait, so for any LUTs from outside Corona install we need either the string option or a gamma operator @0.45 before the LUT? I remember trying some LUTs from other sources but gave up thinking they were not the right type.

I do not know the story behind luts from Corona installer but, in general - yes - to have a lut do what it is supposed to do in Corona VFB you need gamma transform operator (1/2.2).
I guess the story why it all works like that is long forgotten as the support was unable to point me to the simple solution - the string option for adjusting VFB gamma. I dug it out from an old 2015 post.

3
But when importing exr's from corona to fusion, there is a extra gamma applied (1.2?) because the image in fusion is much darker than in VFB. And then you need to specify the float gamma thing to have the same result in vfb and fusion ?

AgX luts for Corona from this thread are made for default Corona behaviour regarding gamma transforms in VFB. by default VFB has hidden 2.2 transform after the TONE MAPPING stack and effects. it also has hidden gamma transforms in every LUT operator.
if you are using my AgX luts there is no need for string option changing VFB's gamma behaviour ("float gamma thing").

4
not much difference between Legacy and Physical in RawComponentDiffuse here:

5
looks like you have everything you need here:
https://forum.corona-renderer.com/index.php?topic=40952.msg216985#msg216985

you are good to go with luts I posted a while ago.
edit: no need for string options or gamma operators in vfb.

in Corona Image Editor / VFB:

LUT: mP_Corona_AgX_A_matrix.cube  (this is color matrix from AgX ocio config simulated as lut for Corona and Corona only, it relies on how Corona handles luts, will not work as expected anywhere else - use ocio instead)
LUT(logarythmic): mP_Corona_AgX_B_log_AgX_kraken.cube (this take us to AgX Log (Kraken) - make all your colour correction, grading, look or whatever here)

here goes your custom look, lut most likely. create it on AgX Log (Kraken) image saved from CIE or frame buffer. in Fusion, Photoshop etc.

LUT: AgX_Default_Contrast.cube (attached below, this one would put your Kraken log nicely on a srgb display. edit: nicely but still missing the "look" so it is "bland" on purpose. this is cube version on the lut from original AgX ocio. 1D lut, just a contrast curve. you can obviously add this transform to your look for convenience)

and if you find AgX great - do not forget to say Thank You to Troy Sobotka: https://blenderartists.org/t/dealing-with-aces-agx-srgb/1480752/662



6
From my point of view, the Agx color management is quite seducing. Nice highlight falloff, colors OK, i like the desaturated aspect as will on high values.

I most of the time use your AgX matrix (thanks) + custom 1D curve made with Lutcalc, and it works quite well.

I also tend to have little photoshop editing at the end, so i like to have my colors right in the render, and i find it very hard to finetune them in the VFB.

So i thought of finding the nice color setups with a lut in Resolve, and then bake them with AgX in one single LUT.

are you using Corona Image Editor?

7
if "avoiding user mistakes" is THE strategy - was anything done about Tone Curve after this thread:
https://forum.corona-renderer.com/index.php?topic=40616.0

an updated tooltip or something?

No

well, there you go.
where is a sensible limit of protecting users from "breaking color management" (the non-existent one?) by adjusting gamma.

anyway..

+1 for Gamma operator, it should be there.

8
It would be nice to have your resolve/fusion workflow to see how you manage to create those LUT's... ;)

Between the -1.2 string, the "log" option in the vfb lut, the AgX ocio and DCTL (that i managed to install in resolve+fusion), the custom color correct node, well...it gets a little confused ;)

So when i color edit a 32bit image with Agx and dctl, i have trouble exporting to a lut to have the same result in the corona vfb

well,
feel free to ask the Corona Team why things are so convoluted with luts in CIE and frame buffer: https://forum.corona-renderer.com/index.php?topic=40988.0;all

if you're on 11.1 - you can use Gamma Operator 0.455 before LUT operators and the rest of invisible gamma transforms is cancelling itself out. no need for string option and this would work in CIE as well.

Fusion exports luts only for closed domain of 0-1 float, same as photoshop and most lut tools.
Easy way of doing that in Corona is Highlight compression 999 (Reinhard tonemapper x=y/(y+1)) - it acts as your log encoding - raw render is compressed into 0-1 range and lut can access those colour easily.
So in Fusion after creating hald image you need to apply reversed Reinhard on it, convert to arri logC3 and then AgX DCTL >>> and you have a lut that does Reinhard to one of AgX DCTL displays.

what are you trying to create exactly? a macro from Fusion is of no use if you do not know the math behind.


9
if "avoiding user mistakes" is THE strategy - was anything done about Tone Curve after this thread:
https://forum.corona-renderer.com/index.php?topic=40616.0

an updated tooltip or something?

10
For what it's worth - Gamma operator lets you use lut files in Image Editor in the same manner as in every other software. just makes things simpler for the time being.

11
Hello Piotrus,

what do you mean by "float colormap.additionalGamma = -1.2" ?
do you type this in maxcript listener ? (when i type this, i got a bunch of errors)

thanks!


12
I would love to hear the reasoning behind that decision.

13
[Max] I need help! / Re: Render multiples camera matching
« on: 2024-04-19, 16:06:35 »
3dsMax State Sets?

14
More of AgX by Troy Sobotka - this time his Resolve version of it (quite different) married with a film look from Arri:
https://forum.corona-renderer.com/index.php?topic=41947.msg223544#msg223544

note: it does require a string option to turn off VFB's sRGB view lut so might be a bit more cumbersome to use.

15
The thing I find different about CoronaPhysicalMtl and energy conservation is actually too much energy reflected at low Base Color values like 0.02-0.04.

I'm talking nonsense - CoronaPhysicalMtl is actually a bit darker than StandardSurface.

What is odd though is that CoronaPhysicalMtl returns at F0 (furnace test, GeoSphere mesh, Base Color 0.18, full roughness, ior 1.5) less than 0.18 float.

Compared with VRayMtl here:

Pages: [1] 2 3 ... 17