Author Topic: Time to ditch sRGB/Linear as default (?)  (Read 102144 times)

2017-02-28, 09:53:32
Reply #90

Fluss

  • Active Users
  • **
  • Posts: 553
    • View Profile
Damn what a difference between the first two images. The first one suffers from the "murky greys" that I experience when using Corona's highlight compression and the 2nd has those nice ethereal highlights with controlled natural burnouts.

I totally agree, the ACES filmic mapping looks way closer to what we should see through a camera with great dynamic range.

I have not really informed myself about ACES yet, so what is the workflow here ?
« Last Edit: 2017-02-28, 10:43:33 by Fluss »

2018-03-02, 15:56:19
Reply #91

Okmijun

  • Active Users
  • **
  • Posts: 25
    • View Profile
I have a very simple question for those who are familiar with Fusion, which I am not...obviously.
So, basically, I just need following steps to do, and the tutorials I've found are much more complex than this, and it is hard for me to find what I really need...

1. Import 16-32-bit TIFF or EXR
2. Apply macro (or settings?) provided by DeadClown
3. export, render or what ever....

I am not kidding, this mission impossible for me.
And last but not least...
I do not want to teach to fish, just give me the fish and feed me for the day!!
(so, do not point me on help or google, please)

2018-03-02, 17:54:30
Reply #92

dubcat

  • Active Users
  • **
  • Posts: 425
  • ฅ^•ﻌ•^ฅ meow
    • View Profile
feed me

Copy and paste this into Fusion

Code: [Select]
{
Tools = ordered() {
sRGB_1 = CustomColorMatrix {
CtrlWZoom = false,
NameSet = true,
Inputs = {
Matrix = Input {
Value = MatrixTable {
NumEntries = 54,
Type = 10,
Offset = 0,
Minimum = 0,
Maximum = 1,
MinimumValue = 0,
MaximumValue = 1,
StartSlope = 1,
EndSlope = 1,
StartIn = 0,
EndIn = 1,
Table = { 1, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 1.60475, -0.53108, -0.07367, 0, 0, 0, 0, -0.10208, 1.10813, -0.00605, 0, 0, 0, 0, -0.00327, -0.07276, 1.07602, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 1 }
},
},
Input = Input {
SourceOp = "dubcat_aces_v3",
Source = "Output",
},
},
ViewInfo = OperatorInfo { Pos = { -440, 379.5 } },
},
dubcat_aces_v3 = Custom {
NameSet = true,
Inputs = {
NumberIn1 = Input { Value = 0.0245786, },
NumberIn2 = Input { Value = 9.0537e-005, },
NumberIn3 = Input { Value = 0.983729, },
NumberIn4 = Input { Value = 0.432951, },
NumberIn5 = Input { Value = 0.238081, },
NumberIn6 = Input { Value = 1, },
LUTIn1 = Input {
SourceOp = "dubcat_aces_v3LUTIn1",
Source = "Value",
},
LUTIn2 = Input {
SourceOp = "dubcat_aces_v3LUTIn2",
Source = "Value",
},
LUTIn3 = Input {
SourceOp = "dubcat_aces_v3LUTIn3",
Source = "Value",
},
LUTIn4 = Input {
SourceOp = "dubcat_aces_v3LUTIn4",
Source = "Value",
},
RedExpression = Input { Value = "((c1*n6)*((c1*n6)+n1)-n2) / ((c1*n6)*(n3*(c1*n6)+n4)+n5)", },
GreenExpression = Input { Value = "((c1*n6)*((c1*n6)+n1)-n2) / ((c1*n6)*(n3*(c1*n6)+n4)+n5)", },
BlueExpression = Input { Value = "((c1*n6)*((c1*n6)+n1)-n2) / ((c1*n6)*(n3*(c1*n6)+n4)+n5)", },
NumberControls = Input { Value = 1, },
NameforNumber1 = Input { Value = "0.0245786", },
NameforNumber2 = Input { Value = "0.000090537", },
NameforNumber3 = Input { Value = "0.983729", },
NameforNumber4 = Input { Value = "0.4329510", },
NameforNumber5 = Input { Value = "0.238081", },
NameforNumber6 = Input { Value = "Exposure", },
ShowNumber7 = Input { Value = 0, },
ShowNumber8 = Input { Value = 0, },
ShowPoint1 = Input { Value = 0, },
ShowPoint2 = Input { Value = 0, },
ShowPoint3 = Input { Value = 0, },
ShowPoint4 = Input { Value = 0, },
ShowLUT1 = Input { Value = 0, },
ShowLUT2 = Input { Value = 0, },
ShowLUT3 = Input { Value = 0, },
ShowLUT4 = Input { Value = 0, },
Image1 = Input {
SourceOp = "RRT_SAT_1",
Source = "Output",
},
},
ViewInfo = OperatorInfo { Pos = { -550, 379.5 } },
},
dubcat_aces_v3LUTIn1 = LUTBezier {
KeyColorSplines = {
[0] = {
[0] = { 0, RH = { 0.333333333333333, 0.333333333333333 }, Flags = { Linear = true } },
[1] = { 1, LH = { 0.666666666666667, 0.666666666666667 }, Flags = { Linear = true } }
}
},
SplineColor = { Red = 204, Green = 0, Blue = 0 },
NameSet = true,
},
dubcat_aces_v3LUTIn2 = LUTBezier {
KeyColorSplines = {
[0] = {
[0] = { 0, RH = { 0.333333333333333, 0.333333333333333 }, Flags = { Linear = true } },
[1] = { 1, LH = { 0.666666666666667, 0.666666666666667 }, Flags = { Linear = true } }
}
},
SplineColor = { Red = 0, Green = 204, Blue = 0 },
NameSet = true,
},
dubcat_aces_v3LUTIn3 = LUTBezier {
KeyColorSplines = {
[0] = {
[0] = { 0, RH = { 0.333333333333333, 0.333333333333333 }, Flags = { Linear = true } },
[1] = { 1, LH = { 0.666666666666667, 0.666666666666667 }, Flags = { Linear = true } }
}
},
SplineColor = { Red = 0, Green = 0, Blue = 204 },
NameSet = true,
},
dubcat_aces_v3LUTIn4 = LUTBezier {
KeyColorSplines = {
[0] = {
[0] = { 0, RH = { 0.333333333333333, 0.333333333333333 }, Flags = { Linear = true } },
[1] = { 1, LH = { 0.666666666666667, 0.666666666666667 }, Flags = { Linear = true } }
}
},
SplineColor = { Red = 204, Green = 204, Blue = 204 },
NameSet = true,
},
RRT_SAT_1 = CustomColorMatrix {
NameSet = true,
Inputs = {
Matrix = Input {
Value = MatrixTable {
NumEntries = 54,
Type = 10,
Offset = 0,
Minimum = 0,
Maximum = 1,
MinimumValue = 0,
MaximumValue = 1,
StartSlope = 1,
EndSlope = 1,
StartIn = 0,
EndIn = 1,
Table = { 1, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0.59719, 0.35458, 0.04823, 0, 0, 0, 0, 0.076, 0.90834, 0.01566, 0, 0, 0, 0, 0.0284, 0.13383, 0.83777, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 1 }
},
},
},
ViewInfo = OperatorInfo { Pos = { -660, 379.5 } },
}
}
}

