Filmic blender. Do you know it?

[fabrizio_s]

Hi,
I was really impressed by Filmic blender (https://www.youtube.com/watch?v=m9AT7H4GGrA)

Is there any similar solution for octane and octane plugin?

thanx

[calus]

I was really impressed by Filmic blender
Is there any similar solution for octane and octane plugin?

Filmic Blender is just an OCIO configuration, so you can use it in whatever software supports OCIO (OpenColorIO). https://github.com/sobotka/filmic-blender

For example Blender, Maya, Fusion, AfertEffect, Nuke, Krita, ... all support OCIO so can use Filmic Blender.
(though for some reason Filmic Blender fails to initialize in Maya)

I guess at some point Octane will also come with OCIO support then you will be able to use Filmic Blender config files in Standalone.

[bepeg4d]

Interesting, but look at this:

ciao beppe

[calus]

Interesting, but look at this:

right ,
but the saturate to white setting is a naive way to deal with this problem, and can't achieve the same result.
filmic blender try to deal with this problem automaticaly in a way that seems natural to the eye, emulating the smooth curve response of an analog film.
This problem is usually treated at the post-production stage to get the right "look",
the advantage to have it as an OCIO config is to get the exact same result in every software in the rendering pipeline, for example same look in Maya and Nuke.

n.b : OCIO is also needed for example to support the ACES workflow.

[milanm]

I absolutely agree with calus about OCIO support. Also, we should not forget color management of textures. Right now most people use sRGB textures with 2.2 gamma applied in Octane which is completely wrong because sRGB does not use gamma 2.2. It's the same for the recommended Linear/off response and gamma 2.2. That can only be a valid preview if you are watching it on a display that is calibrated for gamma 2.2, a TV, CRT or some mobile device maybe. Unfortunately most computer displays are made to meet sRGB spec and sRGB colorspace is the default on all platforms and the web. This becomes a problem when most compositing apps then treat the tonemapped image from Octane as sRGB. The difference is most noticeable in the shadows, black materials, dark environments etc.

Octane Imager could solve the preview problem partly with 3D Lut support but we definitely need a color space conversion functionality in Octane for both textures and output and that's something that OCIO could provide.

https://en.wikipedia.org/wiki/SRGB

In this image the black dashed line represents the simple 2.2 gamma that we have now in Octane versus the sRGB gamma in red.
https://en.wikipedia.org/wiki/SRGB#/med ... _gamma.svg

Regards
Milan

[fabrizio_s]

Thanx a lot to everybody

@milamn: but if I don't use gamma 2,2 my texture is too "white".....so for an interiors wich values of gamma (textures and Imager (Camera Imager)) are right?

tahnx

[milanm]

Thanx a lot to everybody

@milamn: but if I don't use gamma 2,2 my texture is too "white".....so for an interiors wich values of gamma (textures and Imager (Camera Imager)) are right?

tahnx

My main point was that it's impossible to set the right gamma in Octane because actual sRGB gamma curve is much more complex. A simple gamma value is not enough.

If you want accurate colors in your textures ( brand colors, CMYK, Pantone etc. ) you would have to convert them first to sRGB colorspace if they are not using it already, then save them as OpenExr and set gamma to 1 in Octane. Obviously that's not always practical so a default value of 2.2 is as close as we can get for sRGB textures, at least for now.

As for the "Filmic blender" "look", getting close to that can be as simple as adjusting shadows a little bit in Photoshop. It's not rocket science, it's a simple tonemap curve adjustment with some desaturation in the highlights. The controls that we have in the Camera Imager now can get you 95% there. But remember, again, this is a "LOOK" and not a standard color space. If you work with ANY "look" applied, your shaders and lights will only look good with that "look" and nothing else. There will be no standard way for you to relate your shader colors and light intensities to the real world like you can with sRGB using macbeth color charts for example. So my advice would be to work in a standard colorspace and then after that do your final color grading on untonemapped float image to get the most from your render. Like I said before, without OCIO right now it's only possible to get CLOSE to sRGB colorspace because Octane is using sRGB color primaries.

In Andrew's video, he is comparing a render to a picture from his iPhone. His iPhone definitively DOES NOT have the latitude of Arri alexa camera and the highlight roll off and desaturation like "filmic blender" does. I mean I really really wish my iPhone had that but actually the images from our phones are Rec709 which is using the same color primaries like sRGB but made to be watched on a TV with a simple gamma 2.2 --- > exactly like the Linear/Off and gamma 2.2 setting in Octane Imager

Regards
Milan

[fabrizio_s]

thank you very much Milan!!!
So we could ask "... but we definitely need a color space conversion functionality in Octane for both textures and output and that's something that OCIO could provide." in the wish list for the next release

[RealityFox]

So the best course of action is to just leave Octane on default and adjust in photoshop I take it?

My only problem I've been having using the Blender plugin is that the viewport render and the final render are always slightly different. Was hoping there was a filmic solution :/