Hi Nikola!
I'm using EasySynth every day, and it's really helpful. The added custom post material is a great feature!
In my latest renders, I noticed that the depth images (png) have a gamma lut applied to them : if I do render with a far depth distance of 2 meters, an object placed a 1 meter should have a color value of ~127 (255= 2 meters, ~127= 1 meter). But the value picked at 1 meter is much higher.
I found a fix by modifying the EasySynth Movie Pipeline Config: I've added a Color Output setting and I created a custom OpenColor IO config with a Linear Rec.709 (sRGB) profile for the transform source and a ACEScg profile for the transform destination.
It works well, but the downside of this is that all of the render passes are now in a linear space color.
The SemanticClasses.csv output doesn't match anymore the semantic images.
Do you think this "Linear workflow" could be added to the EasySynth UI?
Thank you!
Noel.
Hi Nikola!
I'm using EasySynth every day, and it's really helpful. The added custom post material is a great feature!
In my latest renders, I noticed that the depth images (png) have a gamma lut applied to them : if I do render with a far depth distance of 2 meters, an object placed a 1 meter should have a color value of ~127 (255= 2 meters, ~127= 1 meter). But the value picked at 1 meter is much higher.
I found a fix by modifying the EasySynth Movie Pipeline Config: I've added a Color Output setting and I created a custom OpenColor IO config with a Linear Rec.709 (sRGB) profile for the transform source and a ACEScg profile for the transform destination.
It works well, but the downside of this is that all of the render passes are now in a linear space color.
The SemanticClasses.csv output doesn't match anymore the semantic images.
Do you think this "Linear workflow" could be added to the EasySynth UI?
Thank you!
Noel.