The original code is made by Stephen Hill, this is my Fusion port. It still has the ACES Blue turns into pink bug.
Adjust the exposure knob, 4 seem to be a good place to start.





             ___
    _] [__|OO|
   (____|___|     https://www.twitch.tv/dubca7 / https://soundcloud.com/dubca7 ( ͡° ͜ʖ ͡°) choo choo

2018-03-03, 07:53:34
Reply #93

Okmijun

  • Active Users
  • **
  • Posts: 25
    • View Profile

2018-03-03, 10:44:04
Reply #94

Okmijun

  • Active Users
  • **
  • Posts: 25
    • View Profile
So far I did this



How to apply these settings or script whatever?
When I move sliders nothing happens, even the numbers on the right side are changing?
Thanks in advance!

2018-03-03, 14:53:51
Reply #95

Okmijun

  • Active Users
  • **
  • Posts: 25
    • View Profile
i made it!
Thanks!
You made one living human soul to be happy!

2018-03-07, 12:40:25
Reply #96

Correntes

  • Active Users
  • **
  • Posts: 100
    • View Profile
    • PRESSRENDER
Yeah we also tend not to use Corona HC.
It simply destroy all the highlights across the image leaving a flat mess.

We usually use Filmic highlights/shadows.

We are also trying not to depend on post-process software. All straight from the framebuffer.


2018-03-07, 17:35:52
Reply #97

Jpjapers

  • Active Users
  • **
  • Posts: 1644
    • View Profile
This is a super interesting thread.
I can see rawalanches point that the user base *generally* works in a way that would benefit a 'true to camera' look because the the final output from us, in the archviz world, are usually the final deliverables and we take on the roles of lighting,colour grading etc ourselves so from a workflow standpoint it would speed things up alot. Whereas when theres a hella lot of people further down the pipleline after the initial render it becomes an issue for it to entirely be removed. Hence why the checkbox would remain.

Im all for it if it means my renders look truer to what a camera would produce and i dont have to rely on luts and lightmix tweaking to get the ideal look and feel in my renders. I also never use Highlight compression in corona as it tends to flatten everything.
« Last Edit: 2018-03-07, 17:40:31 by jpjapers »

2018-03-29, 21:51:27
Reply #98

tanguybod

  • Active Users
  • **
  • Posts: 47
    • View Profile
I think those days the tide is changing from swiss officer knives style (AKA gazilions of AOV) and I am one of those, don't get me wrong, to the more neat "this is your beauty, and this is your masks) period.
Specially guys like WETA, the head of dev is a HARD Liner about that and he is right in many ways. in studios, for mostly multi shots productions, the NEMESIS is heterogeneous output from COMP dpt and / or CG as well, meaning that the director at the end of the day as a heart attack when switching from shot to shot, the color is not flowing correctly and that takes a lot of time to manage and / or control.
So at the end, their thinking is: Why the fuck using a PBR engine and all the pain it brings IF we kill the result a comp time ? that what it is about.
I agree 100% with that. But it requires an education cycle again in the film industry to not get out of that and do a strike with just one little email saying that you just realized the shot was supposed to be night time and not day light, for example.
It will take a bit of time to be able to lose those hard coded habit we have ion the industry, because they are well founded, at the end, but not really making sense. AKA 2nd amendment if you follow me.

And indeed is the question and need of keeping linearity (not Linear workflow... ahah) between all brick of the pipeline. typical pipeline involves a lookDev, (maya/max/houdini/C4D - Nuke/Fusion/Smoke - Katana/Clarisse - Avid/LightWorks/Premiere/and what not. All those guys are required those days to display at viewport level the exact same level in shading and textures display. Probably adding a bit of a challenge as well).

Cheers

2018-04-10, 07:36:43
Reply #99

vermu

  • Active Users
  • **
  • Posts: 75
    • View Profile
I would like that change. If there would be button for everyone there's only win/win. I like that.

2018-05-17, 23:46:31
Reply #100

vkiuru

  • Active Users
  • **
  • Posts: 320
    • View Profile
I've been on a nearly 4 month FStorm vacation and liked the results it gave me. Haven't been paying attention to Corona during the time and have a lot of catching up to do, so first I wanted to ask if this discussion has been picked up by the devs?

2018-05-21, 14:19:01
Reply #101

Juraj

  • Active Users
  • **
  • Posts: 4743
    • View Profile
    • studio website
I've been on a nearly 4 month FStorm vacation and liked the results it gave me. Haven't been paying attention to Corona during the time and have a lot of catching up to do, so first I wanted to ask if this discussion has been picked up by the devs?

Write some thoughts/comparisons :- )
Please follow my new Instagram for latest projects, tips&tricks, short video tutorials and free models
Behance  Probably best updated portfolio of my work
lysfaere.com Please check the new stuff!

2018-05-22, 18:32:45
Reply #102

Tok_Tok

  • Active Users
  • **
  • Posts: 121
    • View Profile
Here you go, just copy and paste it into your graph. Let me know what you think :) I used the function described here: http://forums.odforce.net/topic/25019-hable-and-aces-tonemapping/#comment-145839 . With some fooling around you can make it less contrasty but I used the values as described in the thread as default.

Code: [Select]
{
Tools = ordered() {
ACES_FilmicTonemapping = Custom {
CtrlWZoom = false,
NameSet = true,
CustomData = {
Settings = {
[1] = {
Tools = ordered() {
ACES_FilmicTonemapping = Custom {
Inputs = {
NameforNumber2 = Input { Value = "tB", },
LUTIn4 = Input {
SourceOp = "ACES_FilmicTonemappingLUTIn4",
Source = "Value",
},
ShowPoint2 = Input { Value = 0, },
ShowLUT1 = Input { Value = 0, },
ShowPoint1 = Input { Value = 0, },
RedExpression = Input { Value = " (c1*(n1*c1+n2) ) / (c1*(n3*c1+n4)+n5)", },
Image1 = Input {
SourceOp = "PipeRouter1",
Source = "Output",
},
LUTControls = Input { Value = 1, },
LUTIn2 = Input {
SourceOp = "ACES_FilmicTonemappingLUTIn2",
Source = "Value",
},
ShowNumber8 = Input { Value = 0, },
NumberIn1 = Input { Value = 2.51, },
ShowLUT3 = Input { Value = 0, },
ShowLUT2 = Input { Value = 0, },
NameforNumber1 = Input { Value = "tA", },
NumberControls = Input { Value = 1, },
LUTIn3 = Input {
SourceOp = "ACES_FilmicTonemappingLUTIn3",
Source = "Value",
},
NumberIn2 = Input { Value = 0.03, },
ShowNumber6 = Input { Value = 0, },
NumberIn4 = Input { Value = 0.59, },
NumberIn3 = Input { Value = 2.43, },
ShowPoint4 = Input { Value = 0, },
ShowLUT4 = Input { Value = 0, },
GreenExpression = Input { Value = " (c1*(n1*c1+n2) ) / (c1*(n3*c1+n4)+n5)", },
ShowPoint3 = Input { Value = 0, },
LUTIn1 = Input {
SourceOp = "ACES_FilmicTonemappingLUTIn1",
Source = "Value",
},
BlueExpression = Input { Value = " (c1*(n1*c1+n2) ) / (c1*(n3*c1+n4)+n5)", },
NameforNumber5 = Input { Value = "tE", },
NameforNumber4 = Input { Value = "tD", },
NameforNumber3 = Input { Value = "tC", },
ShowNumber7 = Input { Value = 0, },
NumberIn5 = Input { Value = 0.14, },
},
CtrlWZoom = false,
NameSet = true,
ViewInfo = OperatorInfo { Pos = { 1100, 412.5, }, },
CustomData = {
},
Name = "ACES_FilmicTonemapping",
},
ACES_FilmicTonemappingLUTIn1 = LUTBezier {
SplineColor = { Green = 0, Blue = 0, Red = 204, },
KeyColorSplines = {
[0] = {
[0] = { 0, RH = { 0.333333333333333, 0.333333333333333, }, Flags = { Linear = true, }, },
[1] = { 1, LH = { 0.666666666666667, 0.666666666666667, }, Flags = { Linear = true, }, },
},
},
NameSet = true,
Name = "ACES_FilmicTonemappingLUTIn1",
},
ACES_FilmicTonemappingLUTIn2 = LUTBezier {
SplineColor = { Green = 204, Blue = 0, Red = 0, },
KeyColorSplines = {
[0] = {
[0] = { 0, RH = { 0.333333333333333, 0.333333333333333, }, Flags = { Linear = true, }, },
[1] = { 1, LH = { 0.666666666666667, 0.666666666666667, }, Flags = { Linear = true, }, },
},
},
NameSet = true,
Name = "ACES_FilmicTonemappingLUTIn2",
},
ACES_FilmicTonemappingLUTIn3 = LUTBezier {
SplineColor = { Green = 0, Blue = 204, Red = 0, },
KeyColorSplines = {
[0] = {
[0] = { 0, RH = { 0.333333333333333, 0.333333333333333, }, Flags = { Linear = true, }, },
[1] = { 1, LH = { 0.666666666666667, 0.666666666666667, }, Flags = { Linear = true, }, },
},
},
NameSet = true,
Name = "ACES_FilmicTonemappingLUTIn3",
},
ACES_FilmicTonemappingLUTIn4 = LUTBezier {
SplineColor = { Green = 204, Blue = 204, Red = 204, },
KeyColorSplines = {
[0] = {
[0] = { 0, RH = { 0.333333333333333, 0.333333333333333, }, Flags = { Linear = true, }, },
[1] = { 1, LH = { 0.666666666666667, 0.666666666666667, }, Flags = { Linear = true, }, },
},
},
NameSet = true,
Name = "ACES_FilmicTonemappingLUTIn4",
},
},
},
},
},
Inputs = {
NumberIn1 = Input { Value = 2.51, },
NumberIn2 = Input { Value = 0.03, },
NumberIn3 = Input { Value = 2.43, },
NumberIn4 = Input { Value = 0.59, },
NumberIn5 = Input { Value = 0.14, },
LUTIn1 = Input {
SourceOp = "ACES_FilmicTonemappingLUTIn1",
Source = "Value",
},
LUTIn2 = Input {
SourceOp = "ACES_FilmicTonemappingLUTIn2",
Source = "Value",
},
LUTIn3 = Input {
SourceOp = "ACES_FilmicTonemappingLUTIn3",
Source = "Value",
},
LUTIn4 = Input {
SourceOp = "ACES_FilmicTonemappingLUTIn4",
Source = "Value",
},
RedExpression = Input { Value = " (c1*(n1*c1+n2) ) / (c1*(n3*c1+n4)+n5)", },
GreenExpression = Input { Value = " (c1*(n1*c1+n2) ) / (c1*(n3*c1+n4)+n5)", },
BlueExpression = Input { Value = " (c1*(n1*c1+n2) ) / (c1*(n3*c1+n4)+n5)", },
NumberControls = Input { Value = 1, },
NameforNumber1 = Input { Value = "tA", },
NameforNumber2 = Input { Value = "tB", },
NameforNumber3 = Input { Value = "tC", },
NameforNumber4 = Input { Value = "tD", },
NameforNumber5 = Input { Value = "tE", },
ShowNumber6 = Input { Value = 0, },
ShowNumber7 = Input { Value = 0, },
ShowNumber8 = Input { Value = 0, },
ShowPoint1 = Input { Value = 0, },
ShowPoint2 = Input { Value = 0, },
ShowPoint3 = Input { Value = 0, },
ShowPoint4 = Input { Value = 0, },
LUTControls = Input { Value = 1, },
ShowLUT1 = Input { Value = 0, },
ShowLUT2 = Input { Value = 0, },
ShowLUT3 = Input { Value = 0, },
ShowLUT4 = Input { Value = 0, },
},
ViewInfo = OperatorInfo { Pos = { 1100, 412.5, }, },
},
ACES_FilmicTonemappingLUTIn1 = LUTBezier {
KeyColorSplines = {
[0] = {
[0] = { 0, RH = { 0.333333333333333, 0.333333333333333, }, Flags = { Linear = true, }, },
[1] = { 1, LH = { 0.666666666666667, 0.666666666666667, }, Flags = { Linear = true, }, },
},
},
SplineColor = { Red = 204, Green = 0, Blue = 0, },
NameSet = true,
},
ACES_FilmicTonemappingLUTIn2 = LUTBezier {
KeyColorSplines = {
[0] = {
[0] = { 0, RH = { 0.333333333333333, 0.333333333333333, }, Flags = { Linear = true, }, },
[1] = { 1, LH = { 0.666666666666667, 0.666666666666667, }, Flags = { Linear = true, }, },
},
},
SplineColor = { Red = 0, Green = 204, Blue = 0, },
NameSet = true,
},
ACES_FilmicTonemappingLUTIn3 = LUTBezier {
KeyColorSplines = {
[0] = {
[0] = { 0, RH = { 0.333333333333333, 0.333333333333333, }, Flags = { Linear = true, }, },
[1] = { 1, LH = { 0.666666666666667, 0.666666666666667, }, Flags = { Linear = true, }, },
},
},
SplineColor = { Red = 0, Green = 0, Blue = 204, },
NameSet = true,
},
ACES_FilmicTonemappingLUTIn4 = LUTBezier {
KeyColorSplines = {
[0] = {
[0] = { 0, RH = { 0.333333333333333, 0.333333333333333, }, Flags = { Linear = true, }, },
[1] = { 1, LH = { 0.666666666666667, 0.666666666666667, }, Flags = { Linear = true, }, },
},
},
SplineColor = { Red = 204, Green = 204, Blue = 204, },
NameSet = true,
},
},
ActiveTool = "ACES_FilmicTonemapping",
}

Is it possible to make this script for After Effects? I'm also very interested in this. I always use Highlight Compression but it always felt like the images would lose depth, seeing the ACES tonemapping blows me away, such a big difference!

2018-05-25, 11:22:40
Reply #103

Jpjapers

  • Active Users
  • **
  • Posts: 1644
    • View Profile
I've been on a nearly 4 month FStorm vacation and liked the results it gave me. Haven't been paying attention to Corona during the time and have a lot of catching up to do, so first I wanted to ask if this discussion has been picked up by the devs?

Yes please write some comparisons. I wanted to look into it too but the lawsuit surrounding it has put me off testing it in a production environment

2018-06-08, 14:47:53
Reply #104

aldola

  • Active Users
  • **
  • Posts: 109
    • View Profile
Would be great to have real camera responses instead of linear output as default.

it is possible to make presets ?, like canon 5d mark 4,  canon 5ds etc

i think that a lot of people is working with corona as a photographer and having to figure out  tonemapping from linear every time is more difficult.

May be is a dumb question and we can make this with luts, but the ones that comes with corona doesn`t seem to be the case.